Re: Broadcom BCM5702 Major Problems

• Next message: Martin J. Bligh: "Re: [PATCH] concurrent block allocation for ext2 against 2.5.64"
• Previous message: William Lee Irwin III: "Re: [PATCH] concurrent block allocation for ext2 against 2.5.64"
• Maybe in reply to: war@lucidpixels.com: "Broadcom BCM5702 Major Problems"
• Next in thread: Paul Rolland: "Re: Broadcom BCM5702 Major Problems"
• Reply: Paul Rolland: "Re: Broadcom BCM5702 Major Problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Found the bug.
Well, for me anyway.
When I have this configuration option turned on:

[*] IO-APIC support on uniprocessors

Everything goes to hell.

Even the 3COM I stuck in wants to get routed to IRQ 18 and you cannot even force it to use anotheR IRQ.

This option:

[*] Local APIC support on uniprocessors

Works fine.

It is the second option that royally screws over the system.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Martin J. Bligh: "Re: [PATCH] concurrent block allocation for ext2 against 2.5.64"
• Previous message: William Lee Irwin III: "Re: [PATCH] concurrent block allocation for ext2 against 2.5.64"
• Maybe in reply to: war@lucidpixels.com: "Broadcom BCM5702 Major Problems"
• Next in thread: Paul Rolland: "Re: Broadcom BCM5702 Major Problems"
• Reply: Paul Rolland: "Re: Broadcom BCM5702 Major Problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:42 EST