Re: [proaudio] kernel config |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] kernel config
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Wed, 21 Mar 2007 16:07:51 +0100
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Wed, 21 Mar 2007 21:48:44 +0100,
Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx> a écrit :
> On Mi, 21.03.07 08:01 Dominique Michel <dominique.michel@xxxxxxxxxxxx>
> wrote:
>
> > Le Wed, 21 Mar 2007 08:53:25 +0100,
> > Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx> a écrit :
> >
> > > On Mi, 21.03.07 21:26 Geoff Beasley <songshop@xxxxxxxxxxxxxxx>
> > > 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.
> >
>
> No IO-APIC? Do you have ACPI disabled or pci=noacpi set in grub.conf?
> Because here it looks like:
>
> tom@SiRiUS ~ $ cat /proc/interrupts
> CPU0
> 0: 284 IO-APIC-edge timer
> 1: 2150 IO-APIC-edge i8042
> 6: 5 IO-APIC-edge floppy
> 7: 0 IO-APIC-edge parport0
> 8: 2 IO-APIC-edge rtc
> 9: 0 IO-APIC-fasteoi acpi
> 12: 4 IO-APIC-edge i8042
> 14: 71042 IO-APIC-edge ide0
> 15: 394948 IO-APIC-edge ide1
> 16: 50453 IO-APIC-fasteoi eth0
> 17: 47583 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2,
> uhci_hcd:usb3, uhci_hcd:usb4
> 18: 112936 IO-APIC-fasteoi ide2
> 19: 0 IO-APIC-fasteoi ICE1724
> 20: 97037 IO-APIC-fasteoi ICE1712
> 21: 5608587 IO-APIC-fasteoi nvidia
> NMI: 0
> LOC: 46108412
> ERR: 0
> MIS: 0
>
> 2.6.20-rt8 that is.
>
> Cheers,
> Tom
I get in my bios and I have something new now (after playing with the ps2
setting). I also removed the pci=noacpi in grub for the 2.6.21:
CPU0
0: 270 XT-PIC-XT timer
1: 176 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 5982 XT-PIC-XT ohci_hcd:usb1
4: 1669 XT-PIC-XT ohci1394, eth0
5: 98 XT-PIC-XT ohci_hcd:usb2
6: 783 XT-PIC-XT ohci_hcd:usb3, ehci_hcd:usb4
7: 1 XT-PIC-XT parport0
8: 2 XT-PIC-XT rtc
9: 0 XT-PIC-XT acpi
10: 4 XT-PIC-XT bttv0
11: 427702 XT-PIC-XT EMU10K1
12: 4 XT-PIC-XT i8042
14: 21349 XT-PIC-XT ide0
15: 6951 XT-PIC-XT ide1
NMI: 0
LOC: 477708
ERR: 0
MIS: 0
I will see if it work.
And yes, no io-apic. It doesn't help much with a realtime kernel. And APIC is
not a completely new hardware design but some kind of glue over the xt-pic and
it have more overrun.
In case of troubles, you may have to go at the xt-pic level because the
bios, as the PCI slots, doesn't understand something else. Sometime, shared IRQ
are easy to solve because you see them at the APIC level. But sometime, the
APIC level is looking good and you are in trouble. When this append, the only
possibility to see the problem is to shift to the PIC interface and solve the
problem at that level.
And when it is done, it is better to stay at the PIC level because it is
simpler and faster in the hardware.
Ciao,
Dominique