linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 3.0.0-rc2 fails to boot on Atom appliance.
@ 2011-06-06 20:09 Ben Greear
  2011-06-06 23:26 ` 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915) Ben Greear
  0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2011-06-06 20:09 UTC (permalink / raw)
  To: Linux Kernel Mailing List

Anyone seen something like this?  For what it's worth, it seems
that -rc1 had the same problem.  I'll start bisecting soon if
the problem isn't already resolved somehow...

OS is 32-bit Fedora 13.

udevd (96): /proc/96/oom_adj is deprecated, please use /proc/96/oom_score_adj instead.
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
dracut:
dracut: udevadm settle - timeout of 30 seconds reached, the event queue contains:
dracut: /sys/devices/pci0000:00/0000:00:02.0 (885)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (965)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (966)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (967)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (968)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (969)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (970)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (971)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (972)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (973)
dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (974)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (975)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (976)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (977)
dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (978)
dracut: Starting plymouth daemon
Gdracut: rd_NO_DM: removing DM RAID activation
dracut: rd_NO_MD: removing MD RAID activation
Gudevd[96]: worker [99] unexpectedly returned with status 0x0100

udevd[96]: worker [99] failed while handling '/devices/pci0000:00/0000:00:02.0'


udevadm settle - timeout of 180 seconds reached, the event queue contains:
   /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (965)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (966)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (967)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (968)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (969)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (970)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (971)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (972)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (973)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (974)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (975)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (976)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (977)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (978)
   /sys/devices/pci0000:00/0000:00:02.0 (1053)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (1054)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (1055)
   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (1056)
   /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (1057)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (1058)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (1059)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (1060)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (1061)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (1062)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (1063)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (1064)
   /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (1065)
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
INFO: task modprobe:263 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
modprobe        D f26ebeec     0   263      1 0x00000000
  f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
  f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
  00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
Call Trace:
  [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
  [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
  [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
  [<c045153c>] ? prepare_to_wait+0x56/0x5c
  [<c067e89b>] wait_for_device_probe+0x5d/0x76
  [<c0451360>] ? wake_up_bit+0x60/0x60
  [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
  [<c040115e>] do_one_initcall+0x76/0x126
  [<f8563000>] ? 0xf8562fff
  [<c046b929>] sys_init_module+0x7c/0x1a8
  [<c0801d98>] sysenter_do_call+0x12/0x38
no locks held by modprobe/263.
SysRq : Show Locks Held

Showing all locks held in the system:
7 locks held by modprobe/100:
  #0:  (&__lockdep_no_validate__){+.+.+.}, at: [<c067e724>] __driver_attach+0x31/0x6b
  #1:  (&__lockdep_no_validate__){+.+.+.}, at: [<c067e730>] __driver_attach+0x3d/0x6b
  #2:  (drm_global_mutex){+.+.+.}, at: [<f810a024>] drm_get_pci_dev+0xad/0x21b [drm]
  #3:  (&(&i->lock)->rlock){-.-...}, at: [<c066a101>] serial8250_interrupt+0x23/0xe9
  #4:  (&port_lock_key){-.-...}, at: [<c0669e59>] serial8250_handle_port+0x15/0x29a
  #5:  (sysrq_key_table_lock){-.....}, at: [<c065a4cc>] __handle_sysrq+0x1d/0x115
  #6:  (tasklist_lock){.+.+..}, at: [<c0461000>] debug_show_all_locks+0x41/0x16b

=============================================

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-06 20:09 3.0.0-rc2 fails to boot on Atom appliance Ben Greear
@ 2011-06-06 23:26 ` Ben Greear
  2011-06-06 23:41   ` Keith Packard
  0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2011-06-06 23:26 UTC (permalink / raw)
  To: Linux Kernel Mailing List, barnes, keithp

On 06/06/2011 01:09 PM, Ben Greear wrote:
> Anyone seen something like this?  For what it's worth, it seems
> that -rc1 had the same problem. I'll start bisecting soon if
> the problem isn't already resolved somehow...

I bisected this problem down to this commit:


[greearb@build-32 linux-2.6]$ git bisect bad
6067aaeadb5b3df26f27ac827256b1ef01e674f5 is the first bad commit
commit 6067aaeadb5b3df26f27ac827256b1ef01e674f5
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Thu Apr 28 15:04:31 2011 -0700

     drm/i915: split clock gating init into per-chipset functions

     This helps contain the mess to init_display() instead.

     Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
     Reviewed-by: Keith Packard <keithp@keithp.com>
     Signed-off-by: Keith Packard <keithp@keithp.com>

:040000 040000 9f53568fc450a9a53b1fe749142dd9c8f2707881 a3c2031ba7d5ea9c4190279315c436131b6cf922 M	drivers


Full dmesg from a working boot (2.6.38.7) is here:

http://www.candelatech.com/~greearb/misc/fw7535-dmesg.txt

I'm happy to test patches...

Thanks,
Ben


>
> OS is 32-bit Fedora 13.
>
> udevd (96): /proc/96/oom_adj is deprecated, please use
> /proc/96/oom_score_adj instead.
> [drm] Initialized drm 1.1.0 20060810
> i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [drm] Driver supports precise vblank timestamp query.
> vgaarb: device changed decodes:
> PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
> dracut:
> dracut: udevadm settle - timeout of 30 seconds reached, the event queue
> contains:
> dracut: /sys/devices/pci0000:00/0000:00:02.0 (885)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (965)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (966)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (967)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (968)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (969)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (970)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (971)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (972)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (973)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (974)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (975)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (976)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (977)
> dracut: /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (978)
> dracut: Starting plymouth daemon
> Gdracut: rd_NO_DM: removing DM RAID activation
> dracut: rd_NO_MD: removing MD RAID activation
> Gudevd[96]: worker [99] unexpectedly returned with status 0x0100
>
> udevd[96]: worker [99] failed while handling
> '/devices/pci0000:00/0000:00:02.0'
>
>
> udevadm settle - timeout of 180 seconds reached, the event queue contains:
> /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (965)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (966)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (967)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (968)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (969)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (970)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (971)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (972)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (973)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (974)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (975)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (976)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (977)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (978)
> /sys/devices/pci0000:00/0000:00:02.0 (1053)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0 (1054)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (1055)
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (1056)
> /sys/devices/pci0000:00/0000:00:02.0/drm/controlD64 (1057)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-0 (1058)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-1 (1059)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-2 (1060)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-3 (1061)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-4 (1062)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-5 (1063)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-6 (1064)
> /sys/devices/pci0000:00/0000:00:02.0/i2c-7 (1065)
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> INFO: task modprobe:263 blocked for more than 180 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> modprobe D f26ebeec 0 263 1 0x00000000
> f26ebf58 00000046 00000006 f26ebeec c0b1fc00 f261d280 c0b1fc00 c0b1fc00
> f261d4fc c0b1fc00 7bff03b0 00000032 00000000 00000032 f261d280 00000000
> 00000007 f261d280 c07fc13c 00000002 f26ebf28 c04619c3 c0a6bb34 00000246
> Call Trace:
> [<c07fc13c>] ? _raw_spin_unlock_irqrestore+0x41/0x4d
> [<c04619c3>] ? trace_hardirqs_on_caller+0x10e/0x12f
> [<c04619ef>] ? trace_hardirqs_on+0xb/0xd
> [<c045153c>] ? prepare_to_wait+0x56/0x5c
> [<c067e89b>] wait_for_device_probe+0x5d/0x76
> [<c0451360>] ? wake_up_bit+0x60/0x60
> [<f8563008>] wait_scan_init+0x8/0x11 [scsi_wait_scan]
> [<c040115e>] do_one_initcall+0x76/0x126
> [<f8563000>] ? 0xf8562fff
> [<c046b929>] sys_init_module+0x7c/0x1a8
> [<c0801d98>] sysenter_do_call+0x12/0x38
> no locks held by modprobe/263.
> SysRq : Show Locks Held
>
> Showing all locks held in the system:
> 7 locks held by modprobe/100:
> #0: (&__lockdep_no_validate__){+.+.+.}, at: [<c067e724>]
> __driver_attach+0x31/0x6b
> #1: (&__lockdep_no_validate__){+.+.+.}, at: [<c067e730>]
> __driver_attach+0x3d/0x6b
> #2: (drm_global_mutex){+.+.+.}, at: [<f810a024>]
> drm_get_pci_dev+0xad/0x21b [drm]
> #3: (&(&i->lock)->rlock){-.-...}, at: [<c066a101>]
> serial8250_interrupt+0x23/0xe9
> #4: (&port_lock_key){-.-...}, at: [<c0669e59>]
> serial8250_handle_port+0x15/0x29a
> #5: (sysrq_key_table_lock){-.....}, at: [<c065a4cc>]
> __handle_sysrq+0x1d/0x115
> #6: (tasklist_lock){.+.+..}, at: [<c0461000>]
> debug_show_all_locks+0x41/0x16b
>
> =============================================
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-06 23:26 ` 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915) Ben Greear
@ 2011-06-06 23:41   ` Keith Packard
  2011-06-06 23:59     ` Ben Greear
  0 siblings, 1 reply; 7+ messages in thread
From: Keith Packard @ 2011-06-06 23:41 UTC (permalink / raw)
  To: Ben Greear, Linux Kernel Mailing List, barnes

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On Mon, 06 Jun 2011 16:26:25 -0700, Ben Greear <greearb@candelatech.com> wrote:
> On 06/06/2011 01:09 PM, Ben Greear wrote:
> > Anyone seen something like this?  For what it's worth, it seems
> > that -rc1 had the same problem. I'll start bisecting soon if
> > the problem isn't already resolved somehow...
> 
> I bisected this problem down to this commit:

This should be fixed by this patch:

-------------------- drivers/gpu/drm/i915/intel_display.c ---------------------
index f553ddf..bb1b59b 100644
@@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
 			dev_priv->display.update_wm = NULL;
 		} else
 			dev_priv->display.update_wm = pineview_update_wm;
+		dev_priv->display.init_clock_gating = gen3_init_clock_gating;
 	} else if (IS_G4X(dev)) {
 		dev_priv->display.update_wm = g4x_update_wm;
 		dev_priv->display.init_clock_gating = g4x_init_clock_gating;

This hasn't been merged yet, but should be soon.

-- 
keith.packard@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-06 23:41   ` Keith Packard
@ 2011-06-06 23:59     ` Ben Greear
  2011-06-07  0:24       ` Jesse Barnes
  0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2011-06-06 23:59 UTC (permalink / raw)
  To: Keith Packard; +Cc: Linux Kernel Mailing List, jbarnes

On 06/06/2011 04:41 PM, Keith Packard wrote:
> On Mon, 06 Jun 2011 16:26:25 -0700, Ben Greear<greearb@candelatech.com>  wrote:
>> On 06/06/2011 01:09 PM, Ben Greear wrote:
>>> Anyone seen something like this?  For what it's worth, it seems
>>> that -rc1 had the same problem. I'll start bisecting soon if
>>> the problem isn't already resolved somehow...
>>
>> I bisected this problem down to this commit:
>
> This should be fixed by this patch:
>
> -------------------- drivers/gpu/drm/i915/intel_display.c ---------------------
> index f553ddf..bb1b59b 100644
> @@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
>   			dev_priv->display.update_wm = NULL;
>   		} else
>   			dev_priv->display.update_wm = pineview_update_wm;
> +		dev_priv->display.init_clock_gating = gen3_init_clock_gating;
>   	} else if (IS_G4X(dev)) {
>   		dev_priv->display.update_wm = g4x_update_wm;
>   		dev_priv->display.init_clock_gating = g4x_init_clock_gating;
>
> This hasn't been merged yet, but should be soon.

I tried adding that, but the problem stays the same.

Any other patches I should try?

Thanks,
Ben

>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-06 23:59     ` Ben Greear
@ 2011-06-07  0:24       ` Jesse Barnes
  2011-06-07  4:00         ` Ben Greear
  0 siblings, 1 reply; 7+ messages in thread
From: Jesse Barnes @ 2011-06-07  0:24 UTC (permalink / raw)
  To: Ben Greear; +Cc: Keith Packard, Linux Kernel Mailing List

On Mon, 06 Jun 2011 16:59:02 -0700
Ben Greear <greearb@candelatech.com> wrote:

> On 06/06/2011 04:41 PM, Keith Packard wrote:
> > On Mon, 06 Jun 2011 16:26:25 -0700, Ben Greear<greearb@candelatech.com>  wrote:
> >> On 06/06/2011 01:09 PM, Ben Greear wrote:
> >>> Anyone seen something like this?  For what it's worth, it seems
> >>> that -rc1 had the same problem. I'll start bisecting soon if
> >>> the problem isn't already resolved somehow...
> >>
> >> I bisected this problem down to this commit:
> >
> > This should be fixed by this patch:
> >
> > -------------------- drivers/gpu/drm/i915/intel_display.c ---------------------
> > index f553ddf..bb1b59b 100644
> > @@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
> >   			dev_priv->display.update_wm = NULL;
> >   		} else
> >   			dev_priv->display.update_wm = pineview_update_wm;
> > +		dev_priv->display.init_clock_gating = gen3_init_clock_gating;
> >   	} else if (IS_G4X(dev)) {
> >   		dev_priv->display.update_wm = g4x_update_wm;
> >   		dev_priv->display.init_clock_gating = g4x_init_clock_gating;
> >
> > This hasn't been merged yet, but should be soon.
> 
> I tried adding that, but the problem stays the same.
> 
> Any other patches I should try?

Are you sure you booted the right kernel and that it built & installed
correctly?

You could add an:
  if (dev_priv->display.init_clock_gating)
above the call to display.init_clock_gating in intel_init_clock_gating
to be sure it's the same problem...

-- 
Jesse Barnes, Intel Open Source Technology Center

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-07  0:24       ` Jesse Barnes
@ 2011-06-07  4:00         ` Ben Greear
  2011-06-07 17:09           ` Ben Greear
  0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2011-06-07  4:00 UTC (permalink / raw)
  To: Jesse Barnes; +Cc: Keith Packard, Linux Kernel Mailing List

On 06/06/2011 05:24 PM, Jesse Barnes wrote:
> On Mon, 06 Jun 2011 16:59:02 -0700
> Ben Greear<greearb@candelatech.com>  wrote:
>
>> On 06/06/2011 04:41 PM, Keith Packard wrote:
>>> On Mon, 06 Jun 2011 16:26:25 -0700, Ben Greear<greearb@candelatech.com>   wrote:
>>>> On 06/06/2011 01:09 PM, Ben Greear wrote:
>>>>> Anyone seen something like this?  For what it's worth, it seems
>>>>> that -rc1 had the same problem. I'll start bisecting soon if
>>>>> the problem isn't already resolved somehow...
>>>>
>>>> I bisected this problem down to this commit:
>>>
>>> This should be fixed by this patch:
>>>
>>> -------------------- drivers/gpu/drm/i915/intel_display.c ---------------------
>>> index f553ddf..bb1b59b 100644
>>> @@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
>>>    			dev_priv->display.update_wm = NULL;
>>>    		} else
>>>    			dev_priv->display.update_wm = pineview_update_wm;
>>> +		dev_priv->display.init_clock_gating = gen3_init_clock_gating;
>>>    	} else if (IS_G4X(dev)) {
>>>    		dev_priv->display.update_wm = g4x_update_wm;
>>>    		dev_priv->display.init_clock_gating = g4x_init_clock_gating;
>>>
>>> This hasn't been merged yet, but should be soon.
>>
>> I tried adding that, but the problem stays the same.
>>
>> Any other patches I should try?
>
> Are you sure you booted the right kernel and that it built&  installed
> correctly?

I double checked, but I tried to cheat a bit and just applied that patch on
top of -rc2 instead of on top of the patch that breaks things according to
bisect.  Maybe there is more than one problem.  I'll try tweaking that single
patch tomorrow.

And, I built and booted twice to make sure I didn't screw up..but it had been
a long day of bisecting, so maybe I still messed up some how.

>
> You could add an:
>    if (dev_priv->display.init_clock_gating)
> above the call to display.init_clock_gating in intel_init_clock_gating
> to be sure it's the same problem...

Ok, can try that too.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
  2011-06-07  4:00         ` Ben Greear
@ 2011-06-07 17:09           ` Ben Greear
  0 siblings, 0 replies; 7+ messages in thread
From: Ben Greear @ 2011-06-07 17:09 UTC (permalink / raw)
  To: Jesse Barnes; +Cc: Keith Packard, Linux Kernel Mailing List

On 06/06/2011 09:00 PM, Ben Greear wrote:
> On 06/06/2011 05:24 PM, Jesse Barnes wrote:
>> On Mon, 06 Jun 2011 16:59:02 -0700
>> Ben Greear<greearb@candelatech.com> wrote:
>>
>>> On 06/06/2011 04:41 PM, Keith Packard wrote:
>>>> On Mon, 06 Jun 2011 16:26:25 -0700, Ben
>>>> Greear<greearb@candelatech.com> wrote:
>>>>> On 06/06/2011 01:09 PM, Ben Greear wrote:
>>>>>> Anyone seen something like this? For what it's worth, it seems
>>>>>> that -rc1 had the same problem. I'll start bisecting soon if
>>>>>> the problem isn't already resolved somehow...
>>>>>
>>>>> I bisected this problem down to this commit:
>>>>
>>>> This should be fixed by this patch:
>>>>
>>>> -------------------- drivers/gpu/drm/i915/intel_display.c
>>>> ---------------------
>>>> index f553ddf..bb1b59b 100644
>>>> @@ -7675,6 +7675,7 @@ static void intel_init_display(struct
>>>> drm_device *dev)
>>>> dev_priv->display.update_wm = NULL;
>>>> } else
>>>> dev_priv->display.update_wm = pineview_update_wm;
>>>> + dev_priv->display.init_clock_gating = gen3_init_clock_gating;
>>>> } else if (IS_G4X(dev)) {
>>>> dev_priv->display.update_wm = g4x_update_wm;
>>>> dev_priv->display.init_clock_gating = g4x_init_clock_gating;
>>>>
>>>> This hasn't been merged yet, but should be soon.
>>>
>>> I tried adding that, but the problem stays the same.
>>>
>>> Any other patches I should try?
>>
>> Are you sure you booted the right kernel and that it built& installed
>> correctly?
>
> I double checked, but I tried to cheat a bit and just applied that patch on
> top of -rc2 instead of on top of the patch that breaks things according to
> bisect. Maybe there is more than one problem. I'll try tweaking that single
> patch tomorrow.
>
> And, I built and booted twice to make sure I didn't screw up..but it had
> been
> a long day of bisecting, so maybe I still messed up some how.

Ok, building with just your fixup patch on top of the busted patch
does let it boot.

There must be some other failure that is causing -rc2 to fail.

Think I'll wait for -rc3...

Thanks,
Ben


>
>>
>> You could add an:
>> if (dev_priv->display.init_clock_gating)
>> above the call to display.init_clock_gating in intel_init_clock_gating
>> to be sure it's the same problem...
>
> Ok, can try that too.
>
> Thanks,
> Ben
>
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2011-06-07 17:09 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-06 20:09 3.0.0-rc2 fails to boot on Atom appliance Ben Greear
2011-06-06 23:26 ` 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915) Ben Greear
2011-06-06 23:41   ` Keith Packard
2011-06-06 23:59     ` Ben Greear
2011-06-07  0:24       ` Jesse Barnes
2011-06-07  4:00         ` Ben Greear
2011-06-07 17:09           ` Ben Greear

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).