6:57 p.m.
Hi,
Is anyone else having trouble with 3.12 kernels? Both of them stop at
the Fedora bubble for me. They just stop. Here are screens-hots that I
took:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.31.27.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.32.22.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.34.07.jpg
It only saved journalctl logs for one of these failed boots:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/journalctl-previo...
It seems to stop at initrd.service starting up (line 1203).
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?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1045662
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
8:07 p.m.
On Dec 20, 2013, at 5:57 PM, Ankur Sinha <sanjay.ankur(a)gmail.com> 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.
Could be dracut, could be udev, could be systemd… need to narrow it down.
I see a TON of NetworkManager and firewalld errors.
What's this?
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
12:03 a.m.
On Fri, 2013-12-20 at 19:07 -0700, Chris Murphy wrote:
On Dec 20, 2013, at 5:57 PM, Ankur Sinha
<sanjay.ankur(a)gmail.com> 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
12:06 a.m.
On Fri, 2013-12-20 at 19:07 -0700, Chris Murphy wrote:
On Dec 20, 2013, at 5:57 PM, Ankur Sinha
<sanjay.ankur(a)gmail.com> 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
12:34 a.m.
On Sat, 2013-12-21 at 17:06 +1100, Ankur Sinha wrote:
I'll dig up more logs and stuff and see what's causing it.
It looks like a DRM issue
It booted into runlevel3 just fine, which pointed to an X related error.
This is what the Xorg log gave me:
egrep EE Xorg.1.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 19610.801] Initializing built-in extension MIT-SCREEN-SAVER
[ 19611.032] (EE) intel(0): [drm] failed to set drm interface version.
[ 19611.032] (EE) intel(0): Failed to become DRM master.
[ 19611.032] (EE) Screen(s) found, but none have a usable configuration.
[ 19611.032] (EE)
[ 19611.032] (EE) no screens found(EE)
[ 19611.032] (EE)
[ 19611.032] (EE) Please also check the log file at "/var/log/Xorg.1.log" for
additional information.
[ 19611.032] (EE)
[ 19611.038] (EE) Server terminated with error (1). Closing log file.
[asinha@ankur-laptop ~]$
The system hung up in a bit, even in run level 3, and I had to power it
off using the button. Here's a screenshot:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/drm-hangup.jpg
I'm guessing this confirms this to be a kernel/drm/nouveau issue? X
wouldn't cause the entire system to hang up in runlevel3? (I've checked
the kernel bug list and haven't found anything like this yet.) Any hints
on how I could collect more information on the issue?
Complete Xorg log is here:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/Xorg.1.log
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
4:22 p.m.
On Sat, 2013-12-21 at 17:34 +1100, Ankur Sinha wrote:
On Sat, 2013-12-21 at 17:06 +1100, Ankur Sinha wrote:
> I'll dig up more logs and stuff and see what's causing it.
It looks like a DRM issue
It booted into runlevel3 just fine, which pointed to an X related error.
This is what the Xorg log gave me:
> egrep EE Xorg.1.log
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 19610.801] Initializing built-in extension MIT-SCREEN-SAVER
> [ 19611.032] (EE) intel(0): [drm] failed to set drm interface version.
> [ 19611.032] (EE) intel(0): Failed to become DRM master.
> [ 19611.032] (EE) Screen(s) found, but none have a usable configuration.
> [ 19611.032] (EE)
> [ 19611.032] (EE) no screens found(EE)
> [ 19611.032] (EE)
> [ 19611.032] (EE) Please also check the log file at "/var/log/Xorg.1.log"
for additional information.
> [ 19611.032] (EE)
> [ 19611.038] (EE) Server terminated with error (1). Closing log file.
> [asinha@ankur-laptop ~]$
The system hung up in a bit, even in run level 3, and I had to power it
off using the button. Here's a screenshot:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/drm-hangup.jpg
I'm guessing this confirms this to be a kernel/drm/nouveau issue? X
wouldn't cause the entire system to hang up in runlevel3? (I've checked
the kernel bug list and haven't found anything like this yet.) Any hints
on how I could collect more information on the issue?
Complete Xorg log is here:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/Xorg.1.log
Well, it's dying in the intel driver, not nouveau...
I'd file a bug against xorg-x11-drv-intel either up or downstream, and
include the contents of 'dmesg' or the journal when booting with
'drm.debug=15' and reproducing the problem.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
11:02 p.m.
On 12/20/2013 09:57 PM, Ankur Sinha wrote:
Hi,
Is anyone else having trouble with 3.12 kernels? Both of them stop at
the Fedora bubble for me. They just stop. Here are screens-hots that I
took:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.31.27.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.32.22.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.34.07.jpg
It only saved journalctl logs for one of these failed boots:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/journalctl-previo...
It seems to stop at initrd.service starting up (line 1203).
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?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1045662
Hi Ankur,
Kernel 3.12.5-302.fc20.x86_64 works fine here (Dell Vostro 3500).
--
Germán A. Racca
Fedora Package Maintainer
https://fedoraproject.org/wiki/User:Skytux
11:42 p.m.
On 12/20/2013 09:02 PM, "Germán A. Racca" wrote:
On 12/20/2013 09:57 PM, Ankur Sinha wrote:
> Hi,
>
> Is anyone else having trouble with 3.12 kernels? Both of them stop at
> the Fedora bubble for me. They just stop. Here are screens-hots that I
> took:
>
> http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
> 2011.31.27.jpg
> http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
> 2011.32.22.jpg
> http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
> 2011.34.07.jpg
>
>
> It only saved journalctl logs for one of these failed boots:
> http://ankursinha.fedorapeople.org/kernel-3.12-failures/journalctl-previo...
>
>
>
> It seems to stop at initrd.service starting up (line 1203).
>
> 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?
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1045662
Hi Ankur,
Kernel 3.12.5-302.fc20.x86_64 works fine here (Dell Vostro 3500).
My rawhide tree shows 3.13 kernels and has for some time.....
--
Chuck Forsberg WA7KGX caf(a)omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
12:04 a.m.
On Sat, 2013-12-21 at 02:02 -0300, "Germán A. Racca" wrote:
Kernel 3.12.5-302.fc20.x86_64 works fine here (Dell Vostro 3500).
Ah. I'm on a vostro 3400. It's got both broadcom and nvidia chipsets
though (slightly customized).
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
12:06 a.m.
On Sat, 2013-12-21 at 02:02 -0300, "Germán A. Racca" wrote:
Kernel 3.12.5-302.fc20.x86_64 works fine here (Dell Vostro 3500).
Ah. I'm on a vostro 3400. It's got both broadcom and nvidia chipsets
though (slightly customized).
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
11:36 p.m.
On 12/20/2013 06:57 PM, Ankur Sinha wrote:
Hi,
Is anyone else having trouble with 3.12 kernels? Both of them stop at
the Fedora bubble for me. They just stop. Here are screens-hots that I
took:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.31.27.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.32.22.jpg
http://ankursinha.fedorapeople.org/kernel-3.12-failures/2013-12-21%
2011.34.07.jpg
It only saved journalctl logs for one of these failed boots:
http://ankursinha.fedorapeople.org/kernel-3.12-failures/journalctl-previo...
It seems to stop at initrd.service starting up (line 1203).
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?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1045662
I am booting fine with 3.12.5-301.fc20.x86_64 and nouveau, but I can't
even get to the password for the encrypted disks stage with
3.13.0-0.rc4.git1.1.fc21.x86_64. This issue is apparently fixed in rc5,
but that hasn't made it into rawhide yet.
--
Dan Mossor
Systems Engineer at Large
Fedora QA Team Volunteer FAS: dmossor IRC: danofsatx
San Antonio, Texas, USA
5:46 a.m.
I now have 3.12 running on my server and a test computer.
Yum update on my office computer doesn't see it yet ?/?
So far no problems booting up.
What should we be looking for in 3.12?
--
Chuck Forsberg WA7KGX caf(a)omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
3829
days inactive
3829
days old
11 comments
6 participants
participants (6)
-
"Germán A. Racca" -
Adam Williamson -
Ankur Sinha -
Chris Murphy -
Chuck Forsberg WA7KGX -
Dan Mossor