Re: SMP irq sharing problem in 2.2.17

2000-10-13 Thread David Woodhouse


[EMAIL PROTECTED] said:
>  Do we have any [non-kernel] software that will read/analyze MPS
> tables?

I believe there's a port of http://people.freebsd.org/~fsmp/SMP/mptable/
somewhere. It's probably quicker to port it again yourself than search for
it.


--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



RE: SMP irq sharing problem in 2.2.17

2000-10-13 Thread Dunlap, Randy

> > I had a similar problem with the USB driver assigned to 
> IRQ19 but not receiving any interrupts.
> > 
> > Perhaps someone more knowledgable can explain why linux 
> fails under MPS1.4.
> 
> Linux is fine with MPS1.4. There are two possible causes I see
> 
> 1.Some clown built a USB controller with only 4 bits of 
> the IRQ line
>   writable/checkable. We've seen sound chips with that 'feature'
> 
> 2.The MPS 1.4 tables in the BIOS are wrong. Remarkably 
> common problem


Do we have any [non-kernel] software that will read/analyze MPS
tables?

Thanks,
~Randy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-13 Thread Alan Cox

> I had a similar problem with the USB driver assigned to IRQ19 but not receiving any 
>interrupts.
> 
> Perhaps someone more knowledgable can explain why linux fails under MPS1.4.

Linux is fine with MPS1.4. There are two possible causes I see

1.  Some clown built a USB controller with only 4 bits of the IRQ line
writable/checkable. We've seen sound chips with that 'feature'

2.  The MPS 1.4 tables in the BIOS are wrong. Remarkably common problem


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-13 Thread Alan Cox

 I had a similar problem with the USB driver assigned to IRQ19 but not receiving any 
interrupts.
 
 Perhaps someone more knowledgable can explain why linux fails under MPS1.4.

Linux is fine with MPS1.4. There are two possible causes I see

1.  Some clown built a USB controller with only 4 bits of the IRQ line
writable/checkable. We've seen sound chips with that 'feature'

2.  The MPS 1.4 tables in the BIOS are wrong. Remarkably common problem


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



RE: SMP irq sharing problem in 2.2.17

2000-10-13 Thread Dunlap, Randy

  I had a similar problem with the USB driver assigned to 
 IRQ19 but not receiving any interrupts.
  
  Perhaps someone more knowledgable can explain why linux 
 fails under MPS1.4.
 
 Linux is fine with MPS1.4. There are two possible causes I see
 
 1.Some clown built a USB controller with only 4 bits of 
 the IRQ line
   writable/checkable. We've seen sound chips with that 'feature'
 
 2.The MPS 1.4 tables in the BIOS are wrong. Remarkably 
 common problem


Do we have any [non-kernel] software that will read/analyze MPS
tables?

Thanks,
~Randy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-13 Thread David Woodhouse


[EMAIL PROTECTED] said:
  Do we have any [non-kernel] software that will read/analyze MPS
 tables?

I believe there's a port of http://people.freebsd.org/~fsmp/SMP/mptable/
somewhere. It's probably quicker to port it again yourself than search for
it.


--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-12 Thread John Silva

Timur Tabi wrote:

> ** Reply to message from "Robert B. Easter" <[EMAIL PROTECTED]> on Thu,
> 12 Oct 2000 18:47:22 -0400
>
> > Since installing a
> > second CPU and recompiling the kernel for SMP and recompiling ALSA with
> > --with-smp=yes, the sound loops.  I can hear the sound, but it doesn't
> > continue to play normally, rather, a sample will loop over and over.
>
> This means that the driver is not receiving any IRQs from the hardware.
> Typically, this is the result of an IRQ conflict (some other driver has claimed
> the IRQ for your hardware, and its interrupt handler is getting called instead).
>
> --
> Timur Tabi - [EMAIL PROTECTED]
> Interactive Silicon - http://www.interactivesi.com
>
> When replying to a mailing-list message, please don't cc: me, because then I'll just 
>get two copies of the same message.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

The 694D defaults to MPS1.4.  Make sure the 694D is configured for MPS1.1 and the 
problem will disappear.

I had a similar problem with the USB driver assigned to IRQ19 but not receiving any 
interrupts.

Perhaps someone more knowledgable can explain why linux fails under MPS1.4.

-J.

--
John Silva - [EMAIL PROTECTED]
farm9 Intrusion Detection & Prevention
http://www.farm9.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-12 Thread Timur Tabi

** Reply to message from "Robert B. Easter" <[EMAIL PROTECTED]> on Thu,
12 Oct 2000 18:47:22 -0400


> Since installing a 
> second CPU and recompiling the kernel for SMP and recompiling ALSA with 
> --with-smp=yes, the sound loops.  I can hear the sound, but it doesn't 
> continue to play normally, rather, a sample will loop over and over.

This means that the driver is not receiving any IRQs from the hardware.
Typically, this is the result of an IRQ conflict (some other driver has claimed
the IRQ for your hardware, and its interrupt handler is getting called instead).



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please don't cc: me, because then I'll just 
get two copies of the same message.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-12 Thread Timur Tabi

** Reply to message from "Robert B. Easter" [EMAIL PROTECTED] on Thu,
12 Oct 2000 18:47:22 -0400


 Since installing a 
 second CPU and recompiling the kernel for SMP and recompiling ALSA with 
 --with-smp=yes, the sound loops.  I can hear the sound, but it doesn't 
 continue to play normally, rather, a sample will loop over and over.

This means that the driver is not receiving any IRQs from the hardware.
Typically, this is the result of an IRQ conflict (some other driver has claimed
the IRQ for your hardware, and its interrupt handler is getting called instead).



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please don't cc: me, because then I'll just 
get two copies of the same message.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: SMP irq sharing problem in 2.2.17

2000-10-12 Thread John Silva

Timur Tabi wrote:

 ** Reply to message from "Robert B. Easter" [EMAIL PROTECTED] on Thu,
 12 Oct 2000 18:47:22 -0400

  Since installing a
  second CPU and recompiling the kernel for SMP and recompiling ALSA with
  --with-smp=yes, the sound loops.  I can hear the sound, but it doesn't
  continue to play normally, rather, a sample will loop over and over.

 This means that the driver is not receiving any IRQs from the hardware.
 Typically, this is the result of an IRQ conflict (some other driver has claimed
 the IRQ for your hardware, and its interrupt handler is getting called instead).

 --
 Timur Tabi - [EMAIL PROTECTED]
 Interactive Silicon - http://www.interactivesi.com

 When replying to a mailing-list message, please don't cc: me, because then I'll just 
get two copies of the same message.
 -
 To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
 the body of a message to [EMAIL PROTECTED]
 Please read the FAQ at http://www.tux.org/lkml/

The 694D defaults to MPS1.4.  Make sure the 694D is configured for MPS1.1 and the 
problem will disappear.

I had a similar problem with the USB driver assigned to IRQ19 but not receiving any 
interrupts.

Perhaps someone more knowledgable can explain why linux fails under MPS1.4.

-J.

--
John Silva - [EMAIL PROTECTED]
farm9 Intrusion Detection  Prevention
http://www.farm9.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/