| Re: [proaudio] 2.6.17-rt8 kernel does not boot |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] 2.6.17-rt8 kernel does not boot
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Tue, 29 Aug 2006 11:48:20 +0200
- 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=
Each motherboard is a particular case with IRQ. With my board, it was
always booting, but crashing from time to time. I go with the APIC
interface, but even here it was still some sharing. But I did get it
very stable. It was only my webcam that was crashing the system, and as
I almost don't use it, I don't care of it until recently. I try the PIC
interface, because I was reading at it is more efficient as the APIC
(less overun). At the end, I am even able to use the webcam without
crash, but it was necessary to disable the acpi in order to win an IRQ.
And it was a "good" IRQ, the 9. The result is at I have a more stable
system as ever before with the PIC, and at I am even able to use the 3D
driver with my nvidia card (that use an IRQ when the 2D driver don't
use an IRQ).
If you look in the BIOS, you can assign some IRQ, but it is only
possible with the PIC interface, not with the APIC. I don't know all
this hardware design, but the APIC is more as a supplementary level
above the PIC as a real new hardware design. So, its great at your box
is running now, but if you get some instability, especially system
crash when accessing the hardware, it will be a clue like what this IRQ
problem is not completely solved. In some cases, it can be a
conflict between 2 drivers, as example with a nvidia card, you must
choose during the kernel configuration if you want to use the free 2D
driver or the nvidia driver, and use and compile only one of those
drivers.
Dominique
Le Tue, 29 Aug 2006 10:04:47 +0200,
"Mark Tombs" <mark.tombs@xxxxxxxxx> a écrit :
> Enabled APIC and it boots! Thanks a lot. Not completely out of the woods yet
> but I can see the light.
>
> On 8/29/06, Rossco <rosscoad@xxxxxxxxxxxxxxx> wrote:
> >
> > ......
> >
> > Dominique Michel wrote:
> > > I think at it is a hardware IRQ sharing problem. RT-kernel don't like
> > > it. You have 2 devices that share the same IRQ.
> > >
> > > You must look in the bios to see if you can reassign the IRQ, or try to
> > > move some cards from slot to slot. You can also boot the vanilla kernel
> > > and look at the output of
> > >
> > > cat /proc/interrupts
> > >
> > > It will show you the shared IRQ. acpi=off is a good option with a
> > > realtime kernel. The acpi system will be disabled and it will spare an
> > > IRQ that will be avaible for other hardware.
> > >
> > > Dominique
> > >
> >
> > Further to Dominique's comments, you could also try enabling APIC in the
> > kernel config if it is available and not already enabled. That will
> > provide more IRQs which may help to prevent the IRQ sharing.
> >
> > Ross.
> >
> >
> >