[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
No, Compiz is not enabled. -- Resume fails with fglrx due to ASIC hang with dual-head configuration https://bugs.launchpad.net/bugs/308964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
** Description changed: Ubuntu Version: 8.10 xorg-driver-fglrx Version: 8.543 GFX Card: ATI Radeon Xpress 1250 Resume fails when using the attached xorg dual-head configuration - without an external monitor connected. I have enable Randr 1.2 support + without an external monitor connected. I have enabled Randr 1.2 support with the following command because otherwise X would not even be able to start without an external monitor connected. aticonfig --set-pcs-str=DDX,EnableRandr12,TRUE No password prompt appears and the following dump is written to /var/log/kern.log. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713011] [fglrx] ASIC hang happens. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713023] Pid: 5823, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713047] [f8cb8c2d] KCL_dump_stack+0xd/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713117] [f8ccd49c] firegl_hardwareHangRecovery+0x1c/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713180] [f8d4cceb] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713256] [f8cb7c18] ? KAS_GetTickCounter+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713301] [f8d4cc87] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713375] [f8d51d16] _ZN6AsicR616ASICIdleInternalEN4Asic15idle_WaitMethodE+0x96/0x1f0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713450] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713504] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713570] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713623] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713688] [c014f082] ? update_wall_time+0x442/0x890 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713698] [f8d296b6] ? QSSubmitList+0x56/0x170 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713775] [f8d4b42c] _ZN4Asic7PM4idleENS_15idle_WaitMethodE+0x4c/0x80 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713849] [f8d44565] _ZN15QS_PRIVATE_CORE7PM4idleEN4Asic15idle_WaitMethodE+0x35/0x70 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713930] [f8d31f11] _ZN10QS_PRIVATE11synchronizeEv+0x31/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714000] [f8d297e7] QSSynchronize+0x17/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714067] [f8d32bd9] _Z14uQSSynchronizej+0x19/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714136] [f8d3ab4b] _Z8uCWDDEQCjjjPvjS_+0x3db/0x1260 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714207] [f8d28cd4] CMMQS_uCWDDEQC+0x34/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714274] [f8ceb202] firegl_cmmqs_CWDDE_32+0x402/0x4b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714324] [c02548ca] copy_from_user+0x3a/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714330] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714343] [f8ce998d] firegl_cmmqs_CWDDE32+0x8d/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714409] [c0211bf2] cap_capable+0x12/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714419] [c013a828] capable+0x18/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714426] [f8ce9900] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714481] [f8cc8577] firegl_ioctl+0x227/0x2b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714523] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714543] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714548] [c037c999] schedule+0x429/0x790 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714558] [f8cbcafe] ip_firegl_ioctl+0x1e/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714598] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714602] [c01beef1] vfs_ioctl+0x81/0x90 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714606] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714610] [c01bf086] do_vfs_ioctl+0x66/0x1f0 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714614] [c02549fb] copy_to_user+0x3b/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714618] [c02147d8] cap_file_ioctl+0x8/0x10 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714624] [c01bf27b] sys_ioctl+0x6b/0x70 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714628] [c0103f7b] sysenter_do_call+0x12/0x2f Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714632]
[Bug 308964] [NEW] Resume fails with fglrx due to ASIC hang with dual-head configuration
Public bug reported: Ubuntu Version: 8.10 xorg-driver-fglrx Version: 8.543 GFX Card: ATI Radeon Xpress 1250 Resume fails when using the attached xorg dual-head configuration without an external monitor connected. I have enable Randr 1.2 support with the following command because otherwise X would not even be able to start without an external monitor connected. aticonfig --set-pcs-str=DDX,EnableRandr12,TRUE No password prompt appears and the following dump is written to /var/log/kern.log. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713011] [fglrx] ASIC hang happens. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713023] Pid: 5823, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713047] [f8cb8c2d] KCL_dump_stack+0xd/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713117] [f8ccd49c] firegl_hardwareHangRecovery+0x1c/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713180] [f8d4cceb] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713256] [f8cb7c18] ? KAS_GetTickCounter+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713301] [f8d4cc87] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713375] [f8d51d16] _ZN6AsicR616ASICIdleInternalEN4Asic15idle_WaitMethodE+0x96/0x1f0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713450] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713504] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713570] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713623] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713688] [c014f082] ? update_wall_time+0x442/0x890 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713698] [f8d296b6] ? QSSubmitList+0x56/0x170 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713775] [f8d4b42c] _ZN4Asic7PM4idleENS_15idle_WaitMethodE+0x4c/0x80 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713849] [f8d44565] _ZN15QS_PRIVATE_CORE7PM4idleEN4Asic15idle_WaitMethodE+0x35/0x70 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713930] [f8d31f11] _ZN10QS_PRIVATE11synchronizeEv+0x31/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714000] [f8d297e7] QSSynchronize+0x17/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714067] [f8d32bd9] _Z14uQSSynchronizej+0x19/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714136] [f8d3ab4b] _Z8uCWDDEQCjjjPvjS_+0x3db/0x1260 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714207] [f8d28cd4] CMMQS_uCWDDEQC+0x34/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714274] [f8ceb202] firegl_cmmqs_CWDDE_32+0x402/0x4b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714324] [c02548ca] copy_from_user+0x3a/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714330] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714343] [f8ce998d] firegl_cmmqs_CWDDE32+0x8d/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714409] [c0211bf2] cap_capable+0x12/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714419] [c013a828] capable+0x18/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714426] [f8ce9900] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714481] [f8cc8577] firegl_ioctl+0x227/0x2b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714523] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714543] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714548] [c037c999] schedule+0x429/0x790 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714558] [f8cbcafe] ip_firegl_ioctl+0x1e/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714598] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714602] [c01beef1] vfs_ioctl+0x81/0x90 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714606] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714610] [c01bf086] do_vfs_ioctl+0x66/0x1f0 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714614] [c02549fb] copy_to_user+0x3b/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714618] [c02147d8] cap_file_ioctl+0x8/0x10 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714624] [c01bf27b] sys_ioctl+0x6b/0x70 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714628] [c0103f7b] sysenter_do_call+0x12/0x2f Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714632] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714637] === Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714642]
[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
** Attachment added: xorg.conf http://launchpadlibrarian.net/20496349/xorg.conf -- Resume fails with fglrx due to ASIC hang with dual-head configuration https://bugs.launchpad.net/bugs/308964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294713] Re: Resume fails with fglrx due to ASIC hang on Samsung R20
*** This bug is a duplicate of bug 308964 *** https://bugs.launchpad.net/bugs/308964 ** This bug has been marked a duplicate of bug 308964 Resume fails with fglrx due to ASIC hang with dual-head configuration -- Resume fails with fglrx due to ASIC hang on Samsung R20 https://bugs.launchpad.net/bugs/294713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
** Attachment added: lspci.log http://launchpadlibrarian.net/20496380/lspci.log -- Resume fails with fglrx due to ASIC hang with dual-head configuration https://bugs.launchpad.net/bugs/308964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/20496406/Xorg.0.log -- Resume fails with fglrx due to ASIC hang with dual-head configuration https://bugs.launchpad.net/bugs/308964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 308964] Re: Resume fails with fglrx due to ASIC hang with dual-head configuration
** Attachment added: kern.log http://launchpadlibrarian.net/20496375/kern.log -- Resume fails with fglrx due to ASIC hang with dual-head configuration https://bugs.launchpad.net/bugs/308964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87317] Re: Screensaver just detects idle time on one screen
I can confirm this issue with ubuntu 8.10 (upgraded all the way from 7.04). -- Screensaver just detects idle time on one screen https://bugs.launchpad.net/bugs/87317 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294713] Re: Resume fails with fglrx due to ASIC hang on Samsung R20
** Attachment added: kern.log http://launchpadlibrarian.net/19427870/kern.log -- Resume fails with fglrx due to ASIC hang on Samsung R20 https://bugs.launchpad.net/bugs/294713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294713] [NEW] Resume fails with fglrx due to ASIC hang on Samsung R20
Public bug reported: Ubuntu Version: 8.10 xorg-driver-fglrx Version: 8.543 GFX Card: ATI Radeon Xpress 1250 After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume stopped working on my Samsung R20 notebook. The notebook suspends fine but when trying to resume the screen just flickers for a moment and becomes a bit brighter. With Ctrl+Alt+Del I'm still able to reboot. I also tried downgrading to the 2.6.27-7.14 kernel but resume has stopped working with that kernel too. In the attached kern.log I found fglrx-dumps such as this one: Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713011] [fglrx] ASIC hang happens. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713023] Pid: 5823, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713047] [f8cb8c2d] KCL_dump_stack+0xd/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713117] [f8ccd49c] firegl_hardwareHangRecovery+0x1c/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713180] [f8d4cceb] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713256] [f8cb7c18] ? KAS_GetTickCounter+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713301] [f8d4cc87] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713375] [f8d51d16] _ZN6AsicR616ASICIdleInternalEN4Asic15idle_WaitMethodE+0x96/0x1f0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713450] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713504] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713570] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713623] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713688] [c014f082] ? update_wall_time+0x442/0x890 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713698] [f8d296b6] ? QSSubmitList+0x56/0x170 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713775] [f8d4b42c] _ZN4Asic7PM4idleENS_15idle_WaitMethodE+0x4c/0x80 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713849] [f8d44565] _ZN15QS_PRIVATE_CORE7PM4idleEN4Asic15idle_WaitMethodE+0x35/0x70 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713930] [f8d31f11] _ZN10QS_PRIVATE11synchronizeEv+0x31/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714000] [f8d297e7] QSSynchronize+0x17/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714067] [f8d32bd9] _Z14uQSSynchronizej+0x19/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714136] [f8d3ab4b] _Z8uCWDDEQCjjjPvjS_+0x3db/0x1260 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714207] [f8d28cd4] CMMQS_uCWDDEQC+0x34/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714274] [f8ceb202] firegl_cmmqs_CWDDE_32+0x402/0x4b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714324] [c02548ca] copy_from_user+0x3a/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714330] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714343] [f8ce998d] firegl_cmmqs_CWDDE32+0x8d/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714409] [c0211bf2] cap_capable+0x12/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714419] [c013a828] capable+0x18/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714426] [f8ce9900] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714481] [f8cc8577] firegl_ioctl+0x227/0x2b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714523] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714543] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714548] [c037c999] schedule+0x429/0x790 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714558] [f8cbcafe] ip_firegl_ioctl+0x1e/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714598] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714602] [c01beef1] vfs_ioctl+0x81/0x90 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714606] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714610] [c01bf086] do_vfs_ioctl+0x66/0x1f0 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714614] [c02549fb] copy_to_user+0x3b/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714618] [c02147d8] cap_file_ioctl+0x8/0x10 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714624] [c01bf27b] sys_ioctl+0x6b/0x70 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714628] [c0103f7b] sysenter_do_call+0x12/0x2f Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714632] [c01c64a6] d_materialise_unique+0x156/0x370
[Bug 294713] Re: Resume fails with fglrx due to ASIC hang on Samsung R20
** Attachment added: lspci.log http://launchpadlibrarian.net/19427872/lspci.log -- Resume fails with fglrx due to ASIC hang on Samsung R20 https://bugs.launchpad.net/bugs/294713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294713] Re: Resume fails with fglrx due to ASIC hang on Samsung R20
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/19427883/Xorg.0.log ** Description changed: Ubuntu Version: 8.10 xorg-driver-fglrx Version: 8.543 GFX Card: ATI Radeon Xpress 1250 After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume stopped working on my Samsung R20 notebook. The notebook suspends fine but when trying to resume the screen just flickers for a moment and becomes a bit brighter. With Ctrl+Alt+Del I'm still able to reboot. I also tried downgrading to the 2.6.27-7.14 kernel but resume has stopped working with that kernel too. - In the attached kern.log I found the dumps such as the following: + In the attached kern.log I found fglrx-dumps such as this one: + Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713011] [fglrx] ASIC hang happens. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713023] Pid: 5823, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713047] [f8cb8c2d] KCL_dump_stack+0xd/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713117] [f8ccd49c] firegl_hardwareHangRecovery+0x1c/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713180] [f8d4cceb] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713256] [f8cb7c18] ? KAS_GetTickCounter+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713301] [f8d4cc87] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713375] [f8d51d16] _ZN6AsicR616ASICIdleInternalEN4Asic15idle_WaitMethodE+0x96/0x1f0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713450] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713504] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713570] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713623] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713688] [c014f082] ? update_wall_time+0x442/0x890 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713698] [f8d296b6] ? QSSubmitList+0x56/0x170 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713775] [f8d4b42c] _ZN4Asic7PM4idleENS_15idle_WaitMethodE+0x4c/0x80 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713849] [f8d44565] _ZN15QS_PRIVATE_CORE7PM4idleEN4Asic15idle_WaitMethodE+0x35/0x70 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713930] [f8d31f11] _ZN10QS_PRIVATE11synchronizeEv+0x31/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714000] [f8d297e7] QSSynchronize+0x17/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714067] [f8d32bd9] _Z14uQSSynchronizej+0x19/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714136] [f8d3ab4b] _Z8uCWDDEQCjjjPvjS_+0x3db/0x1260 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714207] [f8d28cd4] CMMQS_uCWDDEQC+0x34/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714274] [f8ceb202] firegl_cmmqs_CWDDE_32+0x402/0x4b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714324] [c02548ca] copy_from_user+0x3a/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714330] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714343] [f8ce998d] firegl_cmmqs_CWDDE32+0x8d/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714409] [c0211bf2] cap_capable+0x12/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714419] [c013a828] capable+0x18/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714426] [f8ce9900] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714481] [f8cc8577] firegl_ioctl+0x227/0x2b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714523] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714543] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714548] [c037c999] schedule+0x429/0x790 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714558] [f8cbcafe] ip_firegl_ioctl+0x1e/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714598] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714602] [c01beef1] vfs_ioctl+0x81/0x90 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714606] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714610] [c01bf086] do_vfs_ioctl+0x66/0x1f0 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714614] [c02549fb] copy_to_user+0x3b/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714618] [c02147d8] cap_file_ioctl+0x8/0x10 Nov 6 13:28:04
[Bug 294713] Re: Resume fails with fglrx due to ASIC hang on Samsung R20
** Description changed: Ubuntu Version: 8.10 xorg-driver-fglrx Version: 8.543 GFX Card: ATI Radeon Xpress 1250 - After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume - stopped working on my Samsung R20 notebook. The notebook suspends fine - but when trying to resume the screen just flickers for a moment and - becomes a bit brighter. With Ctrl+Alt+Del I'm still able to reboot. + Important Update: Suspend/Resume works with my dual-head setup! The + password prompt appears on the external monitor. If I start the X server + without an external monitor connected to the VGA port, I'm not able to + unlock the screen. I'm not sure whether resuming ever worked without the + external monitor. So the old description below might be obsolete. + + Old description: After the latest security updates (2.6.27-7.14 - + 2.6.27-7.16) resume stopped working on my Samsung R20 notebook. The + notebook suspends fine but when trying to resume the screen just + flickers for a moment and becomes a bit brighter. With Ctrl+Alt+Del I'm + still able to reboot. I also tried downgrading to the 2.6.27-7.14 kernel but resume has stopped working with that kernel too. In the attached kern.log I found fglrx-dumps such as this one: Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713011] [fglrx] ASIC hang happens. Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713023] Pid: 5823, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713047] [f8cb8c2d] KCL_dump_stack+0xd/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713117] [f8ccd49c] firegl_hardwareHangRecovery+0x1c/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713180] [f8d4cceb] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713256] [f8cb7c18] ? KAS_GetTickCounter+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713301] [f8d4cc87] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713375] [f8d51d16] _ZN6AsicR616ASICIdleInternalEN4Asic15idle_WaitMethodE+0x96/0x1f0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713450] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713504] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713570] [f8cb7c38] ? KCL_get_pubdev+0x8/0x10 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713623] [f8ce87cd] ? firegl_trace+0x3d/0x1b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713688] [c014f082] ? update_wall_time+0x442/0x890 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713698] [f8d296b6] ? QSSubmitList+0x56/0x170 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713775] [f8d4b42c] _ZN4Asic7PM4idleENS_15idle_WaitMethodE+0x4c/0x80 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713849] [f8d44565] _ZN15QS_PRIVATE_CORE7PM4idleEN4Asic15idle_WaitMethodE+0x35/0x70 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.713930] [f8d31f11] _ZN10QS_PRIVATE11synchronizeEv+0x31/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714000] [f8d297e7] QSSynchronize+0x17/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714067] [f8d32bd9] _Z14uQSSynchronizej+0x19/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714136] [f8d3ab4b] _Z8uCWDDEQCjjjPvjS_+0x3db/0x1260 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714207] [f8d28cd4] CMMQS_uCWDDEQC+0x34/0x40 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714274] [f8ceb202] firegl_cmmqs_CWDDE_32+0x402/0x4b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714324] [c02548ca] copy_from_user+0x3a/0x130 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714330] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714343] [f8ce998d] firegl_cmmqs_CWDDE32+0x8d/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714409] [c0211bf2] cap_capable+0x12/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714419] [c013a828] capable+0x18/0x40 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714426] [f8ce9900] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714481] [f8cc8577] firegl_ioctl+0x227/0x2b0 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714523] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714543] [c01c64a6] d_materialise_unique+0x156/0x370 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714548] [c037c999] schedule+0x429/0x790 Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714558] [f8cbcafe] ip_firegl_ioctl+0x1e/0x20 [fglrx] Nov 6 13:28:04 thomas-samsungr20 kernel: [ 4199.714598] [c01c64a6]
[Bug 226566] Re: 2.6.24-17 breaks suspend/resume
*** This bug is a duplicate of bug 226279 *** https://bugs.launchpad.net/bugs/226279 ** This bug has been marked a duplicate of bug 226279 Kernel 2.6.24-17 - broken resume from suspend to RAM -- 2.6.24-17 breaks suspend/resume https://bugs.launchpad.net/bugs/226566 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
I can confirm this on my Samsung R20. Resume stopped working after the upgrade to 2.6.24-17. Works fine with 2.6.24-16. -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227838] Re: Failed to intialize HAL error message after gdm login. possibly because of wrong gdm priority in /etc/rc*/
** Attachment added: hal.log http://launchpadlibrarian.net/14342928/hal.log -- Failed to intialize HAL error message after gdm login. possibly because of wrong gdm priority in /etc/rc*/ https://bugs.launchpad.net/bugs/227838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227838] [NEW] Failed to intialize HAL error message after gdm login. possibly because of wrong gdm priority in /etc/rc*/
Public bug reported: Binary package hint: gdm After upgrades from Feisty to Gutsy and from Gutsy to Hardy I get an error message after logging in with gdm (2.20.5-0ubuntu3) saying Failed to initialize HAL but debugging HAL showed that it just comes up fine (see attachment). These are the symlinks to gdm and hal in /etc/rc*: $ ls -l /etc/rc*/*hal /etc/rc1.d/K16hal - ../init.d/hal /etc/rc2.d/S24hal - ../init.d/hal /etc/rc3.d/S24hal - ../init.d/hal /etc/rc4.d/S24hal - ../init.d/hal /etc/rc5.d/S24hal - ../init.d/hal $ ls -l /etc/rc*/*gdm* /etc/rc0.d/K01gdm - ../init.d/gdm /etc/rc1.d/K01gdm - ../init.d/gdm /etc/rc2.d/S13gdm - ../init.d/gdm /etc/rc3.d/S13gdm - ../init.d/gdm /etc/rc4.d/S13gdm - ../init.d/gdm /etc/rc5.d/S13gdm - ../init.d/gdm /etc/rc6.d/K01gdm - ../init.d/gdm HAL is started after gdm and if I login to quickly HAL is not running yet. I was hinted to this by Martin Pitt (who thinks that this an Feisty upgrade issue) in another bug report: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/comments/180 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- Failed to intialize HAL error message after gdm login. possibly because of wrong gdm priority in /etc/rc*/ https://bugs.launchpad.net/bugs/227838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210346] Re: Network Manager does not automatically connect on login
In my case this bug is a consequence of this one: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838 Changing the priority of gdm in /etc/rc*/*gdm from 13 to 30 solved the problem for me. -- Network Manager does not automatically connect on login https://bugs.launchpad.net/bugs/210346 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Thanks! I've changed the level of gdm to 30 and everything's fine now. I've created a new bug report against gdm which can be found at https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I just ran into this problem after updating to hal 0.5.11~rc2-1ubuntu8 (which was supposed to fix this bug for some people if I got the discussion right) on my Samung R20 running Hardy. Neither the subsequent update to 0.5.11~rc2-1ubuntu8.1 nor the downgrade to 0.5.11~rc2-1ubuntu7 did help. After logging in with gdm I get the infamous Failed to initialize HAL message. Wifi isn't working at first but comes up after about 30 seconds. $ ls -l /etc/rc*/*dbus* /etc/rc1.d/K88dbus - ../init.d/dbus /etc/rc2.d/S12dbus - ../init.d/dbus /etc/rc3.d/S12dbus - ../init.d/dbus /etc/rc4.d/S12dbus - ../init.d/dbus /etc/rc5.d/S12dbus - ../init.d/dbus $ ls -l /etc/rc*/*hal /etc/rc1.d/K16hal - ../init.d/hal /etc/rc2.d/S24hal - ../init.d/hal /etc/rc3.d/S24hal - ../init.d/hal /etc/rc4.d/S24hal - ../init.d/hal /etc/rc5.d/S24hal - ../init.d/hal $ ls -l /etc/rc*/*gdm* /etc/rc0.d/K01gdm - ../init.d/gdm /etc/rc1.d/K01gdm - ../init.d/gdm /etc/rc2.d/S13gdm - ../init.d/gdm /etc/rc3.d/S13gdm - ../init.d/gdm /etc/rc4.d/S13gdm - ../init.d/gdm /etc/rc5.d/S13gdm - ../init.d/gdm /etc/rc6.d/K01gdm - ../init.d/gdm ** Attachment added: hal.log http://launchpadlibrarian.net/14260848/hal.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Attachment added: lshal.txt http://launchpadlibrarian.net/14260858/lshal.txt -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Attachment added: kern.log http://launchpadlibrarian.net/14260875/kern.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
changing the priority of hal in rc2.d from 24 to 13 seems to fix the problem for me. by the way, my upgrade history is feisty - gutsy - hardy. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210346] Re: Network Manager does not automatically connect on login
I can confirm this with my Hardy installation on my Samsung R20 laptop (having a Atheros AR242x PCI Express Adapter). -- Network Manager does not automatically connect on login https://bugs.launchpad.net/bugs/210346 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93466] Re: Screensaver does not recognize activity on 2nd screen
I'm experiencing the same problem. IMHO the importance should be raised from low to medium on this bug. For now I've hacked myself an unsatisfying workaround: http://cc.thammerl.interlinked.org/index.php/2008/01/13 /enablingdisabling-gnome-screensaver-with-a-custom-keyboard-shortcut/ ** Attachment added: xorg.conf http://launchpadlibrarian.net/13091484/xorg.conf -- Screensaver does not recognize activity on 2nd screen https://bugs.launchpad.net/bugs/93466 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152772] Re: Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350
*** This bug is a duplicate of bug 182063 *** https://bugs.launchpad.net/bugs/182063 No boot hangs anymore when booting the gutsy kernel with hpet=disable. There haven't been any system freezes either. Thanks for the suggestion, Fil! -- Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350 https://bugs.launchpad.net/bugs/152772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152772] Re: Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350
Using kernel 2.6.22-14 with kernel parameter acpi=off solved the boot issue for me. For wifi support I need to pass noapic as well to the kernel. With this configuration I don't experience any system freezes anymore. -- Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350 https://bugs.launchpad.net/bugs/152772 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152772] Re: Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350
Updated my BIOS to the latest version (14SH). The system still randomly freezes with kernel 2.6.20-16 if multicore processing is enabled. Kernel 2.6.22-14 takes very long to boot (~10 minutes) but wifi is working now due to the latest update of linux-restricted-modules-generic. I haven't experienced a system freeze with 2.6.22-14 yet. Didn't do much testing with this kernel though. -- Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350 https://bugs.launchpad.net/bugs/152772 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152772] Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350
Public bug reported: I've installed Feisty on my Samsung R20 and experienced random system freezes. Sometimes the freeze happens a few minutes after startup and sometimes the system runs for a few hours without any problem until the crash. The system halts and stays completely unresponsive. If sound is active at the time of the freeze the last few milliseconds of the sound are repeated over and over again. I tried to ping the freezed system and i tried to log in via SSH from another machine but got no response. Memtest didn't show any errors and cpu temperature was normal (TZ00: 50° celsius, TZ01: 27° celsius). Nothing suspicious was written to the logfiles in /var/log at the time of the freeze. I upgraded to Gutsy to see if this would solve the issue but the new kernel (2.6.22-14) wouldn't boot so I'm using Gutsy with the Feisty kernel (2.6.20-16). The system still randomly crashed in this environment. Disabling multicore support in my system's BIOS seems to have solved my problem. I even can boot with the new 2.6.22-14-kernel now but I'm still using the 2.6.20-16-kernel because wifi isn't working with the new kernel. My hardware: * Intel Core Duo T2350 @ 1,86 GHz * 1,5 GB memory (in fact 1,2 GB because my graphic card is taking 256MB) * 128 MB ATI Radeon Express X1250 ** Affects: ubuntu Importance: Undecided Status: New -- Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350 https://bugs.launchpad.net/bugs/152772 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
