Description of problem: After upgrading from 3.6 to 3.7, funny things suddenly began happening in one of my f17 systems: crashes at boot, before gdm is displayed. or during usage. Sometimes the colors look like the mess that is displayed in eog in fedora 18 for some pictures, sometimes. There is also a bug report for a similar problem (in that is the 3.7 kernel involved) on freedesktop.org but i can't find it now $ lspci -nn | grep VGA 00:0d.0 VGA compatible controller [0300]: nVidia Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) The kernel that crashed was: kernel-PAE-3.7.3-101.fc17.i686 Version-Release number of selected component (if applicable): $ rpm -q xorg-x11-drv-nouveau xorg-x11-drv-nouveau-0.0.16-37.20120306gitf5d1cd2.fc17.i686 How reproducible: randomly. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: for now there's no error in /var/log/messages or in Xorg.*.log . the system just freeezed. here are the last lines before the crash: Jan 29 23:10:55 logalhost fedora-storage-init[525]: [ OK ] Jan 29 23:10:55 logalhost systemd-fsck[582]: /dev/mapper/vg_logalhost-lv_home: recovering journal Jan 29 23:10:55 logalhost fedora-storage-init[586]: Setting up Logical Volume Management: 3 logical volume(s) in volume group "vg_logalhost" now active Jan 29 23:10:55 logalhost fedora-storage-init[586]: [ OK ] Jan 29 23:10:55 logalhost lvm[596]: 3 logical volume(s) in volume group "vg_logalhost" monitored Jan 29 23:10:55 logalhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
i've added the other bug report i've written today to the "See also" field. https://bugs.freedesktop.org/show_bug.cgi?id=60007
hmmm, i see nouveau problems on this video card too: $ lspci -nn | grep VGA 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) and this kernel : $ uname -a Linux localhost.localdomain 3.7.2-204.fc18.i686.PAE #1 SMP Wed Jan 16 16:31:26 UTC 2013 i686 i686 i386 GNU/Linux
Can I get kernel logs from after the issues occur please.
Created attachment 692212 [details] the locked system screen reproduction steps according to user are: open pidgin, enter yahoo account, select "Open inbox" from "Accounts". then this funny screen appears and system is dead: no keyboard, no mouse, no ssh. i'll attempt to add some configuration options for debugging, and check if i can get more out of this. right now in /var/log/messages and Xorg*.log i haven't found anything useful. i'll report back today everything i can, since tonight i had to leave for three weeks.
looking with meld at differences between Xorg.0.log (good, 3.6 kernel) and .old (supposedly bad, 3.7 kernel) i've noticed one line: [ 30.801] (II) [drm] nouveau interface version: 1.0.0 which, in .old is: [ 30.893] (II) [drm] nouveau interface version: 1.1.0 also, in /var/log/messages, the kernels that die have this lines: Feb 3 08:58:23 logalhost kernel: [ 93.625828] nouveau [ DRM] native mode from preferred Feb 3 08:58:39 logalhost goa[1585]: goa-daemon version 3.4.2 starting [main.c:112, main()] Feb 3 08:58:43 logalhost kernel: [ 113.339949] nouveau [ 1606] ib channel create, -22 and then system is locked, while on kernel where firefox starts fine is: Feb 3 09:05:57 logalhost dbus[715]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 3 09:06:15 logalhost goa[1578]: goa-daemon version 3.4.2 starting [main.c:112, main()] and that's it, firefox is up'n'running, system is alive. this time the kernel line is like this: # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.6.11-5.fc17.i686.PAE root=/dev/mapper/vg_logalhost-lv_root rd.md=0 rd.dm=0 KEYTABLE=us quiet rd.lvm.lv=vg_logalhost/lv_swap SYSFONT=latarcyrheb-sun16 rd.luks=0 rd.lvm.lv=vg_logalhost/lv_root LANG=en_US.UTF-8 ro rhgb drm.debug=14 log_buf_len=16M i'll attach the two Xorg logs, and tail -f /var/log/messages in both cases.
Created attachment 692213 [details] "good" Xorg log
Created attachment 692214 [details] "bad" Xorg.0.log
there is one problem with the Xorg.0.log.old: it is obtained afaict with a patched f18 kernel, but the behaviour is the same as the native f17 3.7.3 kernel.
Created attachment 692215 [details] no-crash messages
Created attachment 692216 [details] crash messages, f17 native kernel
Created attachment 692217 [details] crash messages, f18 patched kernel
Created attachment 692218 [details] 3.7.3 native kernel crash xorg log This is the native 3.7.3 f17 kernel xorg log
Looks like https://bugzilla.kernel.org/show_bug.cgi?id=50091.
yes, the similarity is amazing. i've also seen backtraces similar at least with the one you've posted there, but on geforce 7300. at some point i've also reported some kernel bugs on redhat's bugzilla, for those.
Created attachment 700166 [details] Xorg.0.log for NVIDIA GeForce 6100 For an NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) video device, X locks up after a few seconds for any kernel 3.7.x of current F18. The last working kernel is kernel-3.6.11-3.fc18. Even the latest F18 build kernel-3.7.9-201.fc18 is affected. Installed packages include: - libdrm-2.4.42-1.fc18 - mesa-libGL-9.0.1-4.fc18 - xorg-x11-drv-nouveau-1.0.6-4.fc18 - xorg-x11-server-Xorg-1.13.2-2.fc18
I've reported a similar bug 919259. It may be a duplicate of this bug. The last working kernel for me was kernel-3.6.11-5.fc17.x86_64. All 3.7 kernels fail.
Sorry, the correct that should read bug 912459.
I've had major problems since upgrading to F18 as well. Sometimes X will hang and not respond to input. Often it will eventually recover, but sometimes not. Various error messages from noveau appear in dmesg, see below for an example. My display adapter is: 01:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce 6200 TurboCache(TM)] (rev a1) dmesg errors: [ 7612.310528] nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 3 Get 0x016bde94 Put 0x00a5dd3c State 0x8002fa20 (err: INVALID_CMD) Push 0x00000000 [ 7612.310528] nouveau [ PGRAPH][0000:01:00.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 7612.310555] nouveau E[ PGRAPH][0000:01:00.0] ch 3 [0x00071000] subc 7 class 0x4497 mthd 0x1a10 data 0xffffffff [ 7612.310574] nouveau [ PGRAPH][0000:01:00.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 7612.310582] nouveau E[ PGRAPH][0000:01:00.0] ch 3 [0x00071000] subc 7 class 0x4497 mthd 0x1a14 data 0xffffffff [ 7612.310596] nouveau [ PGRAPH][0000:01:00.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 7612.310603] nouveau E[ PGRAPH][0000:01:00.0] ch 3 [0x00071000] subc 7 class 0x4497 mthd 0x1a18 data 0xffffffff [ 7645.279037] nouveau E[ 2240] failed to idle channel 0xcccc0000 [ 7645.326636] nouveau E[ DRM] reloc wait_idle failed: -16 [ 7645.326640] nouveau E[ DRM] reloc apply: -16 [ 7654.341044] nouveau E[ DRM] reloc wait_idle failed: -16 [ 7654.341048] nouveau E[ DRM] reloc apply: -16 [ 7684.348056] nouveau E[ DRM] reloc wait_idle failed: -16 [ 7684.348061] nouveau E[ DRM] reloc apply: -16 [ 7684.472058] nouveau [ DRM] 0xD117: Parsing digital output script table [ 7687.513363] nouveau E[ DRM] GPU lockup - switching to software fbcon [ 7687.518407] nouveau E[ DRM] reloc wait_idle failed: -16 [ 7687.518432] nouveau E[ DRM] reloc apply: -16 [ 7708.618048] nouveau E[ 1263] failed to idle channel 0xcccc0000 [ 7709.492569] nouveau [ DRM] 0xD117: Parsing digital output script table [ 7734.083458] nouveau [ DRM] 0xD117: Parsing digital output script table
Created attachment 714609 [details] Dmesg after errors on kernel 3.8.3 Retested after latest update to kernel 3.8.3. Same problems, bug still exists.
For the orginal system the bug was opened for, none of the 3.7 kernels worked. Same is true for the new 3.8.3-103 installed kernel. The system sometimes hanged before gdm, but it always fails when opening firefox and attempting some browsing. kernel-PAE-3.6.11-5.fc17.i686 still works decently. still, the system may hang before gdm, even with this kernel.
Issue still applies to a fully updated F19 system including kernel-3.9.0-301.fc19.
Tried kernel-PAE-3.9.8-100.fc17.i686, and it seems to work so far. Anyone else can confirm this? I may retry F18/19 x64 then that I've given up because of the same problem.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
if anyone has rights, please update version to f19 x32.
it seems that i have rights :) anyway, gnome-shell, in particular, has much less artifacts in 3.9.9 than in 3.9.5. but, when i was about to gladly report that 3.9.9 fixes the problem, it hapened again. the opening of firefox and yahoo and whatever sites the user opened, locked the system again. I attempted to switch to nvidia driver but for some reason this failed for me, although arobatino reported that it worked for him. so here we are: 3.(7,8,9) has broken support for nvidia 6150 se so i reverted to using some 3.6 kernel that i have luckily found in fedora 18 release directory.
(In reply to T-Gergely from comment #22) > Tried kernel-PAE-3.9.8-100.fc17.i686, and it seems to work so far. Anyone > else can confirm this? I may retry F18/19 x64 then that I've given up > because of the same problem. Wow, it has worked for 2 weeks. Now, it crashed while browsing with chromium. :(
Created attachment 783465 [details] dmesg after error on 3.10.4-300.fc19.i686.PAE after error
I'm seeing the same problem with Fedora 19 and a Nvidia GTX 660 card. The nouveau driver starts to spit out a constant stream of these errors after running fine for a random period of time. The only way to recover is to reboot the system. I avoided the issue in the past by running the binary nvidia drivers. [150073.332876] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 7 mthd 0x25fc data 0x3e4b4d65 [150073.332891] nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR [INVALID_VALUE] ch 4 [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa097 mthd 0x260c data 0x3dcc197f [150073.332904] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 7 mthd 0x2610 data 0x3e4b4d65 [150073.332917] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 7 mthd 0x2614 data 0x00000000 lspci for VGA: 01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1)
(In reply to Clinton Work from comment #28) > I'm seeing the same problem with Fedora 19 and a Nvidia GTX 660 card. > > The nouveau driver starts to spit out a constant stream of these errors > after running fine for a random period of time. The only way to recover is > to reboot the system. I avoided the issue in the past by running the binary > nvidia drivers. Completely unrelated issue. Please open a new bug report. For what it's worth, I've noted issues on GK106 related to multiple applications (X + a compositor would count, even without anything else) where the GPU can hang while context switching. It's on my plate to fix upstream. But, yeah, open the new bug and I'll track it for you there. Please provide a full dmesg log when you do :) > > > [150073.332876] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 > [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 > 7 mthd 0x25fc data 0x3e4b4d65 > [150073.332891] nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR [INVALID_VALUE] > ch 4 [0x027f7e0000 gnome-shell[2412]] subc > 0 class 0xa097 mthd 0x260c data 0x3dcc197f > [150073.332904] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 > [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 > 7 mthd 0x2610 data 0x3e4b4d65 > [150073.332917] nouveau E[ PGRAPH][0000:01:00.0] ILLEGAL_MTHD ch 4 > [0x027f7e0000 gnome-shell[2412]] subc 0 class 0xa09 > 7 mthd 0x2614 data 0x00000000 > > lspci for VGA: > 01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX > 660] (rev a1)
(In reply to georgy from comment #27) > Created attachment 783465 [details] > dmesg after error on 3.10.4-300.fc19.i686.PAE after error It's entirely possible your issue is related to AGP here. You can try nouveau.agpmode=0 as a workaround.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This can be reproduced on F22 with 4.1.8-200.fc22.i686+PAE. Last time it happened by just opening news.yahoo.com in Epiphany. But is not an always issue. However seems to happen more often if you watch a full screen video.
Created attachment 1081651 [details] nouveau crashes kernel - journal Attached the journalctl -alf log from latest crash. i believe the kernel was updated in the meantime.
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide. Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still happening on F24. I don't have the kernel version at hand but i think it's irrelevant. The bug was introduced back then and nobody ever took it out.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.