On Thu, 2006-06-22 at 18:39 -0700, Randy.Dunlap wrote: > This sounds like just running with CONFIG_IO_APIC=n or using > "noapic" on the kernel boot command line. If that's what is > needed, we can know that. I just haven't seen info to know > what the real problem is. yes, could be a way, if we know if IO_APIC or LOCAL_APIC is enabled or not ? thanks, -- Sérgio M. B.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Follow-Ups:
- References:
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Johny <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Andrew Morton <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Johny <[email protected]>
- who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: "Randy.Dunlap" <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: "Randy.Dunlap" <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: "Randy.Dunlap" <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Chris Wedgwood <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- From: "Randy.Dunlap" <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- Prev by Date: [PATCH] avoid cpu removal if busy revisited
- Next by Date: [PATCH] Fixed the number of arguments about mremap
- Previous by thread: Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- Next by thread: Re: how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
- Index(es):
 |