On saucy, with kernel 3.11.0-2-generic, I sometimes get the same error message when having Radeon DPM enabled (radeon.dpm=1). Unity desktop then freezes and after a few seconds, the screen turns black. However, I can switch to the console and reboot. When leaving DPM disabled (radeon,dpm=0), I don't run into this problem. In any case, my computer always boots fine.
This is some hopefully relevant output that I got by 'grep radeon /var/log/kern.log' (DPM enabled): Aug 15 11:08:04 beifang kernel: [ 4.171526] [drm] radeon kernel modesetting enabled. Aug 15 11:08:04 beifang kernel: [ 4.282475] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 11:08:04 beifang kernel: [ 4.291115] radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) Aug 15 11:08:04 beifang kernel: [ 4.291120] radeon 0000:00:01.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF Aug 15 11:08:04 beifang kernel: [ 4.298334] [drm] radeon: 1024M of VRAM memory ready Aug 15 11:08:04 beifang kernel: [ 4.298336] [drm] radeon: 512M of GTT memory ready. Aug 15 11:08:04 beifang kernel: [ 4.346703] radeon 0000:00:01.0: WB enabled Aug 15 11:08:04 beifang kernel: [ 4.346710] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041ea8fc00 Aug 15 11:08:04 beifang kernel: [ 4.347447] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900125b5a18 Aug 15 11:08:04 beifang kernel: [ 4.347449] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88041ea8fc04 Aug 15 11:08:04 beifang kernel: [ 4.347452] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88041ea8fc08 Aug 15 11:08:04 beifang kernel: [ 4.347454] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041ea8fc0c Aug 15 11:08:04 beifang kernel: [ 4.347456] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88041ea8fc10 Aug 15 11:08:04 beifang kernel: [ 4.348164] radeon 0000:00:01.0: irq 57 for MSI/MSI-X Aug 15 11:08:04 beifang kernel: [ 4.348332] radeon 0000:00:01.0: radeon: using MSI. Aug 15 11:08:04 beifang kernel: [ 4.349755] [drm] radeon: irq initialized. Aug 15 11:08:04 beifang kernel: [ 4.567511] [drm] radeon: power management initialized Aug 15 11:08:05 beifang kernel: [ 4.751046] fbcon: radeondrmfb (fb0) is primary device Aug 15 11:08:05 beifang kernel: [ 4.850214] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device Aug 15 11:08:05 beifang kernel: [ 4.850215] radeon 0000:00:01.0: registered panic notifier Aug 15 11:08:05 beifang kernel: [ 4.851477] [drm] Initialized radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0 Aug 15 11:14:42 beifang kernel: [ 5.519888] [drm] radeon kernel modesetting enabled. Aug 15 11:14:42 beifang kernel: [ 5.519925] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 11:14:42 beifang kernel: [ 5.520701] radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) Aug 15 11:14:42 beifang kernel: [ 5.520704] radeon 0000:00:01.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF Aug 15 11:14:42 beifang kernel: [ 5.521658] [drm] radeon: 1024M of VRAM memory ready Aug 15 11:14:42 beifang kernel: [ 5.521659] [drm] radeon: 512M of GTT memory ready. Aug 15 11:14:42 beifang kernel: [ 5.549871] radeon 0000:00:01.0: WB enabled Aug 15 11:14:42 beifang kernel: [ 5.549876] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8803f8a2ec00 Aug 15 11:14:42 beifang kernel: [ 5.550625] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90012cb5a18 Aug 15 11:14:42 beifang kernel: [ 5.550628] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8803f8a2ec04 Aug 15 11:14:42 beifang kernel: [ 5.550630] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8803f8a2ec08 Aug 15 11:14:42 beifang kernel: [ 5.550633] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8803f8a2ec0c Aug 15 11:14:42 beifang kernel: [ 5.550635] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8803f8a2ec10 Aug 15 11:14:42 beifang kernel: [ 5.550852] radeon 0000:00:01.0: irq 56 for MSI/MSI-X Aug 15 11:14:42 beifang kernel: [ 5.550865] radeon 0000:00:01.0: radeon: using MSI. Aug 15 11:14:42 beifang kernel: [ 5.551522] [drm] radeon: irq initialized. Aug 15 11:14:42 beifang kernel: [ 5.818960] [drm] radeon: dpm initialized Aug 15 11:14:42 beifang kernel: [ 6.037287] fbcon: radeondrmfb (fb0) is primary device Aug 15 11:14:42 beifang kernel: [ 6.105416] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device Aug 15 11:14:42 beifang kernel: [ 6.105417] radeon 0000:00:01.0: registered panic notifier Aug 15 11:14:42 beifang kernel: [ 6.120260] [drm] Initialized radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0 Aug 15 11:47:08 beifang kernel: [ 6.265938] [drm] radeon kernel modesetting enabled. Aug 15 11:47:09 beifang kernel: [ 6.651842] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 11:47:09 beifang kernel: [ 6.653815] radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) Aug 15 11:47:09 beifang kernel: [ 6.653818] radeon 0000:00:01.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF Aug 15 11:47:09 beifang kernel: [ 6.662763] [drm] radeon: 1024M of VRAM memory ready Aug 15 11:47:09 beifang kernel: [ 6.662765] [drm] radeon: 512M of GTT memory ready. Aug 15 11:47:09 beifang kernel: [ 6.788370] radeon 0000:00:01.0: WB enabled Aug 15 11:47:09 beifang kernel: [ 6.788376] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8803f5210c00 Aug 15 11:47:09 beifang kernel: [ 6.789107] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900125b5a18 Aug 15 11:47:09 beifang kernel: [ 6.789110] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8803f5210c04 Aug 15 11:47:09 beifang kernel: [ 6.789112] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8803f5210c08 Aug 15 11:47:09 beifang kernel: [ 6.789115] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8803f5210c0c Aug 15 11:47:09 beifang kernel: [ 6.789117] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8803f5210c10 Aug 15 11:47:09 beifang kernel: [ 6.789148] radeon 0000:00:01.0: irq 57 for MSI/MSI-X Aug 15 11:47:09 beifang kernel: [ 6.789161] radeon 0000:00:01.0: radeon: using MSI. Aug 15 11:47:09 beifang kernel: [ 6.789435] [drm] radeon: irq initialized. Aug 15 11:47:09 beifang kernel: [ 7.067105] [drm] radeon: dpm initialized Aug 15 11:47:09 beifang kernel: [ 7.243644] fbcon: radeondrmfb (fb0) is primary device Aug 15 11:47:09 beifang kernel: [ 7.323668] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device Aug 15 11:47:09 beifang kernel: [ 7.323670] radeon 0000:00:01.0: registered panic notifier Aug 15 11:47:09 beifang kernel: [ 7.323775] [drm] Initialized radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0 Aug 15 12:52:01 beifang kernel: [ 6.277564] [drm] radeon kernel modesetting enabled. Aug 15 12:52:01 beifang kernel: [ 6.308798] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 12:52:01 beifang kernel: [ 6.309547] radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) Aug 15 12:52:01 beifang kernel: [ 6.309550] radeon 0000:00:01.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF Aug 15 12:52:01 beifang kernel: [ 6.313378] [drm] radeon: 1024M of VRAM memory ready Aug 15 12:52:01 beifang kernel: [ 6.313379] [drm] radeon: 512M of GTT memory ready. Aug 15 12:52:01 beifang kernel: [ 6.368038] radeon 0000:00:01.0: WB enabled Aug 15 12:52:01 beifang kernel: [ 6.368045] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8803f5c15c00 Aug 15 12:52:01 beifang kernel: [ 6.368776] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90012cb5a18 Aug 15 12:52:01 beifang kernel: [ 6.368779] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8803f5c15c04 Aug 15 12:52:01 beifang kernel: [ 6.368782] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8803f5c15c08 Aug 15 12:52:01 beifang kernel: [ 6.368784] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8803f5c15c0c Aug 15 12:52:01 beifang kernel: [ 6.368787] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8803f5c15c10 Aug 15 12:52:01 beifang kernel: [ 6.368819] radeon 0000:00:01.0: irq 56 for MSI/MSI-X Aug 15 12:52:01 beifang kernel: [ 6.368832] radeon 0000:00:01.0: radeon: using MSI. Aug 15 12:52:01 beifang kernel: [ 6.369105] [drm] radeon: irq initialized. Aug 15 12:52:02 beifang kernel: [ 6.844325] [drm] radeon: dpm initialized Aug 15 12:52:02 beifang kernel: [ 7.037762] fbcon: radeondrmfb (fb0) is primary device Aug 15 12:52:02 beifang kernel: [ 7.158912] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device Aug 15 12:52:02 beifang kernel: [ 7.158914] radeon 0000:00:01.0: registered panic notifier Aug 15 12:52:02 beifang kernel: [ 7.168045] [drm] Initialized radeon 2.34.0 20080528 for 0000:00:01.0 on minor 0 Aug 15 12:57:06 beifang kernel: [ 311.697896] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec Aug 15 12:57:06 beifang kernel: [ 311.697906] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000004660 last fence id 0x000000000000465f) Aug 15 12:57:06 beifang kernel: [ 312.090125] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090143] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090149] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090154] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090159] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090185] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090193] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090204] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090210] radeon 0000:00:01.0: couldn't schedule ib Aug 15 12:57:06 beifang kernel: [ 312.090215] radeon 0000:00:01.0: couldn't schedule ib [...] goes on like this until I reboot, I guess. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1043541 Title: radeon 0000:00:01.0: couldn't schedule ib Status in “linux” package in Ubuntu: Incomplete Bug description: when attempting to boot up, the computer will randomly fail to boot, and then later will have error messages in kern.log [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! and radeon 0000:00:01.0: couldn't schedule ib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
