El Miércoles 07 Octubre 2009, Ben Hutchings escribió: > On Wed, 2009-10-07 at 11:38 +0100, Antonio Marcos López Alonso wrote: > > 2009/10/6 Ben Hutchings <b...@decadent.org.uk> > > On Tue, 2009-10-06 at 23:26 +0100, Antonio Marcos López Alonso > > > > wrote: > > > On Tue, Oct 6, 2009 at 1:26 AM, Ben Hutchings > > > > <b...@decadent.org.uk> > > > > > wrote: > > > > [...] > > > > > > Could you try adding 'noapic' to the kernel command line? > > > > > > Sure. Here is /proc/interrupts using irqpoll + noapic (yet > > > > no much time > > > > > has passed to reproduce the failure): > > > > [...] > > > > Do you mean this bug still occurs when you use 'noapic'? > > > > Ben. > > > > > > No, I mean I'm still waiting for the bug to occur. > > Excellent. > > > I will do it for around 72 hours (crossing fingers). Anyway, what is > > your opinion about what is happening? I guess this is not very common. > > I think that there may be a bug in the way the BIOS sets up the IO-APIC, > but I don't really understand what sorts of things can go wrong with > this. >
Still waiting :-). Googling around I found this bug is quite old: http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html And this: http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html It seems the fix is not the same for everyone. Supposing the only fix by now is a kernel option, should I close this bug? Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
