On Tue, May 7, 2013 at 1:11 AM, David Cohen wrote:
> When DT is not used IOAPIC does not register irq domain. As result
> IOAPIC won't care about gpio-langwell's virq and may cause conflict if
> an irq number is equal to gpio-langwell's virq mapped beforehand.
>
> This patch tells gpio_langwell
On Tue, May 7, 2013 at 1:11 AM, David Cohen david.a.co...@intel.com wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause conflict if
an irq number is equal to gpio-langwell's virq mapped beforehand.
This patch
Hi Grant,
On 05/07/2013 09:34 AM, David Cohen wrote:
On 05/07/2013 12:59 AM, Mika Westerberg wrote:
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause
Hi Grant,
On 05/07/2013 09:34 AM, David Cohen wrote:
On 05/07/2013 12:59 AM, Mika Westerberg wrote:
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause
On 05/07/2013 12:59 AM, Mika Westerberg wrote:
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause conflict if
an irq number is equal to gpio-langwell's virq
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
> When DT is not used IOAPIC does not register irq domain. As result
> IOAPIC won't care about gpio-langwell's virq and may cause conflict if
> an irq number is equal to gpio-langwell's virq mapped beforehand.
>
> This patch tells
On 05/07/2013 12:59 AM, Mika Westerberg wrote:
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause conflict if
an irq number is equal to gpio-langwell's virq
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause conflict if
an irq number is equal to gpio-langwell's virq mapped beforehand.
This patch tells gpio_langwell to not ignore irq_base if != 0 and
preferably use it to avoid
>With 2.4.5 I *often* get kernel Oopses with IRQ
>routing error messages. This never happend before
>and the only one change was a a second network
>card inserted into the mobo and changed kernel
>from 2.4.3 to 2.4.5.
As as wrote... Here is one of them, getting every 3
hours...
CPU: 0
EIP:
I would like to know may I use the same IRQs for more
than one component with 2.4.x?
My first network card use the same IRQ as paralell
port,
and my second card use the same as my USB have.
BX chipset, ne2k-pci driver.
With 2.4.5 I *often* get kernel Oopses with IRQ
routing error messages.
I would like to know may I use the same IRQs for more
than one component with 2.4.x?
My first network card use the same IRQ as paralell
port,
and my second card use the same as my USB have.
BX chipset, ne2k-pci driver.
With 2.4.5 I *often* get kernel Oopses with IRQ
routing error messages.
With 2.4.5 I *often* get kernel Oopses with IRQ
routing error messages. This never happend before
and the only one change was a a second network
card inserted into the mobo and changed kernel
from 2.4.3 to 2.4.5.
As as wrote... Here is one of them, getting every 3
hours...
CPU: 0
EIP:
Andrey Panin wrote:
>
> Hi Brian.
>
> I'm sorry, patch itself was not attached in previous post :(
>
Yes, this does fix that part of the problem. There is still the matter
of the class code being wrong but I have ideas on how to fix that.
--
Hi Brian.
I'm sorry, patch itself was not attached in previous post :(
Best regards.
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
--- /linux/arch/i386/kernel/pci-pc.c.orig Mon Feb 12
On Sat, Feb 10, 2001 at 07:06:52PM -0500, Brian Gerst wrote:
> Alan Cox wrote:
> >
> > >
> > > ACPI: Core Subsystem version [20010208]
> > > ACPI: SCI (IRQ9) allocation failed
> > > ACPI: Subsystem enable failed
> > > Trying to free free IRQ9
> >
> > That seems to indicate acpi is freeing a
On Sat, Feb 10, 2001 at 07:06:52PM -0500, Brian Gerst wrote:
Alan Cox wrote:
SoundBlaster EMU8000 (RAM2048k)
ACPI: Core Subsystem version [20010208]
ACPI: SCI (IRQ9) allocation failed
ACPI: Subsystem enable failed
Trying to free free IRQ9
That seems to indicate acpi is
Hi Brian.
I'm sorry, patch itself was not attached in previous post :(
Best regards.
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
--- /linux/arch/i386/kernel/pci-pc.c.orig Mon Feb 12
Andrey Panin wrote:
Hi Brian.
I'm sorry, patch itself was not attached in previous post :(
Yes, this does fix that part of the problem. There is still the matter
of the class code being wrong but I have ideas on how to fix that.
--
Alan Cox wrote:
>
> >
> > ACPI: Core Subsystem version [20010208]
> > ACPI: SCI (IRQ9) allocation failed
> > ACPI: Subsystem enable failed
> > Trying to free free IRQ9
>
> That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
> good bet it will fix any random irq/driver
>
> ACPI: Core Subsystem version [20010208]
> ACPI: SCI (IRQ9) allocation failed
> ACPI: Subsystem enable failed
> Trying to free free IRQ9
That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
good bet it will fix any random irq/driver problem right now
-
To unsubscribe
Brian Gerst wrote:
>
> I'm having problems with 2.4.2-pre3 and IRQ conflicts. Last kernel that
> I tried and worked without conflict was 2.4.0-test11. Here are the
> relevant messages that I get:
I enabled more debug messages, so here is the updated messages. I also
notic
I'm having problems with 2.4.2-pre3 and IRQ conflicts. Last kernel that
I tried and worked without conflict was 2.4.0-test11. Here are the
relevant messages that I get:
Linux version 2.4.2-pre3 (root@neriak) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Sat Feb 10 11:13:59
I'm having problems with 2.4.2-pre3 and IRQ conflicts. Last kernel that
I tried and worked without conflict was 2.4.0-test11. Here are the
relevant messages that I get:
Linux version 2.4.2-pre3 (root@neriak) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Sat Feb 10 11:13:59
Brian Gerst wrote:
I'm having problems with 2.4.2-pre3 and IRQ conflicts. Last kernel that
I tried and worked without conflict was 2.4.0-test11. Here are the
relevant messages that I get:
I enabled more debug messages, so here is the updated messages. I also
noticed that ACPI is trying
SoundBlaster EMU8000 (RAM2048k)
ACPI: Core Subsystem version [20010208]
ACPI: SCI (IRQ9) allocation failed
ACPI: Subsystem enable failed
Trying to free free IRQ9
That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
good bet it will fix any random irq/driver problem right
Alan Cox wrote:
SoundBlaster EMU8000 (RAM2048k)
ACPI: Core Subsystem version [20010208]
ACPI: SCI (IRQ9) allocation failed
ACPI: Subsystem enable failed
Trying to free free IRQ9
That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
good bet it will fix any random
26 matches
Mail list logo
