[Bug 27796] New: atombios stuck in loop

All of lore.kernel.org
 help / color / mirror / Atom feed

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27796] New: atombios stuck in loop
Date: Thu, 22 Apr 2010 10:26:26 -0700 (PDT)	[thread overview]
Message-ID: <bug-27796-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=27796

           Summary: atombios stuck in loop
           Product: DRI
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pjsanon@hotmail.com


Created an attachment (id=35239)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=35239)
bios

I am having problems with lock up in X i loose all input devices
Switching back from the console, i see the following on the screen

atombios stuck in loop



I am using fedora and the version of Xorg is 1.8.0-7.

LSPCI
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility
X1600] (prog-if 00 [VGA controller])
    Subsystem: Apple Computer Inc. MacBook Pro
    Flags: bus master, fast devsel, latency 0, IRQ 28
    Memory at c0000000 (32-bit, prefetchable) [size=256M]
    I/O ports at 3000 [size=256]
    Memory at d8300000 (32-bit, non-prefetchable) [size=64K]
    Expansion ROM at d8320000 [disabled] [size=128K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Kernel driver in use: radeon
    Kernel modules: radeon

EXTRACT FROM /var/log/messages

Apr 22 10:59:51 localhost kernel: INFO: task Xorg:1792 blocked for more than
120 seconds.
Apr 22 10:59:51 localhost kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 22 10:59:51 localhost kernel: Xorg          D 0000000000000000  3856  1792 
 1789 0x00400088
Apr 22 10:59:51 localhost kernel: ffff8800b06cdbc8 0000000000000046
ffff8800b06cdb90 ffff8800b06cdb8c
Apr 22 10:59:51 localhost kernel: ffff8800b06cdb38 0000000000000000
0000000000001402 ffff8800b06cdfd8
Apr 22 10:59:51 localhost kernel: ffff8800b06cdfd8 000000000000fb80
00000000001d5e80 ffff8800b072a888
Apr 22 10:59:51 localhost kernel: Call Trace:
Apr 22 10:59:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 10:59:51 localhost kernel: [<ffffffff81477870>]
__mutex_lock_common+0x24e/0x392
Apr 22 10:59:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 10:59:51 localhost kernel: [<ffffffff8107baca>] ?
lock_release_holdtime+0x34/0xe3
Apr 22 10:59:51 localhost kernel: [<ffffffff81477a78>]
mutex_lock_nested+0x3e/0x43
Apr 22 10:59:51 localhost kernel: [<ffffffffa00a60ba>]
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 10:59:51 localhost kernel: [<ffffffff810f1d8c>] ? might_fault+0x5c/0xac
Apr 22 10:59:51 localhost kernel: [<ffffffff81479540>] ? _lock_kernel+0x7d/0x95
Apr 22 10:59:51 localhost kernel: [<ffffffffa0019418>] drm_ioctl+0x28f/0x373
[drm]
Apr 22 10:59:51 localhost kernel: [<ffffffffa00a6083>] ?
radeon_cs_ioctl+0x0/0x1a1 [radeon]
Apr 22 10:59:51 localhost kernel: [<ffffffff810710fd>] ?
sched_clock_local+0x1c/0x82
Apr 22 10:59:51 localhost kernel: [<ffffffff81054941>] ?
do_setitimer+0x1b1/0x1e2
Apr 22 10:59:51 localhost kernel: [<ffffffff81071226>] ?
sched_clock_cpu+0xc3/0xce
Apr 22 10:59:51 localhost kernel: [<ffffffff8107ba94>] ?
trace_hardirqs_off+0xd/0xf
Apr 22 10:59:51 localhost kernel: [<ffffffff8112c054>] vfs_ioctl+0x32/0xa6
Apr 22 10:59:51 localhost kernel: [<ffffffff8112c5d4>] do_vfs_ioctl+0x490/0x4d6
Apr 22 10:59:51 localhost kernel: [<ffffffff8112c670>] sys_ioctl+0x56/0x79
Apr 22 10:59:51 localhost kernel: [<ffffffff81009c72>]
system_call_fastpath+0x16/0x1b
Apr 22 10:59:51 localhost kernel: 1 lock held by Xorg/1792:
Apr 22 10:59:51 localhost kernel: #0:  (&rdev->cs_mutex){+.+.+.}, at:
[<ffffffffa00a60ba>] radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:01:51 localhost kernel: INFO: task Xorg:1792 blocked for more than
120 seconds.
Apr 22 11:01:51 localhost kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 22 11:01:51 localhost kernel: Xorg          D 0000000000000000  3856  1792 
 1789 0x00400088
Apr 22 11:01:51 localhost kernel: ffff8800b06cdbc8 0000000000000046
ffff8800b06cdb90 ffff8800b06cdb8c
Apr 22 11:01:51 localhost kernel: ffff8800b06cdb38 0000000000000000
0000000000001402 ffff8800b06cdfd8
Apr 22 11:01:51 localhost kernel: ffff8800b06cdfd8 000000000000fb80
00000000001d5e80 ffff8800b072a888
Apr 22 11:01:51 localhost kernel: Call Trace:
Apr 22 11:01:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:01:51 localhost kernel: [<ffffffff81477870>]
__mutex_lock_common+0x24e/0x392
Apr 22 11:01:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:01:51 localhost kernel: [<ffffffff8107baca>] ?
lock_release_holdtime+0x34/0xe3
Apr 22 11:01:51 localhost kernel: [<ffffffff81477a78>]
mutex_lock_nested+0x3e/0x43
Apr 22 11:01:51 localhost kernel: [<ffffffffa00a60ba>]
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:01:51 localhost kernel: [<ffffffff810f1d8c>] ? might_fault+0x5c/0xac
Apr 22 11:01:51 localhost kernel: [<ffffffff81479540>] ? _lock_kernel+0x7d/0x95
Apr 22 11:01:51 localhost kernel: [<ffffffffa0019418>] drm_ioctl+0x28f/0x373
[drm]
Apr 22 11:01:51 localhost kernel: [<ffffffffa00a6083>] ?
radeon_cs_ioctl+0x0/0x1a1 [radeon]
Apr 22 11:01:51 localhost kernel: [<ffffffff810710fd>] ?
sched_clock_local+0x1c/0x82
Apr 22 11:01:51 localhost kernel: [<ffffffff81054941>] ?
do_setitimer+0x1b1/0x1e2
Apr 22 11:01:51 localhost kernel: [<ffffffff81071226>] ?
sched_clock_cpu+0xc3/0xce
Apr 22 11:01:51 localhost kernel: [<ffffffff8107ba94>] ?
trace_hardirqs_off+0xd/0xf
Apr 22 11:01:51 localhost kernel: [<ffffffff8112c054>] vfs_ioctl+0x32/0xa6
Apr 22 11:01:51 localhost kernel: [<ffffffff8112c5d4>] do_vfs_ioctl+0x490/0x4d6
Apr 22 11:01:51 localhost kernel: [<ffffffff8112c670>] sys_ioctl+0x56/0x79
Apr 22 11:01:51 localhost kernel: [<ffffffff81009c72>]
system_call_fastpath+0x16/0x1b
Apr 22 11:01:51 localhost kernel: 1 lock held by Xorg/1792:
Apr 22 11:01:51 localhost kernel: #0:  (&rdev->cs_mutex){+.+.+.}, at:
[<ffffffffa00a60ba>] radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:03:51 localhost kernel: INFO: task Xorg:1792 blocked for more than
120 seconds.
Apr 22 11:03:51 localhost kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 22 11:03:51 localhost kernel: Xorg          D 0000000000000000  3856  1792 
 1789 0x00400088
Apr 22 11:03:51 localhost kernel: ffff8800b06cdbc8 0000000000000046
ffff8800b06cdb90 ffff8800b06cdb8c
Apr 22 11:03:51 localhost kernel: ffff8800b06cdb38 0000000000000000
0000000000001402 ffff8800b06cdfd8
Apr 22 11:03:51 localhost kernel: ffff8800b06cdfd8 000000000000fb80
00000000001d5e80 ffff8800b072a888
Apr 22 11:03:51 localhost kernel: Call Trace:
Apr 22 11:03:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:03:51 localhost kernel: [<ffffffff81477870>]
__mutex_lock_common+0x24e/0x392
Apr 22 11:03:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:03:51 localhost kernel: [<ffffffff8107baca>] ?
lock_release_holdtime+0x34/0xe3
Apr 22 11:03:51 localhost kernel: [<ffffffff81477a78>]
mutex_lock_nested+0x3e/0x43
Apr 22 11:03:51 localhost kernel: [<ffffffffa00a60ba>]
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:03:51 localhost kernel: [<ffffffff810f1d8c>] ? might_fault+0x5c/0xac
Apr 22 11:03:51 localhost kernel: [<ffffffff81479540>] ? _lock_kernel+0x7d/0x95
Apr 22 11:03:51 localhost kernel: [<ffffffffa0019418>] drm_ioctl+0x28f/0x373
[drm]
Apr 22 11:03:51 localhost kernel: [<ffffffffa00a6083>] ?
radeon_cs_ioctl+0x0/0x1a1 [radeon]
Apr 22 11:03:51 localhost kernel: [<ffffffff810710fd>] ?
sched_clock_local+0x1c/0x82
Apr 22 11:03:51 localhost kernel: [<ffffffff81054941>] ?
do_setitimer+0x1b1/0x1e2
Apr 22 11:03:51 localhost kernel: [<ffffffff81071226>] ?
sched_clock_cpu+0xc3/0xce
Apr 22 11:03:51 localhost kernel: [<ffffffff8107ba94>] ?
trace_hardirqs_off+0xd/0xf
Apr 22 11:03:51 localhost kernel: [<ffffffff8112c054>] vfs_ioctl+0x32/0xa6
Apr 22 11:03:51 localhost kernel: [<ffffffff8112c5d4>] do_vfs_ioctl+0x490/0x4d6
Apr 22 11:03:51 localhost kernel: [<ffffffff8112c670>] sys_ioctl+0x56/0x79
Apr 22 11:03:51 localhost kernel: [<ffffffff81009c72>]
system_call_fastpath+0x16/0x1b
Apr 22 11:03:51 localhost kernel: 1 lock held by Xorg/1792:
Apr 22 11:03:51 localhost kernel: #0:  (&rdev->cs_mutex){+.+.+.}, at:
[<ffffffffa00a60ba>] radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:05:51 localhost kernel: INFO: task Xorg:1792 blocked for more than
120 seconds.
Apr 22 11:05:51 localhost kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 22 11:05:51 localhost kernel: Xorg          D 0000000000000000  3856  1792 
 1789 0x00400088
Apr 22 11:05:51 localhost kernel: ffff8800b06cdbc8 0000000000000046
ffff8800b06cdb90 ffff8800b06cdb8c
Apr 22 11:05:51 localhost kernel: ffff8800b06cdb38 0000000000000000
0000000000001402 ffff8800b06cdfd8
Apr 22 11:05:51 localhost kernel: ffff8800b06cdfd8 000000000000fb80
00000000001d5e80 ffff8800b072a888
Apr 22 11:05:51 localhost kernel: Call Trace:
Apr 22 11:05:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:05:51 localhost kernel: [<ffffffff81477870>]
__mutex_lock_common+0x24e/0x392
Apr 22 11:05:51 localhost kernel: [<ffffffffa00a60ba>] ?
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:05:51 localhost kernel: [<ffffffff8107baca>] ?
lock_release_holdtime+0x34/0xe3
Apr 22 11:05:51 localhost kernel: [<ffffffff81477a78>]
mutex_lock_nested+0x3e/0x43
Apr 22 11:05:51 localhost kernel: [<ffffffffa00a60ba>]
radeon_cs_ioctl+0x37/0x1a1 [radeon]
Apr 22 11:05:51 localhost kernel: [<ffffffff810f1d8c>] ? might_fault+0x5c/0xac
Apr 22 11:05:51 localhost kernel: [<ffffffff81479540>] ? _lock_kernel+0x7d/0x95
Apr 22 11:05:51 localhost kernel: [<ffffffffa0019418>] drm_ioctl+0x28f/0x373
[drm]
Apr 22 11:05:51 localhost kernel: [<ffffffffa00a6083>] ?
radeon_cs_ioctl+0x0/0x1a1 [radeon]
Apr 22 11:05:51 localhost kernel: [<ffffffff810710fd>] ?
sched_clock_local+0x1c/0x82
Apr 22 11:05:51 localhost kernel: [<ffffffff81054941>] ?
do_setitimer+0x1b1/0x1e2
Apr 22 11:05:51 localhost kernel: [<ffffffff81071226>] ?
sched_clock_cpu+0xc3/0xce
Apr 22 11:05:51 localhost kernel: [<ffffffff8107ba94>] ?
trace_hardirqs_off+0xd/0xf
Apr 22 11:05:51 localhost kernel: [<ffffffff8112c054>] vfs_ioctl+0x32/0xa6
Apr 22 11:05:51 localhost kernel: [<ffffffff8112c5d4>] do_vfs_ioctl+0x490/0x4d6
Apr 22 11:05:51 localhost kernel: [<ffffffff8112c670>] sys_ioctl+0x56/0x79
Apr 22 11:05:51 localhost kernel: [<ffffffff81009c72>]
system_call_fastpath+0x16/0x1b
Apr 22 11:05:51 localhost kernel: 1 lock held by Xorg/1792:
Apr 22 11:05:51 localhost kernel: #0:  (&rdev->cs_mutex){+.+.+.}, at:
[<ffffffffa00a60ba>] radeon_cs_ioctl+0x37/0x1a1 [radeon]

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

next             reply	other threads:[~2010-04-22 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:26 bugzilla-daemon [this message]
2010-06-30 18:53 ` [Bug 27796] atombios stuck in loop bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27796-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.