On Thu, 22 Mar 2012 14:14:53 -0500, Mark Copper wrote: > On Thu, Mar 22, 2012 at 12:24 PM, Camaleón <noela...@gmail.com> wrote:
(...) >> I wonder if you already have tried what the message suggests :-? >> >> > I don't know about the original poster, but booting with irqpoll did not > solve the problem for me. (I may have included this in my post to this > list around March of last year). Trying won't hurt. >> In addition, consider in opening a bug report if the above does not >> make any difference. > > I found numerous bug reports stemming from this type of problem around > the net, none resolved. So I think the problems are generally > idiosyncratic and between device and kernel. And, sorry to repeat, the > best help seems to come from kernel people if you can get their > attention. One's chances of that are better if one provides info > regarding one's hardware and a listing of the devices using the IRQ. > > Hoping my travails may be of some benefit, Yup, I would send a bug report against the kernel package (linux-image-*) because of the trace. And true is that devels in that "department" are fast as hell... Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jki5s9$ld4$6...@dough.gmane.org
