lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5232E294.9090909@t-online.de>
Date:	Fri, 13 Sep 2013 12:01:56 +0200
From:	Knut Petersen <Knut_Petersen@...nline.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Frederic Weisbecker <fweisbec@...il.com>, mingo@...nel.org,
	linux-kernel <linux-kernel@...r.kernel.org>, gcoady.lk@...il.com
Subject: [BUG] kernel panic during shutdown in run_timer_softirq()

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 ....

cu,
  Knut

Download attachment "shutdown-trace-2013-09-13.pdf" of type "application/pdf" (331076 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ