From: Jiri Masik <masik@pc203b.fzu.cz>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Occasional crash reports
Date: 14 Aug 2001 18:02:15 +0200 [thread overview]
Message-ID: <4vg0auiq9k.fsf@darbujan.fzu.cz> (raw)
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> So basically, the kernel tends to die in various locations where things
> should be just fine, but I did notice one thing: In most of these cases,
> I had softirq around in the backtrace (either running in softirqs, or
> having do_softirq() in the backtrace). There is one case where I didn't
> have it: it dies inside power_save(), so probably because an interrupt
> that happened just before messed things up.
>
> I'm wondering if we might be running into some stack overflow...
>
> Any clue ?
>
> Ben.
Hi,
I haven't observed any problem with recent kernels from your tree with
power supply. When running on battery kernel crashes soon (usually by
15 minutes). This is on my Pismo (March 2000) with 2.4.7-ben0. On the
second thought it might be related to USB as well as I'm not using
battery and USB mouse uncorrelated - IIRC one crash occurred inside
hc_interrupt. I'll rsync and see what's the current status.
cheers,
Jiri
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-14 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 16:02 Jiri Masik [this message]
2001-08-14 16:28 ` Occasional crash reports Benjamin Herrenschmidt
2001-08-14 16:45 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-08-18 11:16 Iain Sandoe
2001-08-20 2:51 ` Robert E Brose II
2001-08-18 1:28 Robert E Brose II
2001-08-14 13:03 Iain Sandoe
2001-08-14 9:45 Iain Sandoe
2001-08-14 12:18 ` Takashi Oe
2001-08-13 16:35 Benjamin Herrenschmidt
2001-08-14 2:59 ` Takashi Oe
2001-08-14 18:15 ` Mike Fedyk
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=4vg0auiq9k.fsf@darbujan.fzu.cz \
--to=masik@pc203b.fzu.cz \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).