Re: 3.12 kernels get stuck midway and do not get to gdm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2013-12-20 at 19:07 -0700, Chris Murphy wrote:
> On Dec 20, 2013, at 5:57 PM, Ankur Sinha <sanjay.ankur@xxxxxxxxx> wrote:
> 
> > Hi,
> > 
> > Is anyone else having trouble with 3.12 kernels?
> 
> 
> No problem for me with: 3.12.5-301.fc21.x86_64 or with  3.13.0-0.rc4.git0.1.fc21.x86_64.
> 
> > I don't have enough data to decide if it's a kernel issue or something
> > else, but it comes up with both 3.12 kernels. I've filed a bug here[1].
> > Should I give the 3.12 kernels negative karma for this?
> 
> If you don't have data knowing for sure it's the kernel, don't give the kernel negative karma. I'd say a problem must clearly be with kernel proper, or clearly with popular/necessary module or driver.

Aye. I haven't.

> 
> Could be dracut, could be udev, could be systemd… need to narrow it down.

I'm checking up their bugs too, to see if there's anything relevant. 

Add nouveau to that list :|
> 
> 
> > 
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1045662
> 
> I see a TON of NetworkManager and firewalld errors. 
> 
> What's this?

Well, it's a broadcom wireless chip. They've been improving support in
the kernel recently, but it could be a regression.

> 
> Dec 21 11:33:14 ankur-laptop kernel: b43: probe of bcma0:0 failed with error -524
> …
> Dec 21 11:33:15 ankur-laptop systemd-udevd[362]: renamed network interface wlan0 to wlp18s0
> …
> Dec 21 11:33:31 ankur-laptop firewalld[486]: 2013-12-21 11:33:31 ERROR: UNKNOWN_INTERFACE: wlp18s0
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
> Dec 21 11:33:31 ankur-laptop firewalld[486]: 2013-12-21 11:33:31 ERROR: UNKNOWN_INTERFACE: wlp18s0
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: <info> NetworkManager state is now CONNECTING
> Dec 21 11:33:31 ankur-laptop firewalld[486]: 2013-12-21 11:33:31 ERROR: UNKNOWN_INTERFACE: wlp18s0
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: <warn> (wlp18s0): add_pending_action (3): 'autoactivate' already added
> Dec 21 11:33:31 ankur-laptop firewalld[486]: 2013-12-21 11:33:31 ERROR: UNKNOWN_INTERFACE: wlp18s0
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: file devices/nm-device.c: line 6864 (nm_device_add_pending_action): should not be reached
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
> Dec 21 11:33:31 ankur-laptop firewalld[486]: 2013-12-21 11:33:31 ERROR: UNKNOWN_INTERFACE: wlp18s0
> Dec 21 11:33:31 ankur-laptop NetworkManager[629]: <warn> (wlp18s0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: wlp18s0
> 
> 
> I can't tell what firewalld is unhappy about. It could still be a wireless driver regression. danofsatx was having some wireless issues yesterday or day before, but I have no idea if that was instigated by a kernel change or not.
> 
> 
> Chris Murphy

I'll dig up more logs and stuff and see what's causing it. 
-- 
Thanks for your comments,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux