http://bugzilla.kernel.org/show_bug.cgi?id=6414

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acpi-
                   |                            |[EMAIL PROTECTED]
                   |                            |et
          Component|BIOS                        |Config-Interrupts
            Summary|sky2  problem               |irq 10: nobody cared  - sky2
                   |                            |fails, sk98lin-8.31  works -
                   |                            |Toshiba M45-S265



------- Additional Comments From [EMAIL PROTECTED]  2006-04-25 10:50 -------
Chen,
Please boot with "acpi=off" and attach the output from dmesg -s64000
and paste in the contents of /proc/interrupts
and report if the sky2 is working or not.

Also, if you rmmod the driver and then load it again, as suggested
by Scott, does the problem go away?

Can you answer Shaohua's question?
> 'inb 0x4d0' and 'inb 0x4d1'?

Stephen,
XT-PIC mode is independent of level vs. edge triggering.
LAPIC mode is independent of level vs. edge triggering,

> Local APIC disabled by BIOS -- you can enable it with "lapic"

BTW. It is usually a very bad idea to over-ride the BIOS on this.
Indeed, it is usually such a bad idea, that this line should
probably be removed from the kernel to not tempt people.

Stephen,  What is the interaction between ohci and the NIC that you've
see as an issue in the past?  Chen, A simple way to to prevent the
X module from loading is to find it under /lib/modules X.ko, gzip it
and reboot.

Here is the failing device:

> lspci -vv

01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast 
Ethernet Controller (rev 10)
        Interrupt: pin A routed to IRQ 11

> failing dmesg

ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> 
IRQ 11
PCI: Setting latency timer of device 0000:01:00.0 to 64
sky2 v0.15 addr 0xcc000000 irq 11 Yukon-FE (0xb7) rev 1
sky2 eth0: addr 00:a0:d1:21:5b:e1


> working dmesg

ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> 
IRQ 11
sk98lin: Network Device Driver v8.31.2.3
(C)Copyright 1999-2006 Marvell(R).

In both cases, the device is using IRQ11.  Unclear why sky fails
and sk98lin works.  Maybe sk98lin is doing some polling and sky is not?

Both cases share the serious issue that IRQ10 is broken:

irq 10: nobody cared

This could happen if the NIC registers on IRQ11, but is really
pulling on IRQ10.

(shot in dark) Any change if you boot with sky2.disable_msi=1


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to