From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
Cc: "Om N." <xhandle@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC : remote driver debugging efforts
Date: Sat, 12 Aug 2006 21:39:22 +0200 [thread overview]
Message-ID: <9a8748490608121239v63ea829eqc490ac8744677f93@mail.gmail.com> (raw)
In-Reply-To: <9a8748490608121235s6f3830b9yc9ab564599d77d07@mail.gmail.com>
On 12/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 12/08/06, Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:
> > On 8/10/06, Om N. <xhandle@gmail.com> wrote:
> > > (I do not have a remote power on/off switch. The driver panics so
> > > often that somebody has to babysit the machine to switch it off and
> > > on. We are in different time zones and things are not moving forward at all)
> >
> > two (or three) things I've done to help this, when I'm working remotely
> >
> > add panic=30 to your kernel options in grub (or echo 30 >
> > /proc/sys/kernel/panic) to reboot the system automatically on panic.
> >
> > set grub to automatically boot the safe kernel by default, and when
> > making a new kernel, set grub to boot it only once with (say your
> > default is 0 and the new kernel is 1 in grub)
> >
> > echo 'savedefault --default=1 --once' | grub --batch
> >
> > set up netconsole so that you can see the kernel messages (optional) on oops.
> >
> > finding out about all these was incredibly hard and obtuse :-) So
> > hope this helps.
>
> If you have remote access to the keyboard/display etc, for example via
> a network enabled KVM switch or similar, then magic sysrq can also be
> very helpful to remotely sync & unmount filesystems, and do emergency
> reboots... It can also be used to get stack dumps etc... Read
> Documentation/sysrq.txt for all the details.
>
> I'm not sure, but I think there was a patch floating around at one
> point that would let you trigger sysrq remotely over the network
> without even logging into the box or having remote keyboard access -
> could be very useful in your case although it is ofcourse extremely
> insecure.
>
One other thing, putting a watchdog card in the box to automatically
reboot it if the machine hangs would also be a good thing. If you
don't have (or don't want to buy) such a card, then building the
kernel with the software watchdog is better than nothing - there are
situations where it'll fail to reboot the machine that a real watchdog
card would be able to handle, but it's a lot better than nothing.
See; Device Drivers --> Character devices --> Watchdog Cards in menuconfig.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-08-12 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 6:19 Om N.
2006-08-12 18:43 ` Jesse Brandeburg
2006-08-12 19:35 ` Jesper Juhl
2006-08-12 19:39 ` Jesper Juhl [this message]
2006-08-12 22:50 ` Frederik Deweerdt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a8748490608121239v63ea829eqc490ac8744677f93@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xhandle@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®