Re: Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On 07/10/2010 03:22, brian m. carlson wrote: On Thu, Oct 07, 2010 at 01:53:27AM +0100, Ben Hutchings wrote: I can't reproduce your bug, so I can't answer any further questions that upstream has for you. If you don't wish to do that, I will simply close it and stop wasting your time. I'm not trying to be rude here. If you decide you want to forward it, I'm happy to be on the CC list so the fd.o maintainers can ask me questions if they need to. But it's not fair to users to force them to acquire huge numbers (at least 20 I can think of) of bugzilla accounts in order to report bugs in Debian. In general, I only take the time to forward bugs upstream when there's a specific patch that I really want to push. I am, unfortunately, unfamiliar with the DRI infrastructure and therefore will not be providing a patch in this case. If you want to close it, fine. There's nothing I can do to stop you. I figured the responsible thing to do was file a bug report instead of just complaining. The problem is that the Debian kernel team is too small and too short in free time to be able to handle upstream forwarding of bugs. They mainly focus into packaging new version and backporting upstream fix (and new drivers). Just doing that took a lot of time. So they 'require' user help when a new bug (not yet handled upstream) is found. Regards, Vincent (not at all in the Kernel Team) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4caded2b.3030...@free.fr
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
Package: linux-2.6 Version: 2.6.36~rc6-1~experimental.1 Severity: normal When browsing the web, I experienced a lockup of Xorg. It did not respond further (including to Ctrl-Alt-F1), but I was able to SSH in from another machine on the network. Killing Xorg was ineffective: the screen did not change. I rebooted the machine and found the following in the kernel log: Oct 6 19:26:19 lakeview kernel: [71400.520086] INFO: task Xorg:4165 blocked for more than 120 seconds. Oct 6 19:26:19 lakeview kernel: [71400.520092] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 6 19:26:19 lakeview kernel: [71400.520097] Xorg D 880037afe028 0 4165 1819 0x0044 Oct 6 19:26:19 lakeview kernel: [71400.520106] 8800988f4420 0082 88009dd01fd8 8800bcdd4af0 Oct 6 19:26:19 lakeview kernel: [71400.520115] 00014940 00014940 88009dd01fd8 00014940 Oct 6 19:26:19 lakeview kernel: [71400.520123] 00014940 8800988f46f8 8800988f4700 8800988f4420 Oct 6 19:26:19 lakeview kernel: [71400.520131] Call Trace: Oct 6 19:26:19 lakeview kernel: [71400.520144] [8130b66e] ? __mutex_lock_common+0x127/0x193 Oct 6 19:26:19 lakeview kernel: [71400.520151] [8130b7a6] ? mutex_lock+0x1a/0x33 Oct 6 19:26:19 lakeview kernel: [71400.520189] [a0670f93] ? i915_gem_fault+0x4b/0x17d [i915] Oct 6 19:26:19 lakeview kernel: [71400.520197] [810c8c9a] ? __do_fault+0x52/0x3f3 Oct 6 19:26:19 lakeview kernel: [71400.520206] [8103f7d9] ? default_wake_function+0x0/0xf Oct 6 19:26:19 lakeview kernel: [71400.520213] [810c9b6f] ? handle_mm_fault+0x427/0x9f4 Oct 6 19:26:19 lakeview kernel: [71400.520220] [81036ebe] ? __wake_up_sync_key+0x3f/0x57 Oct 6 19:26:19 lakeview kernel: [71400.520227] [812c1974] ? sk_wake_async+0x19/0x3c Oct 6 19:26:19 lakeview kernel: [71400.520234] [810f9fbb] ? pollwake+0x0/0x4e Oct 6 19:26:19 lakeview kernel: [71400.520240] [812c0664] ? unix_destruct_scm+0x6d/0x74 Oct 6 19:26:19 lakeview kernel: [71400.520248] [8130f54d] ? do_page_fault+0x2b9/0x2ce Oct 6 19:26:19 lakeview kernel: [71400.520255] [8130c915] ? page_fault+0x25/0x30 Oct 6 19:26:19 lakeview kernel: [71400.520264] [81193255] ? __copy_user_nocache+0x55/0xb8 Oct 6 19:26:19 lakeview kernel: [71400.520283] [a066ff55] ? i915_gem_pwrite_ioctl+0x1d1/0x5d7 [i915] Oct 6 19:26:19 lakeview kernel: [71400.520291] [81249372] ? __sock_recvmsg_nosec+0x29/0x69 Oct 6 19:26:19 lakeview kernel: [71400.520298] [8124bbee] ? sock_aio_read+0xb6/0xc5 Oct 6 19:26:19 lakeview kernel: [71400.520317] [a061d220] ? drm_ioctl+0x24e/0x322 [drm] Oct 6 19:26:19 lakeview kernel: [71400.520335] [a066fd84] ? i915_gem_pwrite_ioctl+0x0/0x5d7 [i915] Oct 6 19:26:19 lakeview kernel: [71400.520342] [810f91c8] ? do_vfs_ioctl+0x4a2/0x4ef Oct 6 19:26:19 lakeview kernel: [71400.520348] [810f9260] ? sys_ioctl+0x4b/0x6f Oct 6 19:26:19 lakeview kernel: [71400.520356] [810eceee] ? sys_read+0x5f/0x6b Oct 6 19:26:19 lakeview kernel: [71400.520363] [81008a02] ? system_call_fastpath+0x16/0x1b Oct 6 19:26:19 lakeview kernel: [71400.520380] INFO: task compiz:4322 blocked for more than 120 seconds. Oct 6 19:26:19 lakeview kernel: [71400.520384] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 6 19:26:19 lakeview kernel: [71400.520389] compizD 880037afe028 0 4322 4193 0x Oct 6 19:26:19 lakeview kernel: [71400.520396] 8800bb984420 0082 dead00200200 8800bd90b680 Oct 6 19:26:19 lakeview kernel: [71400.520404] 00014940 00014940 88009de37fd8 00014940 Oct 6 19:26:19 lakeview kernel: [71400.520411] 00014940 8800bb9846f8 8800bb984700 8800bb984420 Oct 6 19:26:19 lakeview kernel: [71400.520419] Call Trace: Oct 6 19:26:19 lakeview kernel: [71400.520426] [8130b66e] ? __mutex_lock_common+0x127/0x193 Oct 6 19:26:19 lakeview kernel: [71400.520445] [a066f1af] ? i915_gem_object_set_to_gtt_domain+0x8d/0x9c [i915] Oct 6 19:26:19 lakeview kernel: [71400.520452] [8130b7a6] ? mutex_lock+0x1a/0x33 Oct 6 19:26:19 lakeview kernel: [71400.520470] [a066efd0] ? i915_gem_busy_ioctl+0x4f/0xbf [i915] Oct 6 19:26:19 lakeview kernel: [71400.520487] [a061d220] ? drm_ioctl+0x24e/0x322 [drm] Oct 6 19:26:19 lakeview kernel: [71400.520505] [a066ef81] ? i915_gem_busy_ioctl+0x0/0xbf [i915] Oct 6 19:26:19 lakeview kernel: [71400.520512] [810f91c8] ? do_vfs_ioctl+0x4a2/0x4ef Oct 6 19:26:19 lakeview kernel: [71400.520519] [81064925] ? ktime_get_ts+0x66/0xab Oct 6 19:26:19 lakeview kernel: [71400.520525] [810f9260] ? sys_ioctl+0x4b/0x6f Oct 6 19:26:19 lakeview kernel: [71400.520531]
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Wed, 2010-10-06 at 19:59 +, brian m. carlson wrote: Package: linux-2.6 Version: 2.6.36~rc6-1~experimental.1 Severity: normal When browsing the web, I experienced a lockup of Xorg. It did not respond further (including to Ctrl-Alt-F1), but I was able to SSH in from another machine on the network. Killing Xorg was ineffective: the screen did not change. I rebooted the machine and found the following in the kernel log: [...] Please report this upstream at https://bugs.freedesktop.org under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Wed, Oct 06, 2010 at 10:38:48PM +0100, Ben Hutchings wrote: Please report this upstream at https://bugs.freedesktop.org under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. It's my opinion that the maintainers should forward bugs. I have no interest in yet another bugzilla account and with several papers that must be written *now* I simply don't have the time to forward bugs manually. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Thu, 2010-10-07 at 00:37 +, brian m. carlson wrote: On Wed, Oct 06, 2010 at 10:38:48PM +0100, Ben Hutchings wrote: Please report this upstream at https://bugs.freedesktop.org under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. It's my opinion that the maintainers should forward bugs. I have no interest in yet another bugzilla account and with several papers that must be written *now* I simply don't have the time to forward bugs manually. I can't reproduce your bug, so I can't answer any further questions that upstream has for you. If you don't wish to do that, I will simply close it and stop wasting your time. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Thu, Oct 07, 2010 at 01:53:27AM +0100, Ben Hutchings wrote: I can't reproduce your bug, so I can't answer any further questions that upstream has for you. If you don't wish to do that, I will simply close it and stop wasting your time. I'm not trying to be rude here. If you decide you want to forward it, I'm happy to be on the CC list so the fd.o maintainers can ask me questions if they need to. But it's not fair to users to force them to acquire huge numbers (at least 20 I can think of) of bugzilla accounts in order to report bugs in Debian. In general, I only take the time to forward bugs upstream when there's a specific patch that I really want to push. I am, unfortunately, unfamiliar with the DRI infrastructure and therefore will not be providing a patch in this case. If you want to close it, fine. There's nothing I can do to stop you. I figured the responsible thing to do was file a bug report instead of just complaining. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
