From: Helge Deller <deller@gmx.de>
To: Thibaut VARENE <varenet@parisc-linux.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: blink loadavg LEDs on Oops
Date: Tue, 06 Jan 2009 16:40:14 +0100 [thread overview]
Message-ID: <49637B5E.7010103@gmx.de> (raw)
In-Reply-To: <7d01f9f00901060728w2001ed38v15c305d1472cb66@mail.gmail.com>
Thibaut VARENE wrote:
> On Tue, Jan 6, 2009 at 2:23 PM, Helge Deller <deller@gmx.de> wrote:
>> - blink loadavg LEDs only (not all LEDs) twice a second on Oops
>
> Just out of curiosity, why wouldn't you want to have all leds blinking
> on something as serious as an Oops? I kind of liked to clearly see
> when something went wrong...
Yeah, valid question.
While doing some bugfixing on the HIL drivers I noticed that suddenly
all LEDs were lit on the 715/64. It was strange, as I still was using
the machine and it was running fine.
The reason why the LEDs were lit was, that oops_in_progress was set due
a bug in my code. In dmesg I saw:
BUG: rwlock cpu recursion on CPU#0, modprobe/1098, 00a1599c
Backtrace:
[<102a9c78>] _raw_write_lock+0x54/0x8c
....
So, whenever the kernel hits such a WARNING(), all LEDs will blink.
Now after my patch, the 4 LEDs on the left side blink (they are currently
not used anyway), while Heartbeat, disk-IO and LAN in/out still work
as usual. So, you will notice the 4 LEDs at once as well, but in addition
you still have the possibility to see if LAN goes in/out (e.g. if you ping
the machine) or if the heartbeat still works (and so your machine should
still be reachable).
Helge
next prev parent reply other threads:[~2009-01-06 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 13:23 [PATCH] parisc: blink loadavg LEDs on Oops Helge Deller
2009-01-06 15:28 ` Thibaut VARENE
2009-01-06 15:40 ` Helge Deller [this message]
2009-01-06 15:44 ` Helge Deller
2009-01-07 11:38 ` Thibaut VARENE
2009-01-08 23:03 ` Helge Deller
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=49637B5E.7010103@gmx.de \
--to=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=varenet@parisc-linux.org \
/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