From: "" <simon@baydel.com>
To: "Peter Wächtler" <pwaechtler@loewe-komp.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panic output
Date: Mon, 17 Dec 2001 13:47:15 -0000 [thread overview]
Message-ID: <3C1DF763.28186.17B69A0@localhost> (raw)
In-Reply-To: <3C1DF9AD.1DFEB1B@loewe-komp.de>
I have tried the console only method and this does not work either.
Perhaps I sould add some more information about the panic. This
card is a FC board and there was a bug in the hardware which
caused invalid frame reception. When this happens the driver is
interrupted and goes off to have a look at the frame. It sorts ou the
hardware and continues. Initially I was just dumping part of the
frame and the system continued and all was ok. I decided in
certain circumstances this would not be a good idea so I inserted
the panic. At this stage I get the hang or reboot depending how I
set /proc/sys/kernel/panic. I guess if this is set to 0 the hang
should be a screen oops message ?
I get the impression from the responses that panic does not aways
work, is that correct ?
At this point the hardware is all ok and can be made to continue
running all that has happened is some isolated event internal to a
PCI card.
I will try the serial line.
Many Thanks
Simon.
On 17 Dec 2001, at 14:57, Peter Wächtler wrote:
> simon@baydel.com schrieb:
> >
> > During writing a driver for a PCI board I experienced the hardware
> > hanging and I had to press the big red button. The hang was traced
> > using a PCI analyzer and I found that the driver, loaded as a
> > module, was taking a route which called panic. I changed
> > /proc/sys/kernel/panic to a non zero value and the machine started
> > to reboot on PCI hang. My problem is I never see any output on the
> > screen or in /var/log/messages. All the stuff I have looked at in
> > /usr/src/linux/Documentation suggests the messages should be
> > here. I am running a 2.4.0 kernel with a SuSE 7.1 installation. At
> > the hang time the system is running kde 2 and in a command
> > winow I have a tail -f /var/log/messages running. The first change I
> > see is the PC bios startup.
> >
>
> First: try to start your driver from the console.
> There you should see the panic message.
>
> Then look at Documentation/serial-console.txt and hook up a serial
> console to your box
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
next prev parent reply other threads:[~2001-12-18 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 9:57 Panic output simon
2001-12-17 13:57 ` Peter Wächtler
2001-12-17 13:47 ` simon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-17 14:24 willy tarreau
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=3C1DF763.28186.17B69A0@localhost \
--to=simon@baydel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pwaechtler@loewe-komp.de \
/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.