Opened 12 months ago

Last modified 7 weeks ago

#14265 new bug

iprowifi3945 may not power ON wifi adapter

Reported by: cocobean Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/iprowifi3945 Version: R1/Development
Keywords: iprowifi3945, wpi Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

The iprowifi3945 driver may not 'power on' the Intel 3945 wifi adapter used by some older laptops (<=Y2010).

NOTE (same hardware tested, no hardware changes):

  1. wpi driver and Intel 3945 firmware used in FreeBSD 11.1/11.2 - works.
  2. Same Intel 3945 firmware is used in test Linux distro - works.

Errors:

KERN: [iprowifi3945] (wpi) wpi_read_eeprom: could not power ON adapter, error -2147483639
KERN: [iprowifi3945] (wpi) could not read EEPROM, error -2147483KERN: 639

Attachments (4)

P_20190104_135726[1].jpg (4.6 MB) - added by cocobean 7 months ago.
iprowifi3924 driver KDL info with hrev52711 x86
P_20190105_184811[1].jpg (2.4 MB) - added by cocobean 7 months ago.
iprowifi3945 driver KDL info on hrev52711 x86
haiku_hrev52711_x86_iprowifi3945_syslog_cocobean.txt (81.9 KB) - added by cocobean 7 months ago.
Syslog info from hrev52711 x86
haiku_hrev52738_x86_iprowifi3945_syslog_cocobean.txt (131.3 KB) - added by cocobean 6 months ago.
Syslog info from hrev52738 x86

Change History (21)

comment:1 Changed 12 months ago by waddlesplash

Please retest after hrev52114.

comment:2 Changed 12 months ago by cocobean

No change. hrev52115 x86_gcc2.

KERN: [iprowifi3945] (wpi) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) could not lock memory
KERN: [iprowifi3945] (wpi) wpi_read_eeprom: could not power ON adapter, error -2147483639
KERN: [iprowifi3945] (wpi) could not read EEPROM, error -2147483639

comment:3 Changed 11 months ago by mmu_man

Please test with hrev52204. If it used PCI config registers to do this, they it might work now as it will address the correct device.

comment:4 Changed 11 months ago by cocobean

Tested hrev52711 x86. Crashes with iprowifi3945 wifi driver. Had to use safe mode as workaround until blacklisted. See P_20190104_135726[1].jpg attachment

NOTE: 
PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8175affc, ip 0x8124fc52
...
pci_reserve_device(6,0,0,iprowifi3945)

Last edited 7 months ago by cocobean (previous) (diff)

Changed 7 months ago by cocobean

Attachment: P_20190104_135726[1].jpg added

iprowifi3924 driver KDL info with hrev52711 x86

comment:5 Changed 7 months ago by waddlesplash

The message is cut off, and without that I can't do much.

comment:6 Changed 7 months ago by cocobean

Updated info on initial PANIC message. The 'Haiku legacy driver (probe) code' messages are new as I don't think I saw this in the older revision issue.

Last edited 7 months ago by cocobean (previous) (diff)

comment:7 Changed 7 months ago by waddlesplash

Yes, they are new, the compat layer now reserves devices. That is unrelated.

Please post a picture that is not cut off at the top. I can't do much without the actual panic message.

Changed 7 months ago by cocobean

Attachment: P_20190105_184811[1].jpg added

iprowifi3945 driver KDL info on hrev52711 x86

Changed 7 months ago by cocobean

Syslog info from hrev52711 x86

comment:8 Changed 6 months ago by waddlesplash

Panic fixed in hrev52721.

comment:9 Changed 6 months ago by cocobean

Tested on hrev52738 x86. Confirmed kernel panic issues resolved:

KERN: pci_reserve_device(6,0,0,iprowifi3945)
KERN: [iprowifi3945] (wpi) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) could not lock memory
KERN: [iprowifi3945] (wpi) wpi_read_eeprom: could not power ON adapter, error -2147483639
KERN: [iprowifi3945] (wpi) could not read EEPROM, error -2147483639
KERN: pci_unreserve_device(6,0,0,iprowifi3945)

comment:10 Changed 6 months ago by waddlesplash

Please upload a new full syslog under this revision.

Changed 6 months ago by cocobean

Syslog info from hrev52738 x86

comment:11 Changed 6 months ago by cocobean

New syslog added to ticket.

comment:12 Changed 7 weeks ago by waddlesplash

Please retest after hrev53174.

comment:13 Changed 7 weeks ago by cocobean

Tested hrev53174 x86_gcc2 nightly image.
WIFI Hardware detected: 8086, 4222 - Intel PRO/Wireless 3945ABG Golan Network Connection
NOTE: No change. Previous syslog info exactly the same. No KDL (benefit, I don't have to blacklist the wpi driver anymore.)

Last edited 7 weeks ago by cocobean (previous) (diff)

comment:14 Changed 7 weeks ago by waddlesplash

There is still a "could not lock memory"?

comment:15 Changed 7 weeks ago by cocobean

Yes. All related syslog messages are the same.

comment:16 Changed 7 weeks ago by luroh

32-bit Haiku is currently broken, network wise (see ticket:15096). It would be interesting if you could give x86_64 a try. I think there's a good chance it will work, based on the seemingly similar failures to initialize our devices under gcc2h:

KERN: pci_reserve_device(6, 0, 0, iprowifi3945)
KERN: [iprowifi3945] (wpi) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
KERN: [iprowifi3945] (wpi) could not lock memory
KERN: [iprowifi3945] (wpi) wpi_read_eeprom: could not power ON adapter, error -2147483639
KERN: [iprowifi3945] (wpi) could not read EEPROM, error -2147483639
KERN: pci_unreserve_device(6, 0, 0, iprowifi3945)
KERN: pci_reserve_device(3, 0, 0, idualwifi7260)
KERN: [idualwifi7260] (iwm) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: [idualwifi7260] (iwm) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
KERN: [idualwifi7260] (iwm) fw chunk addr 0x404000 len 712 failed to load
KERN: [idualwifi7260] (iwm) iwm_pcie_load_section: Could not load the [0] uCode section
KERN: [idualwifi7260] (iwm) iwm_start_fw: failed -2147483639
KERN: [idualwifi7260] (iwm) Failed to start INIT ucode: -2147483639
KERN: pci_unreserve_device(3, 0, 0, idualwifi7260)

comment:17 Changed 7 weeks ago by waddlesplash

Only some machines are broken for 32-bit Haiku and network drivers. Quite a lot still work just fine, so your ticket really is the exception here.

Note: See TracTickets for help on using tickets.