On Wed, Aug 12, 2009 at 03:51:27PM +0200, Arnaud Gomes-do-Vale wrote: > Herbert Poetzl <herbert@13thfloor.at> writes: > > > sounds like a hardware/driver issue, I presume you'll > > get the very same messages without the Linux-VServer patch > > too (i.e. with vanilla 2.6.27.29, which I'd suggest to > > test first), but anyways, if you can provide the bootup > > log and a sample of those messages, we probably can pinpoint > > the responsible driver/component > Here are the relevant logs: > http://files.glou.org/intraitable-boot.txt > http://files.glou.org/intraitable-noirqhandler.txt okay, so that looks to me like an irq-line which fires without having any driver attached to handle it ... the question now is, whether this is a hardware problem (broken apic controller) or a software bug, i.e. something enabling an interrupt without providing the proper interrupt handler ... nevertheless, this doesn't seem Linux-VServer related, as I find numerous pages reporting similar on a simple google search (for kernel 2.6.23-2.6.29) anyway, could you also provide the /proc/interrupts contents (just curious :)? best, Herbert > I had to move a few production services on the box earlier than I > wanted to so I can't do much disruptive testing; on the other hand it > doesn't look like the box has any real issues except those messages. > The packages I made are available online if anybody wants to do any > further testing: > > http://freesoftware.ircam.fr/vserver/ > > -- > Arnaud