Felix Miata composed on 2015-02-02 17:23 (UTC-0500):
13.1 worked satisfactorily immediately, including NIC config retaining fixed IP on eth0.
13.2 spewed trap/segfault errors in a neverending stream virtually instantly in trying to boot from some cmdline config attempts. Many of the others ended in trap data, blinking keyboard LEDs and frozen screen claiming reboot would occur in 90 seconds.
The failsafe stanza provided boot, but during init many errors were spewed on tty1 among normal messages. Before I even thought to try failsafe, I chrooted from 13.1 to zypper up and update kernel from 3.16.6 to 3.16.7, then when that didn't help, TW's 3.18.3, also no help. I booted failsafe taking one more option off cmdline each time about 8 times until the only rescue options left were noresume and apm=off, so apm=off definitely functions to get a working boot, yet not without seeing the error stream on tty1. The last attempt without apm=off produced the frozen screen and keyboard condition.
I looked in the mailing list archives and Bugzilla, but didn't find anything I recognized as similar. Is there something journalctl can capture that can help someone help me figure out if this is a 13.2 bug that may have escaped discovery before now?
No improvement with 3.19.0 in TW. More segfault register data on tty1 than anything else until it settles a bit after around 33 seconds into boot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org