Hi,
I'd like to ask for some assistance with 3.15-rc0.git kernels (for Rawhide).
Both 3.15 versions: kernel-3.15.0-0.rc0.git2.1.fc21.i686 kernel-3.15.0-0.rc0.git7.1.fc21.i686
do freeze my computer at graphical login screen. Booting kernel-3.14.0-1.fc21.i686 works okay.
Since my desktop completely freezes I can't anything like dmesg... Any clue?
On Fri, Apr 4, 2014 at 8:48 PM, Fidel Leon fidelleon@mykolab.com wrote:
Hi,
I'd like to ask for some assistance with 3.15-rc0.git kernels (for Rawhide).
Both 3.15 versions: kernel-3.15.0-0.rc0.git2.1.fc21.i686 kernel-3.15.0-0.rc0.git7.1.fc21.i686
do freeze my computer at graphical login screen. Booting kernel-3.14.0-1.fc21.i686 works okay.
Since my desktop completely freezes I can't anything like dmesg... Any clue?
Boot the broken kernel; wait for hang ... boot the working kernel do journalctl -b -1 -e and you should see the log of the failed boot.
On Friday 04 April 2014 21:09:46 drago01 wrote:
Both 3.15 versions: kernel-3.15.0-0.rc0.git2.1.fc21.i686 kernel-3.15.0-0.rc0.git7.1.fc21.i686
do freeze my computer at graphical login screen. Booting kernel-3.14.0-1.fc21.i686 works okay.
Since my desktop completely freezes I can't anything like dmesg... Any clue?
Boot the broken kernel; wait for hang ... boot the working kernel do journalctl -b -1 -e and you should see the log of the failed boot.
Unfortunately, it seems that "journalctl -b 1 -e" is showing the wrong boot log :(
Apr 02 01:15:21 lillinux systemd-shutdown[1]: Sending SIGTERM to remaining processes... Apr 02 01:15:21 lillinux systemd-journal[513]: Journal stopped
I rebooted to the bad kernels some moments ago, so it should be Apr 04 21:20 (CET).
By the way, I did a full journal dump to a text file and found a smoking gun... NetworkManager!
Apr 04 21:18:20 lillinux systemd[1]: Started User Manager for UID 997. Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: send auth to f8:8e:85:14:a9:58 (try 1/3) Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: scanning -> authenticating Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: authenticated Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: authenticating -> associating Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: associate with f8:8e:85:14:a9:58 (try 1/3) Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: RX AssocResp from f8:8e:85:14:a9:58 (capab=0x411 status=0 aid=1) Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: associated Apr 04 21:18:21 lillinux kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u1: link becomes ready Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: associating -> associated Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: associated -> 4-way handshake Apr 04 21:18:22 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: 4-way handshake -> group handshake Apr 04 21:18:22 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: group handshake -> completed Apr 04 21:18:22 lillinux NetworkManager[849]: <info> Activation (wlp0s29f7u1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'HANNUTEAM'. -- Reboot --
I have rebooted to the bad kernels with WiFi adapter removed and they boot okay! Of course, as soon as I plug my WiFi adapter back - rt2800- or reconfigure my wireless connection to use the non-used ipw2200... my laptop locks hard.
So, where would the bug report belong? NetworkManager or Kernel?
On Fri, Apr 4, 2014 at 9:49 PM, Fidel Leon fidelleon@mykolab.com wrote:
On Friday 04 April 2014 21:09:46 drago01 wrote:
Both 3.15 versions: kernel-3.15.0-0.rc0.git2.1.fc21.i686 kernel-3.15.0-0.rc0.git7.1.fc21.i686
do freeze my computer at graphical login screen. Booting kernel-3.14.0-1.fc21.i686 works okay.
Since my desktop completely freezes I can't anything like dmesg... Any clue?
Boot the broken kernel; wait for hang ... boot the working kernel do journalctl -b -1 -e and you should see the log of the failed boot.
Unfortunately, it seems that "journalctl -b 1 -e" is showing the wrong boot log :(
Yes because I said "journalctl -b -1 -e" that's not the same as "journalctl -b 1 -e" ... my command means "previous boot" yours mean "first boot (in the log)"
On Friday 04 April 2014 21:52:10 drago01 wrote:
Yes because I said "journalctl -b -1 -e" that's not the same as "journalctl -b 1 -e" ... my command means "previous boot" yours mean "first boot (in the log)"
Awww sorry, I copied your command reading it from my cell phone screen and didn't see the minus sign (and I'm new to Systemd's journaling) :(
BTW my problem holds true:
# journalctl -b -3 -e [...] Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: send auth to f8:8e:85:14:a9:58 (try 1/3) Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: scanning -> authenticating Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: authenticated Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: authenticating -> associating Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: associate with f8:8e:85:14:a9:58 (try 1/3) Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: RX AssocResp from f8:8e:85:14:a9:58 (capab=0x411 status=0 aid=1) Apr 04 21:18:21 lillinux kernel: wlp0s29f7u1: associated Apr 04 21:18:21 lillinux kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u1: link becomes ready Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: associating -> associated Apr 04 21:18:21 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: associated -> 4-way handshake Apr 04 21:18:22 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: 4-way handshake -> group handshake Apr 04 21:18:22 lillinux NetworkManager[849]: <info> (wlp0s29f7u1): supplicant interface state: group handshake -> completed Apr 04 21:18:22 lillinux NetworkManager[849]: <info> Activation (wlp0s29f7u1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'HANNUTEAM'. [EOF]
On 04.04.2014 20:48, Fidel Leon wrote:
Hi,
I'd like to ask for some assistance with 3.15-rc0.git kernels (for Rawhide).
Both 3.15 versions: kernel-3.15.0-0.rc0.git2.1.fc21.i686 kernel-3.15.0-0.rc0.git7.1.fc21.i686
do freeze my computer at graphical login screen. Booting kernel-3.14.0-1.fc21.i686 works okay.
Since my desktop completely freezes I can't anything like dmesg... Any clue?
kernel-3.15.0-0.rc0.git9.1.fc21.i686
https://www.kernel.org/doc/Documentation/networking/netconsole.txt http://kernelnewbies.org/KernelDebug # vi /etc/sysconfig/netconsole # chkconfig netconsole on
$ lspci [-v] $ lsusb [-t] https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=kerne...
poma
On Saturday 05 April 2014 08:47:00 poma wrote:
Since my desktop completely freezes I can't anything like dmesg... Any clue?
kernel-3.15.0-0.rc0.git9.1.fc21.i686
Just updated to such new kernel. System doesn't lock up anymore but... it's almost unusable (lightdm process takes so much CPU cycles the mouse jumps when moving it).
https://www.kernel.org/doc/Documentation/networking/netconsole.txt http://kernelnewbies.org/KernelDebug
Nice, will check them.
kernel@lists.fedoraproject.org
-
drago01 -
Fidel Leon -
poma