[Prism54-devel] [Bug 121] New: IRQ line too busy :(

[bugzilla-daemon at mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=121

           Summary: IRQ line too busy :(
           Product: prim54
           Version: 1.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel at prism54.org
        ReportedBy: xmedeko at gmail.com


Hi,

recently, i changed the kernel from 2.4.26 to 2.4.27, so i;ve downloaded the
latest cvs snapshot of the prism kernel, make modules install, modprobe prism54
pc_debug=255, ifconfig eth4 up and got

SIOCSIFFLAGS: Input/output error

the syslog says:

Feb 12 18:34:35 cml kernel: Unloaded prism54 driver
Feb 12 18:34:42 cml kernel: Loaded prism54 driver, version 1.2
Feb 12 18:34:42 cml kernel: PCI: Found IRQ 5 for device 00:04.0
Feb 12 18:34:42 cml kernel: IRQ routing conflict for 00:04.0, have irq 11, want
irq 5
Feb 12 18:34:42 cml kernel: prism54: pci_set_master(pdev)
Feb 12 18:34:50 cml kernel: eth4: resetting device...
Feb 12 18:34:50 cml kernel: eth4: uploading firmware...
Feb 12 18:34:50 cml kernel: eth4: firmware version: 1.0.3.0
Feb 12 18:34:50 cml kernel: eth4: firmware upload complete
Feb 12 18:34:50 cml kernel: eth4: no PIMFOR header found
Feb 12 18:34:50 cml kernel: eth4: timeout waiting for mgmt response 100,
triggering device
Feb 12 18:34:50 cml kernel: eth4: timeout waiting for mgmt response 90,
triggering device
Feb 12 18:34:50 cml kernel: eth4: timeout waiting for mgmt response 80,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 70,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 60,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 50,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 40,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 30,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 20,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 10,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response
Feb 12 18:34:51 cml kernel: eth4: mgt_commit_list: failure. oid=ff020008 err=-110
Feb 12 18:34:51 cml kernel: eth4: no PIMFOR header found
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 100,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 90,
triggering device
Feb 12 18:34:51 cml kernel: eth4: timeout waiting for mgmt response 80,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 70,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 60,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 50,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 40,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 30,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 20,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response 10,
triggering device
Feb 12 18:34:52 cml kernel: eth4: timeout waiting for mgmt response
Feb 12 18:34:52 cml kernel: eth4: mgt_commit_list: failure. oid=ff020003 err=-110
Feb 12 18:34:52 cml kernel: eth4: no PIMFOR header found
... (repeating many of times)
Feb 12 18:35:09 cml kernel: eth4: timeout waiting for mgmt response 10,
triggering device
Feb 12 18:35:09 cml kernel: eth4: timeout waiting for mgmt response
Feb 12 18:35:09 cml kernel: eth4: mgt_update_addr: failure
Feb 12 18:35:09 cml kernel: eth4: mgt_commit: failure
Feb 12 18:35:09 cml kernel: eth4: interface reset failure
Feb 12 18:35:09 cml kernel: prism54: Your card/socket may be faulty, or IRQ line
too busy :(

Yes, that's true, the IRQ is too busy, because it shared between WiFi (eth4) and
1GB Ethernet LAN, but it was working in 2.4.26. I had the same problem even with
the newest firmware.

So I've downloaded a couple of older snapshots, and the one from the 1st
November 2004 (prism54-cvs20041001) works fine. See syslog:

Feb 12 18:46:07 cml kernel: Loaded prism54 driver, version 1.2
Feb 12 18:46:07 cml kernel: PCI: Found IRQ 5 for device 00:04.0
Feb 12 18:46:07 cml kernel: IRQ routing conflict for 00:04.0, have irq 11, want
irq 5
Feb 12 18:46:07 cml kernel: prism54: pci_set_master(pdev)
Feb 12 18:46:15 cml kernel: eth4: resetting device...
Feb 12 18:46:15 cml kernel: eth4: uploading firmware...
Feb 12 18:46:16 cml kernel: eth4: firmware upload complete
Feb 12 18:46:16 cml kernel: eth4: interface reset complete
(



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.