Opened 13 months ago

Closed 12 months ago

Last modified 11 months ago

#14701 closed bug (fixed)

Kernel panic booting from USB on MSI laptop

Reported by: dsizzle Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/idualwifi7260 Version: R1/beta1
Keywords: panic, kernel, boot, beta Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64

Description

See attached; looks like maybe it's related to the wifi driver?

model: MSI GS63VR booting from USB, R1 beta x86_64 anyboot image from 9/27/2018

Attachments (2)

kernel-panic.jpg (319.5 KB ) - added by dsizzle 13 months ago.
screenshot of kernel panic
kp_dis.jpg (189.6 KB ) - added by dsizzle 13 months ago.
kernel panic with disassembly

Download all attachments as: .zip

Change History (10)

by dsizzle, 13 months ago

Attachment: kernel-panic.jpg added

screenshot of kernel panic

comment:1 by waddlesplash, 13 months ago

Resolution: fixed
Status: newclosed

Fixed in hrev52544.

comment:2 by dsizzle, 13 months ago

Resolution: fixed
Status: closedreopened

I still get exactly the same panic/trace with the hrev52557 nightly build.

comment:3 by waddlesplash, 13 months ago

OK. Please run "dis -b 6" at the prompt and paste that screenshot here.

by dsizzle, 13 months ago

Attachment: kp_dis.jpg added

kernel panic with disassembly

comment:4 by dsizzle, 13 months ago

new screenshot "kp_dis.jpg" attached with the disassembly. For sanity's sake I also re-imaged my USB key so it's definitely hrev52557 unless my imaging tool is lying to me.

comment:5 by waddlesplash, 12 months ago

Please retest after hrev52657.

comment:6 by dsizzle, 12 months ago

Well, now it boots without panicking...but the wifi adapter doesn't work. I guess you can close this particular ticket and I'll experiment a little to see if I need to file a separate ticket about the adapter.

comment:7 by waddlesplash, 12 months ago

Resolution: fixed
Status: reopenedclosed

There are already a number of tickets about that driver not working on specific hardware; please check if the errors in your syslog match any of the existing tickets first.

comment:8 by waddlesplash, 11 months ago

You may want to retest after hrev52792; this seems to fix the driver on more devices.

Note: See TracTickets for help on using tickets.