Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#17811 closed bug (fixed)

idualwifi7260 KDL when booting image from USB drive

Reported by: vidrep Owned by: waddlesplash
Priority: normal Milestone: R1/beta4
Component: Drivers/Network/idualwifi7260 Version: R1/beta3
Keywords: Cc:
Blocked By: Blocking: #17817
Platform: All

Description

hrev56202 x86_64

When attempting to boot the current Haiku image from a USB drive goes into KDL

Updating to the current hrev from SoftwareUpdater and rebooting works OK

Photo of KDL attached

Attachments (2)

IMG_0669.JPG (1.3 MB ) - added by vidrep 3 years ago.
IMG-0674.jpg (1002.2 KB ) - added by waddlesplash 3 years ago.
first KDL from Vidrep

Change History (13)

by vidrep, 3 years ago

Attachment: IMG_0669.JPG added

comment:1 by waddlesplash, 3 years ago

(The photo of the KDL actually comes from a test with hrev56208.)

comment:2 by waddlesplash, 3 years ago

Component: - GeneralDrivers/Network/idualwifi7260
Owner: changed from nobody to waddlesplash

comment:3 by waddlesplash, 3 years ago

mbrumbelow reports the same phenomenon under the iaxwifi200 driver. Very strange.

comment:4 by mbrumbelow, 3 years ago

I was able to reproduce the issue with idualwifi7260 and iaxwifi200. This was Booting from USB stick with hrev56202 iso.

comment:5 by waddlesplash, 3 years ago

The crash appears to be due to ic->ic_bss being NULL. That should never be the case in this path, because it is set by ieee80211_media_init before ieee80211_media_status is invoked. So, something is going deeply wrong.

The crash before hrev56208 was committed appeared to be an invalid memory access in tq_handle_thread. That may be related, possibly something is misusing memory.

comment:6 by waddlesplash, 3 years ago

Please test booting with SMP disabled and see if that makes any differences.

by waddlesplash, 3 years ago

Attachment: IMG-0674.jpg added

first KDL from Vidrep

comment:7 by waddlesplash, 2 years ago

You should be able to work around this, if I am correct, by temporarily blocklisting the driver, upgrading the intel_wifi_firmwares and wpa_supplicant package, and then rebooting; the driver should then work and not crash.

comment:8 by waddlesplash, 2 years ago

Blocking: 17817 added

in reply to:  6 comment:9 by atomozero, 2 years ago

i dont see difference :(

Replying to waddlesplash:

Please test booting with SMP disabled and see if that makes any differences.

comment:10 by waddlesplash, 2 years ago

Milestone: UnscheduledR1/beta4
Resolution: fixed
Status: newclosed

Fixed in hrev56238.

comment:11 by atomozero, 2 years ago

thx, now dont go to kdl :)

Note: See TracTickets for help on using tickets.