From: Frederic Weisbecker <fweisbec@gmail.com>
To: Knut Petersen <Knut_Petersen@t-online.de>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
mingo@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
gcoady.lk@gmail.com
Subject: Re: [BUG] kernel panic during shutdown in run_timer_softirq()
Date: Fri, 13 Sep 2013 14:20:14 +0200 [thread overview]
Message-ID: <20130913122012.GA4844@somewhere> (raw)
In-Reply-To: <5232E294.9090909@t-online.de>
On Fri, Sep 13, 2013 at 12:01:56PM +0200, Knut Petersen wrote:
> Hi everybody!
>
> Since about July I observe occasional kernel panics happening only during system shutdown on two systems.
>
> Hardware: mobos: both AOpen i915GMm-hfs mobos, cpus: Pentium-M Dothan / Banias, mem: 2GB
> Although the stack traces differ, there is one thing in common: CS:EIP is in run_timer_softirq().
>
> A first report was posted to lkml on 2013-07-10: http://www.gossamer-threads.com/lists/linux/kernel/1744892?#1744892
> jpg of the stack trace: http://www.gossamer-threads.com/lists/engine?do=post_attachment;postatt_id=57017;list=linux
>
> There were several reports of kernel panics with run_timer_softirq() in the call_trace.
>
> @Grant: You reported a kernel panic during shutdown for kernel 3.7.5, but the jpg is not accessible.
> Could you please verify if your report is related?
>
> The problem is still present in yesterdays git master, see attached stacktrace.
> A shortened transcription of that stacktrace:
>
> Bug: unable to handle kernel paging request at ...
> [...]
> Call Trace:
> __do_softirq+[...]
> irq_exit+[...]
> smp_apic_timer_interrupt+[...]
> apic_timer_interrupt+[...]
> ?default_idle+[...]
> ?clocksource_mark_unstable+[...]
> ?default_idle+[...]
> arch_cpu_idle+[...]
> cpu_startup_entry+[...]
> rest_init+[...]
> start_kernel+[...]
> i386_start_kernel+[...]
> [...]
> EIP: run_timer_softirq+[...]
> Kernel panic panic - not syncing: Fatal exception in interrupt
>
> Any idea how to debug that problem? Insert some debugging code and constantly rebooting one of the
> machines would be an option, but I don´t have a clue what to insert ....
Adding Thomas, in case he has a clue.
Thanks.
prev parent reply other threads:[~2013-09-13 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 10:01 [BUG] kernel panic during shutdown in run_timer_softirq() Knut Petersen
2013-09-13 12:20 ` Frederic Weisbecker [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=20130913122012.GA4844@somewhere \
--to=fweisbec@gmail.com \
--cc=Knut_Petersen@t-online.de \
--cc=gcoady.lk@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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