On 08/06/2012 06:51 μμ, Camaleón wrote: > On Fri, 08 Jun 2012 10:23:54 +0300, Panayiotis Karabassis wrote: > >> I was wondering, if anyone is into this kind of stuff: what kind of >> kernel programming bug can completely bring down the kernel and system? >> I am referring to a complete lockup: no screen output, no keyboard >> response, even with serial keyboard, not even the keyboard LEDs respond, >> no netconsole, no kernel panic, no crash dump, no messages in any log, >> it can't even be detected by NMI watchdog, and it doesn't trigger KDB >> (kernel debugger) if it is enabled. Just a freeze, that requires >> hardware reset. > How about ssh, is it still available? No, not even ping works... :-) > By the kind of symthoms you mention it could be hard kernel crash. Its > nature can be hard to debug, though, as it could be a software or > hardware problem. > >> I would say it's a hardware fault, except it's shared by many people, >> and the common denominator is the ath9k driver. A bug is reported [1] >> but I'd like to help solve it. >> >> Best regards, Panayiotis >> >> [1] https://bugzilla.kernel.org/show_bug.cgi?id=42903 > Well, you're in the best hands (kernel devels), they will tell you the > steps to debug the crash :-) > > Anyway, it usually helps to know the latest kernel version where the > system was running stable with no freezes; that can be a good point from > where to start debugging. Thanks, I hadn't thought of that. It's what I will try next. I just hope there is such a version, because the card is pretty new. > Greetings, > Thanks, best regards.
-- 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/4fd31d4c.2040...@gmail.com
