Le Wed, 21 Mar 2007 08:53:25 +0100,
Thomas Kuther <[EMAIL PROTECTED]> a écrit :
> On Mi, 21.03.07 21:26 Geoff Beasley <[EMAIL PROTECTED]> wrote:
>
> > what alsa are you running ?
> >
> > g.
> >
> ... and what's your output of
> $ cat /proc/interrupts
Alsa from the kernel
$ cat /proc/interrupts
CPU0
0: 12280250 XT-PIC-XT timer
1: 20913 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 109811 XT-PIC-XT ohci_hcd:usb1
4: 44460 XT-PIC-XT ohci1394, eth0
5: 12214772 XT-PIC-XT ohci_hcd:usb2
6: 304680 XT-PIC-XT ohci_hcd:usb3, ehci_hcd:usb4
7: 1 XT-PIC-XT parport0
8: 2 XT-PIC-XT rtc
9: 21237749 XT-PIC-XT acpi, EMU10K1
10: 4 XT-PIC-XT bttv0
11: 972580 XT-PIC-XT nvidia
12: 4 XT-PIC-XT i8042
14: 236149 XT-PIC-XT ide0
15: 217965 XT-PIC-XT ide1
NMI: 98265431
LOC: 12280612
ERR: 0
MIS: 0
This is with the 2.6.19. I don't get any interrupts for the nvidia with the
2.6.20 and 21.
It work well with the 2.6.19-rt15 and older kernels. Both 2.6.20 and
21 -rt hang randomly. I try to boot with acpi=off with the 2.6.20. The result
was at only the EMU10k1 was on irq 9 (no acpi), but it didn't solved the
problem. Another concern with acpi is at it is now needed for the timer with a
rt kernel, so acpi=off is not a solution. (I missed that with the 2.6.20 and 19,
it was only the button in the config for acpi. For the 2.6.21, I have both the
button and the timer.)
A difference between those kernels is at I use the nvidia driver with the
2.6.19 and the nv driver with the 2 others. I also made two 2.6.17, one for
use with the nv driver, the other for use with the nvidia, and both of them are
working fine with acpi=off.
Ciao,
Dominique
