Launchpad has imported 12 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=524403.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-09-19T20:51:57+00:00 MartinG wrote: Description of problem: My system runs into a soft lockup after some time, seemingly at random, but it could be that it only happens after ~30 min of idling. The display goes blank, the monitor says "No signal", but I can still ssh into the machine. I am not able to wake it up by ctrl-alt-f2 or the like. "init 3" as root does not work, and I can't seem to kill any running programs (over ssh, as root - the shell never returns) In /var/log/messages I get: INFO: task events/0:9 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. events/0 D ffff88012de02024 0 9 2 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0 Call Trace: [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis] [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42 [<ffffffff81497366>] mutex_lock+0x43/0x71 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915] [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915] [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d [<ffffffff81070665>] kthread+0x6d/0xae [<ffffffff8101313a>] child_rip+0xa/0x20 [<ffffffff81012afd>] ? restore_args+0x0/0x30 [<ffffffff810705f8>] ? kthread+0x0/0xae [<ffffffff81013130>] ? child_rip+0x0/0x20 INFO: task events/0:9 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. events/0 D ffff88012de02024 0 9 2 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0 Call Trace: [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis] [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42 [<ffffffff81497366>] mutex_lock+0x43/0x71 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915] [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915] [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d [<ffffffff81070665>] kthread+0x6d/0xae [<ffffffff8101313a>] child_rip+0xa/0x20 [<ffffffff81012afd>] ? restore_args+0x0/0x30 [<ffffffff810705f8>] ? kthread+0x0/0xae [<ffffffff81013130>] ? child_rip+0x0/0x20 INFO: task events/0:9 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. events/0 D ffff88012de02024 0 9 2 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0 Call Trace: [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis] [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42 [<ffffffff81497366>] mutex_lock+0x43/0x71 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915] [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915] [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d [<ffffffff81070665>] kthread+0x6d/0xae [<ffffffff8101313a>] child_rip+0xa/0x20 [<ffffffff81012afd>] ? restore_args+0x0/0x30 [<ffffffff810705f8>] ? kthread+0x0/0xae [<ffffffff81013130>] ? child_rip+0x0/0x20 Version-Release number of selected component (if applicable): How reproducible: Always, random. Steps to Reproduce: 1. Leave the system idle. Additional info: http://www.smolts.org/client/show/pub_d59a227e-c82a-469a-94fb- 68b8de343818 00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03) # rpm -qa \*intel\* xorg-x11-drv-intel-2.7.0-7.fc11.x86_64 xorg-x11-drv-intel-debuginfo-2.7.0-4.fc11.x86_64 intel-gpu-tools-2.7.0-7.fc11.x86_64 xorg-x11-drv-intel-devel-2.7.0-7.fc11.x86_64 kernel-2.6.30.5-43.fc11.x86_64 # modinfo mantis filename: /lib/modules/2.6.30.5-43.fc11.x86_64/kernel/drivers/media/dvb/mantis/mantis.ko license: GPL author: Manu Abraham description: Mantis PCI DTV bridge driver srcversion: 1705C063CE013A7DAD9F6B0 alias: pci:v00001822d00004E35sv*sd*bc*sc*i* depends: ir-common,dvb-core,stv0299,i2c-core,stb0899,tda10023,tda10021,stb6100,mb86a16,lnbp21 vermagic: 2.6.30.5-43.fc11.x86_64 SMP mod_unload parm: adapter_nr:DVB adapter numbers (array of short) parm: verbose:verbose startup messages, default is 1 (yes) (int) The mantis driver is for the DVB-C card (digital TV card) that is in use on this media center pc. Is the bug in 1. the intel driver? 2. the mantis driver 3. the kernel? 4. ? (what is events/0:9?) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/0 ------------------------------------------------------------------------ On 2009-09-19T21:18:03+00:00 MartinG wrote: Related: https://bugzilla.redhat.com/show_bug.cgi?id=512615 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/1 ------------------------------------------------------------------------ On 2009-09-25T04:27:21+00:00 Chuck wrote: Can you get the output of sysrq-t when that happens? Just ssh in and do: # echo "t" >/proc/sysrq-trigger If the lockup messages are being logged that should be make it to the logs too. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/2 ------------------------------------------------------------------------ On 2009-09-26T16:41:47+00:00 MartinG wrote: Created attachment 362767 /var/log/messages Attached /var/log/messages after the display went dark, and I ssh'd into the machine, and issued the command above. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/3 ------------------------------------------------------------------------ On 2009-09-26T16:49:26+00:00 MartinG wrote: Contrary to what I stated above, I am in fact able to kill running programs - if I do "killall -9 X" I am able to log in as normal, and things seemingly work as it should. But this is not satisfactory workaround for the livingroom TV... ;) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/4 ------------------------------------------------------------------------ On 2009-09-26T19:31:47+00:00 MartinG wrote: Created attachment 362774 /var/log/messages again It happened again, after I had done "killall -9 X" and ran like normal for a while. The numbers in the log are a bit different, don't know if that could be helpful. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/5 ------------------------------------------------------------------------ On 2009-10-31T15:06:38+00:00 Mikolaj wrote: Created attachment 366934 /var/log/messages I had something similar, but with network device. My setup is: ifconfig eth0 up brctl addbr virbr0 brctl addif virbr0 eth0 ifconfig virbr0 172.16.0.1 netmask 255.255.255.0 up and to that bridge qemu-kvm virtual machines are added: cat /srv/kvm/qemu-ifup #!/bin/sh ... ifconfig "$1" up brctl addif virbr0 "$1" I was doing some testing of my new Gigabit switch and I was plugging in and plugging out Ethernet cable to/from eth0 (see my /var/log/messages) and then machine got unresponsive via second interface, wlan0. To bring the box back I've done alt+ctrl+del, as monitor didn't want to turn on. I'm not 100% sure, but that happened on 2.6.30.8-64.fc11.i686.PAE or earlier version. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/6 ------------------------------------------------------------------------ On 2009-10-31T15:08:29+00:00 Mikolaj wrote: Created attachment 366935 dmesg Here is my full dmesg, but with newer version of kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/7 ------------------------------------------------------------------------ On 2010-01-15T19:27:40+00:00 MartinG wrote: This bug report has been silent for a couple of months now, but the bug is still biting me every now and then. It happened just now, as I was watching a recording from my mediacenter, so it is not happening only when idling. Any more info I can provide, any tests I can do...? :) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/20 ------------------------------------------------------------------------ On 2010-01-27T09:58:14+00:00 Matthew wrote: Hi, I'm also seeing this bug daily in Fedora 12. It seems to duplicate the following bugs reported to LKML and Ubuntu: http://lkml.org/lkml/2009/1/11/70 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476 Note that LKML seems to imply that a patch was incorporated in 2.6.29 while feedback from Ubuntu is that the bug is still present in 2.6.31. My seeing the bug would seem to confirm that the issue is also still unfixed and present in fedora 12. Here is some sample output: Jan 27 00:55:29 hyperion kernel: INFO: task firefox:2624 blocked for more than 120 seconds. Jan 27 00:55:29 hyperion kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 27 00:55:29 hyperion kernel: firefox D 0000000000000002 0 2624 2062 0x00000000 Jan 27 00:55:29 hyperion kernel: ffff88008f125528 0000000000000086 ffff88008f1254a8 ffff880000000000 Jan 27 00:55:29 hyperion kernel: ffff88008f125498 ffffffff8104039a ffff8801fdce2f38 ffff880028066670 Jan 27 00:55:29 hyperion kernel: ffff8801fdce32c8 000000000000f8f0 ffff8801fdce32c8 0000000000015600 Jan 27 00:55:29 hyperion kernel: Call Trace: Jan 27 00:55:29 hyperion kernel: [<ffffffff8104039a>] ? account_group_exec_runtime+0x30/0x43 Jan 27 00:55:29 hyperion kernel: [<ffffffff8106e8e3>] ? clocksource_read+0xf/0x11 Jan 27 00:55:29 hyperion kernel: [<ffffffff8106acf2>] ? ktime_get_ts+0x4e/0x53 Jan 27 00:55:29 hyperion kernel: [<ffffffff810c154d>] ? sync_page+0x0/0x4a Jan 27 00:55:29 hyperion kernel: [<ffffffff8141bf53>] io_schedule+0x31/0x42 Jan 27 00:55:29 hyperion kernel: [<ffffffff810c1593>] sync_page+0x46/0x4a Jan 27 00:55:29 hyperion kernel: [<ffffffff8141c465>] __wait_on_bit+0x48/0x7b Jan 27 00:55:29 hyperion kernel: [<ffffffff8141bead>] ? thread_return+0x4e/0xc3 Jan 27 00:55:29 hyperion kernel: [<ffffffff810c1767>] wait_on_page_bit+0x72/0x79 Jan 27 00:55:29 hyperion kernel: [<ffffffff81067b70>] ? wake_bit_function+0x0/0x33 Jan 27 00:55:29 hyperion kernel: [<ffffffff810caeaf>] ? page_evictable+0x17/0x81 Jan 27 00:55:29 hyperion kernel: [<ffffffff810cbc41>] shrink_page_list+0x11d/0x5e0 Jan 27 00:55:29 hyperion kernel: [<ffffffff8109f40e>] ? delayacct_end+0x82/0x8d Jan 27 00:55:29 hyperion kernel: [<ffffffff8109f487>] ? __delayacct_blkio_end+0x3e/0x40 Jan 27 00:55:29 hyperion kernel: [<ffffffff81047f3f>] ? delayacct_blkio_end+0x21/0x41 Jan 27 00:55:29 hyperion kernel: [<ffffffff8141b565>] ? io_schedule_timeout+0x4d/0x58 Jan 27 00:55:29 hyperion kernel: [<ffffffff810d4f00>] ? congestion_wait+0x80/0x8f Jan 27 00:55:29 hyperion kernel: [<ffffffff81067b37>] ? autoremove_wake_function+0x0/0x39 Jan 27 00:55:29 hyperion kernel: [<ffffffff810cc725>] shrink_list+0x3b2/0x64a Jan 27 00:55:29 hyperion kernel: [<ffffffff810c85ae>] ? determine_dirtyable_memory+0x1a/0x2d Jan 27 00:55:29 hyperion kernel: [<ffffffff810c8637>] ? get_dirty_limits+0x27/0x24f Jan 27 00:55:29 hyperion kernel: [<ffffffff810ccc5d>] shrink_zone+0x2a0/0x32c Jan 27 00:55:29 hyperion kernel: [<ffffffff810cdd65>] do_try_to_free_pages+0x1ea/0x353 Jan 27 00:55:29 hyperion kernel: [<ffffffff810cdfc8>] try_to_free_pages+0x6e/0x70 Jan 27 00:55:29 hyperion kernel: [<ffffffff810cb68d>] ? isolate_pages_global+0x0/0x229 Jan 27 00:55:29 hyperion kernel: [<ffffffff810c770b>] __alloc_pages_nodemask+0x3d7/0x5b0 Jan 27 00:55:29 hyperion kernel: [<ffffffff810eb4e7>] alloc_pages_current+0x95/0x9e Jan 27 00:55:29 hyperion kernel: [<ffffffff810f295c>] alloc_slab_page+0x1b/0x28 Jan 27 00:55:29 hyperion kernel: [<ffffffff810f29bd>] new_slab+0x54/0x1d3 Jan 27 00:55:29 hyperion kernel: [<ffffffff810f2fe2>] __slab_alloc+0x1f1/0x3a1 Jan 27 00:55:29 hyperion kernel: [<ffffffffa002b1c2>] ? snd_ctl_ioctl+0x327/0x783 [snd] Jan 27 00:55:29 hyperion kernel: [<ffffffff810f3d34>] __kmalloc_track_caller+0x104/0x158 Jan 27 00:55:29 hyperion kernel: [<ffffffffa002b1c2>] ? snd_ctl_ioctl+0x327/0x783 [snd] Jan 27 00:55:29 hyperion kernel: [<ffffffff810d2b63>] memdup_user+0x29/0x68 Jan 27 00:55:29 hyperion kernel: [<ffffffffa002b1c2>] snd_ctl_ioctl+0x327/0x783 [snd] Jan 27 00:55:29 hyperion kernel: [<ffffffff811c2911>] ? avc_has_perm+0x5c/0x6e Jan 27 00:55:29 hyperion kernel: [<ffffffff81108d84>] vfs_ioctl+0x22/0x87 Jan 27 00:55:29 hyperion kernel: [<ffffffff8104907d>] ? finish_task_switch+0xc3/0xe6 Jan 27 00:55:29 hyperion kernel: [<ffffffff811092e0>] do_vfs_ioctl+0x47b/0x4c1 Jan 27 00:55:29 hyperion kernel: [<ffffffff8110937c>] sys_ioctl+0x56/0x79 Jan 27 00:55:29 hyperion kernel: [<ffffffff81011cf2>] system_call_fastpath+0x16/0x1b Note that there appears to be some sound system calls above in the trace, so I will look into switching sound card drivers for time being. I am currently using the following modules: [root@hyperion ~]# lsmod Module Size Used by rfcomm 71504 4 sco 19972 2 bridge 54112 0 stp 2724 1 bridge llc 6400 2 bridge,stp bnep 19472 2 l2cap 38992 16 rfcomm,bnep nfsd 277328 9 exportfs 4544 1 nfsd nfs 279952 1 lockd 71572 2 nfsd,nfs fscache 38856 1 nfs nfs_acl 3152 2 nfsd,nfs auth_rpcgss 41552 2 nfsd,nfs vmnet 45756 3 ppdev 10040 0 parport_pc 27640 0 parport 34320 2 ppdev,parport_pc vmblock 15032 1 vsock 43680 0 vmci 54936 1 vsock vmmon 78252 0 sunrpc 191912 16 nfsd,nfs,lockd,nfs_acl,auth_rpcgss ipv6 298928 62 p4_clockmod 6148 0 freq_table 4864 1 p4_clockmod speedstep_lib 5712 1 p4_clockmod uvcvideo 58972 0 videodev 36160 1 uvcvideo v4l1_compat 13892 2 uvcvideo,videodev snd_usb_audio 97200 2 v4l2_compat_ioctl32 10736 1 videodev snd_usb_lib 17664 1 snd_usb_audio snd_rawmidi 24032 1 snd_usb_lib snd_seq_device 7620 1 snd_rawmidi dm_multipath 17304 0 tcp_bic 4692 22 uinput 9248 0 btusb 18756 2 bluetooth 94884 12 rfcomm,sco,bnep,l2cap,btusb rfkill 20488 2 bluetooth nvidia 9624568 38 snd_hda_codec_realtek 281380 1 snd_hda_intel 30360 2 snd_hda_codec 72832 2 snd_hda_codec_realtek,snd_hda_intel e1000 115460 0 firewire_ohci 23332 0 snd_hwdep 9224 2 snd_usb_audio,snd_hda_codec snd_pcm 83144 3 snd_usb_audio,snd_hda_intel,snd_hda_codec iTCO_wdt 13008 0 i2c_i801 12800 0 iTCO_vendor_support 3588 1 iTCO_wdt firewire_core 47880 1 firewire_ohci asus_atk0110 12560 0 serio_raw 6644 0 shpchp 34636 0 snd_timer 22608 1 snd_pcm i2c_core 28976 3 videodev,nvidia,i2c_i801 joydev 11984 0 snd 67592 18 snd_usb_audio,snd_usb_lib,snd_rawmidi,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer crc_itu_t 2080 1 firewire_core soundcore 7328 1 snd snd_page_alloc 9568 2 snd_hda_intel,snd_pcm usb_storage 60496 0 [root@hyperion ~]# uname -a Linux hyperion.deploylinux.net 2.6.31.12-174.2.3.fc12.x86_64 #1 SMP Mon Jan 18 19:52:07 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/21 ------------------------------------------------------------------------ On 2010-04-28T10:28:55+00:00 Bug wrote: This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/28 ------------------------------------------------------------------------ On 2010-06-28T14:44:26+00:00 Bug wrote: Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/comments/29 ** Changed in: xserver-xorg-video-intel (Fedora) Status: Confirmed => Won't Fix ** Changed in: xserver-xorg-video-intel (Fedora) Importance: Unknown => High ** Bug watch added: Red Hat Bugzilla #512615 https://bugzilla.redhat.com/show_bug.cgi?id=512615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487185 Title: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/487185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
