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: Fri, 09 Jan 2009 00:03:49 +0100 [thread overview]
Message-ID: <49668655.2010504@gmx.de> (raw)
In-Reply-To: <7d01f9f00901070338m4da2f915m707df8588a134dca@mail.gmail.com>
Thibaut VARENE wrote:
> On Tue, Jan 6, 2009 at 4:40 PM, Helge Deller <deller@gmx.de> wrote:
>
>> Yeah, valid question.
> ....
>> 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).
>
> The thing is that you have a machine with more than 4 LEDs. I have
> B180/B132s which have only 4 leds. Thus I won't notice anything when
> an Oops occurs. If you really don't want to have the old behaviour
> (which, again, I really found nice), how about having the heartbeat
> LED fixed when an oops occurs.
>
> Even better, a way to "reset" the state of the leds through /proc
> would solve both problems: an oops occurs, all/some leds flash/remain
> lit, you (try to) login, figure out the oops wasn't so serious, echo
> something > /proc/pdc/led and the LEDs start blinking normally again.
>
> Anyway, the key point here is that not all machines without LCD have
> more than 4 LEDs ;)
I think you are right. My b160L has 4 LEDs only as well.
So, just changing the "upper" 4 LEDs is the wrong way.
Then I was thinking to just check for the machine type or processor type
and make it dependend on that. No good idea either.
In the end, I think it's the fault of CONFIG_DEBUG_SPINLOCK.
If this is enabled, it just turns sets oops_in_progress=1 as soon as
a spinlock was wrong. Either way, if this happens something is
wrong, and the LEDs should flash.
That said, I think we should just drop my patch. If they all flash
as soon as an error happened this is just right.
In a normal productive system a bad spinlock shouldn't happen either, so
my patch just adds some unnecessary noise.
Helge
prev parent reply other threads:[~2009-01-08 23:03 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
2009-01-06 15:44 ` Helge Deller
2009-01-07 11:38 ` Thibaut VARENE
2009-01-08 23:03 ` Helge Deller [this message]
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=49668655.2010504@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.