Error* Failed To Schedule Ib
Status Importance Assigned to Milestone xserver-xorg-video-ati (Ubuntu) Edit Invalid Low Unassigned Edit You need to log in to change this bug's status. Affecting: xserver-xorg-video-ati (Ubuntu) Filed here by: Jan-Helge When: 2010-05-27 Completed: 2014-01-08 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Low Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: xorg When the screen freezes the following keeps rolling over the virtual consoles (ctrl+alt+1...): kern.log:May 25 13:55:37 planke kernel: [22455.853805] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:37 planke kernel: [22455.854508] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). kern.log:May 25 13:55:37 planke kernel: [22455.854625] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:37 planke kernel: [22455.855120] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). kern.log:May 25 13:55:37 planke kernel: [22455.855282] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:37 planke kernel: [22456.163579] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). kern.log:May 25 13:55:37 planke kernel: [22456.163700] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:38 planke kernel: [22456.468419] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). kern.log:May 25 13:55:38 planke kernel: [22456.468578] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:38 planke kernel: [22456.473296] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4). kern.log:May 25 13:55:38 planke kernel: [22456.473423] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:38 planke kernel: [22456.474532] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(5). kern.log:May 25 13:55:38 planke kernel: [22456.474647] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:38 planke kernel: [22456.475023] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6). kern.log:May 25 13:55:38 planke kernel: [22456.475135] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! kern.log:May 25 13:55:38 planke kernel: [22456.47
Login: [x] First Last Prev Next This bug is not in your last search results. Bug47481 - Random blank screen: radeon_cs_ib_chunk Failed to schedule IB on AMD PALM Summary: Random blank screen: radeon_cs_ib_chunk Failed to schedule IB on AMD PALM Status: RESOLVED CODE_FIX Product: Drivers Classification: Unclassified Component: Video(DRI - non Intel) Hardware: All Linux Importance: P1 normal Assigned To: drivers_video-dri URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2012-09-13 17:15 UTC by Anisse Astier Modified: 2012-12-18 22:23 UTC (History) CC List: 3 users (show) alexdeucher andros sami.nieminen See Also: Kernel Version: 3.5.3, 3.6.0-rc5 Tree: Mainline Regression: Yes Attachments Dmesg of the problem (54.79 https://bugs.launchpad.net/bugs/586243 KB, text/plain) 2012-09-13 17:15 UTC, Anisse Astier Details View All Add an attachment (proposed patch, testcase, etc.) Description Anisse Astier 2012-09-13 17:15:27 UTC Created attachment 80131 [details] Dmesg of the problem Hi, Randomly I might get a bug on an AMD E1-1200 : screen won't turn on and when X is supposed to start I get a lot of these: [ 307.718332] radeon 0000:00:01.0: couldn't schedule ib [ 307.718348] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! https://bugzilla.kernel.org/show_bug.cgi?id=47481 [ 307.719063] radeon 0000:00:01.0: couldn't schedule ib [ 307.719075] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 307.734461] radeon 0000:00:01.0: couldn't schedule ib [ 307.734476] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 307.735489] radeon 0000:00:01.0: couldn't schedule ib [ 307.735502] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! They stop once X is stopped. Full dmesg in attachment. Extract of my xorg.conf: Section "Device" Identifier "Card0 Driver "radeon" Option "DRI" EndSection Comment 1 Anisse Astier 2012-09-13 17:18:45 UTC Correction: screen is blank, but backlight is on. Comment 2 Alex Deucher 2012-09-13 17:19:43 UTC Is this a regression? If so what components did you change (kernel, mesa 3D driver, radeon xorg driver, etc.). Comment 3 Anisse Astier 2012-09-13 17:27:23 UTC I'm not sure. Since it's random I need to do a lot of tests to reproduce it. I'll try to test with 3.2. Sometimes, screen might turn on, but I get vertical black and white stripes. (I have a photo if you need one). My current stack is: - kernel 3.5.3, but it also crashes/bugs with kernel 3.6.0-rc5 - mesa 8.0.4 - DDX 6.14.4 - xserver 1.7.7 Not sure it's relevant since the problem starts before X when modesetting should kick in (screen is blank). Comment 4 Anisse Astier 2012-09-14 10:16:22 UTC I think it is indeed a regression. After many power cycles, I wasn't abl
[x] | Forgot Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First https://bugzilla.redhat.com/show_bug.cgi?id=855275 Last Prev Next This bug is not in your last https://overbenny.wordpress.com/2011/01/26/symptoms-of-a-dying-graphic-card/ search results. Bug855275 - Kernel Error during Bootup: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Summary: Kernel Error during Bootup: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedu... Status: CLOSED CURRENTRELEASE Aliases: None Product: Fedora Classification: Fedora Component: xorg-x11-drv-ati (Show other bugs) Sub Component: --- Version: error* failed 17 Hardware: Unspecified Unspecified Priority unspecified Severity unspecified TargetMilestone: --- TargetRelease: --- Assigned To: X/OpenGL Maintenance List QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2012-09-07 03:42 EDT by Ali Akcaagac Modified: 2013-01-12 05:25 EST (History) CC List: 10 users (show) error* failed to dennyvatwork gansalmon itamar jonathan kernel-maint madhu.chinakonda matthew.slingsby nexfwall oliver.henshaw xgl-maint See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2012-12-06 02:04:23 EST Type: Bug Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) messages.txt from /var/log (108.93 KB, text/plain) 2012-09-07 03:42 EDT, Ali Akcaagac no flags Details Greetings from kernel-3.6.5-1.fc17.i686 (761.68 KB, image/jpeg) 2012-11-02 08:02 EDT, Ali Akcaagac no flags Details Archive with *Screenshots* (3.74 MB, application/x-gzip) 2012-11-02 14:27 EDT, Egor Zaharov no flags Details Full of oops'es (19.44 KB, application/x-bzip) 2012-11-03 09:23 EDT, Ali Akcaagac no flags Details Logs from failed 3.6.10 session (32.24 KB, application/x-gzip) 2012-12-31 15:45 EST, Matt Slingsby no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Ali Akcaagac 2012-09-07 03:42:30 EDT Created attachment 610646 [details] messages.txt from /var/log I
monitor. Moving the window containing the wrong-colors pixels corrected them. The wrong-colored pixels reappear from time to time in increased quantity. Then a second symptom appeared: The screen went black and came back one second later. This was triggered by moving a window and scrolling. I wasn't sure what the reason was. Either it was a bug somewhere in the X stack or some hardware was dying. dmesg showed multiple problems with the radeon driver: [283808.667454] radeon 0000:01:00.0: ffff88021f815c00 unpin not necessary [283808.667820] radeon 0000:01:00.0: GPU softreset [283808.667823] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xE57024A4 [283808.667825] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00330302 [283808.667826] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 [283808.667832] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE [283808.682844] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 [283808.698840] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0x00003028 [283808.698843] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000002 [283808.698845] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 [283808.699845] radeon 0000:01:00.0: GPU reset succeed [283808.717570] [drm] Clocks initialized ! [283808.765829] [drm] ring test succeeded in 0 usecs [283808.765838] [drm] ib test succeeded in 1 usecs [283808.765840] [drm] Enabling audio support [283812.521265] radeon 0000:01:00.0: GPU lockup CP stall for more than 1000msec [283812.521269] --------[ cut here ]-------- [283812.521294] WARNING: at /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x365/0x3d0 [radeon]() [283812.521297] Hardware name: [283812.521299] GPU lockup (waiting for 0x00AE670A last fence id 0x00AE6705) [283812.521301] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs nls_utf8 udf ip6table_filter ip6_tables binfmt_misc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm parport_pc ppdev snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_ac97_codec ac97_bus snd_pcm snd_page_alloc snd_util_mem snd_hwdep snd_seq_midi radeon snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device ttm snd pl2303 drm_kms_helper coretemp usbserial joydev psmouse sou