Bug ID 919836
Summary failsafe (nosmp) required to avoid unrecoverable kernel panic during boot
Classification openSUSE
Product openSUSE Distribution
Version 13.2
Hardware x86
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter mrmazda@earthlink.net
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Without selecting failsafe boot option, or otherwise including nosmp on
cmdline, boot either floods tty1 with a mix of normal and call traces
perpetually, or floods for a while, then announces automatic reboot in 90
seconds, which subsequently does not occur. To recover requires reset button or
power switch.

Initial opensuse-kernel mailing list post that generated no response except my
own follow-ups:
http://lists.opensuse.org/opensuse-kernel/2015-02/msg00003.html

Reproducible here only on one of more than 20 13.2 and Tumbleweed installations
on multiboot systems, of which only this and one other boot from or otherwise
use mdraid. The other raid system uses a slightly newer E7600 Wolfdale Core2Duo
on Intel 82801G/G31/NM10/ICH7 vs. this E6700 Conroe Core2Duo on Intel
82801HR/82P965/ICH8R. Knoppix 7.4.2/kernel 3.16.3 DVD, installed 13.1 with
3.11.x and 3.12.36, and TW with vanilla 3.19.0 work as expected. $SUBJECT
occurs with installed 3.16.x, 3.18.3, 3.18.6 and 3.19.0 desktop kernels on 13.2
and TW.

The system on which this occurs is my main LAN-server/web-server/everyday 24/7
system, so availability for testing is necessarily limited, and delay of
feedback requiring rebooting for data collection or testing is to be expected.


You are receiving this mail because: