Prev: Flash click problem
Next: (no subject)
From: Jochen Schulz on 30 Mar 2010 17:20 Camaleón: > On Tue, 30 Mar 2010 23:20:59 +0300, Dotan Cohen wrote: > >>> I cannot see any "panic" or "kernel oops" in that log. >>> >>> What is the exact behaviour are you seeing? >>> >> The machine is locking up and the keyboard leds flash. > > When the machine locks, try to access it via ssh. That won't work when the keyboard LEDs are flashing. That's a clear sign for a kernel panic. We just haven't seen the corresponding log messages, though. Maybe they don't make it to the syslog befor the kernel locks up. J. -- If I could travel in time I would show my minidisc to the Romans and become Caesar until the batteries ran out. [Agree] [Disagree] <http://www.slowlydownward.com/NODATA/data_enter2.html>
From: Camaleón on 30 Mar 2010 17:40 On Tue, 30 Mar 2010 23:19:29 +0200, Jochen Schulz wrote: > Camaleón: >>> The machine is locking up and the keyboard leds flash. >> >> When the machine locks, try to access it via ssh. > > That won't work when the keyboard LEDs are flashing. That's a clear sign > for a kernel panic. We just haven't seen the corresponding log messages, > though. Maybe they don't make it to the syslog befor the kernel locks > up. Then he could use a serial port and instruct kernel (at boot time) to log out there. I've done that one time, with a VM machine and another linux (openSUSE). What are the recommended steps to achieve this in Debian? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.03.30.21.37.06(a)gmail.com
From: Jochen Schulz on 30 Mar 2010 22:20 Camaleón: > > Then he could use a serial port and instruct kernel (at boot time) to log > out there. I've done that one time, with a VM machine and another linux > (openSUSE). > > What are the recommended steps to achieve this in Debian? /etc/inittab contains examples. (Legacy) Grub can be configured to work over a serial line, too. Don't know about grub-pc. J. -- I hate myself but have no clear idea why. [Agree] [Disagree] <http://www.slowlydownward.com/NODATA/data_enter2.html>
From: Dotan Cohen on 31 Mar 2010 13:10 > As a last resort buy a book on linux that covers the subject you want > answered. > That was quite what I asked: where could I read more on the subject? Dead trees are fine! -- Dotan Cohen http://bido.com http://what-is-what.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/x2q880dece01003311000r3f94fd73s513c19b01f191d2a(a)mail.gmail.com
From: Stephen Powell on 31 Mar 2010 14:10
On Wed, 31 Mar 2010 13:00:18 -0400 (EDT), Dotan Cohen wrote > Wayne wrote: >> As a last resort buy a book on linux that covers the subject you want >> answered. >> > > That was quite what I asked: where could I read more on the subject? > Dead trees are fine! I think I understand Dotan's point. I cut my teeth in the IBM mainframe environment. (And indeed, I still work in that environment.) In the historical IBM mainframe environment, there were messages manuals. *Every message* produced by the operating system, as well as IBM program products, was listed in a messages manual somewhere. It gave an explanation of the message, its fields, what it meant, and in the case of error messages, what to do about it. (Sometimes the "what to do about it" part was not too helpful, such as "correct the error and resubmit the job". But anyway ...) By contrast, most Linux messages are not documented anywhere, unless you call C source code documentation. Someone who comes from the mainframe environment experiences culture shock when he tries to look up a message. There's usually no place to look it up. Yes, you can search the internet, but often you find it in a post about an unrelated topic and the message is not explained. I don't think we're in Kansas anymore, Toto. -- .''`. Stephen Powell <zlinuxman(a)wowway.com> : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/640907089.363281270058423013.JavaMail.root(a)md01.wow.synacor.com |