From: Rob Landley <rob@landley.net>
To: Steven Cole <elenstev@mesatop.com>, linux-kernel@vger.kernel.org
Subject: Re: Suspend to disk panicked in -test9.
Date: Wed, 29 Oct 2003 23:33:06 -0600 [thread overview]
Message-ID: <200310292333.06470.rob@landley.net> (raw)
In-Reply-To: <200310291935.28554.elenstev@mesatop.com>
On Wednesday 29 October 2003 20:35, Steven Cole wrote:
> On Wednesday 29 October 2003 05:57 pm, Rob Landley wrote:
> > Unfortunately, while I was writing down the panic on a piece of paper,
> > the screen blanking code kicked in while I was still copying down the
> > register values. I remember that the call trace mentioned some variant
> > of a write_stuff_to_disk call, but that's not that useful...
> >
> > When is the last time that the screen blanking code actually accomplished
> > something useful? These days it seems to exist for the purpose of
> > destroying panic call traces and annoying people. (I seem to remember
> > that pressing a key used to make it come back, but now we're forced to
> > use the input core that no longer seems to be the case...)
> >
> > I also seem to remember a patch floating by on the list that would make
> > console screen blanking go away. I really think console screen blanking
> > NOT being enabled should be the default these days. Or at the very
> > least, when there's a panic it should get shut off. I'll add looking
> > into that to my to-do list, but will probably get to it somewhere around
> > 2009...
> >
> > Rob
>
> In the meantime, keeping a digital camera close by when testing is a
> low tech/high tech solution to this.
Very few McDonalds have a digital camera behind the register to loan out. I
was lucky they printed out some blank cash register paper for me to write the
panic down on. (Ordinarily, I take notes on my laptop...)
If this was easily reproducible, I'd recreate it at home under a serial
console. (Well, this being a "modern" laptop with no serial port, maybe I
could I could rig up a parallel port console or something. But the
principle's the same. No, don't ask me why this thing has no serial port but
does have a parallel port. Ask IBM.)
Does netconsole handle panics? (Would it work through a wireless card on an
internal cardbus? I also have a pcmcia 10baseT card around here somewhere I
could plug a some cat5 into, if I can get any untangled from the big ball of
miscelanous obsolete computer stuf in the "old parts" box. It's been a
couple months since I needed to reclaim anything that box, but I think I know
where I left it. I vaguely remember a friend asking me what an
unrecognizable component was... For the record, it was a 5 1/4 to 3.5 floppy
cable adapter...)
> Steven
Rob
next prev parent reply other threads:[~2003-10-30 5:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 0:57 Suspend to disk panicked in -test9 Rob Landley
2003-10-30 2:35 ` Steven Cole
2003-10-30 3:24 ` Zwane Mwaikambo
2003-10-30 5:43 ` Rob Landley
2003-10-30 6:03 ` Zwane Mwaikambo
2003-10-30 5:33 ` Rob Landley [this message]
2003-11-07 15:18 ` bill davidsen
2003-10-30 11:18 ` Felipe Alfaro Solana
2003-11-07 15:14 ` bill davidsen
2003-11-07 22:21 ` Valdis.Kletnieks
2003-11-10 19:15 ` Bill Davidsen
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=200310292333.06470.rob@landley.net \
--to=rob@landley.net \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.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