[Ubuntu-x-swat] [Bug 1100286] Re: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
Tried the thing with cat /etc/modprobe.d/radeon-kms.conf options radeon modeset=0 which was proposed in older versions as workaround. but it is not acceptable. Works only with low resolution and no evidence that the bug goes away. Had it again, however! Kernel = Linux atviedl2a149 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1100286 Title: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1100286/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1100286] Re: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
Trying: cat /etc/modprobe.d/radeon-kms.conf options radeon modeset=0 which was proposed in older versions as workaround. Has anybody tried this already? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1100286 Title: [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1100286/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Hi all, I really apoligize for that, still don't know what was going on. Sorry, Klaus -- Klaus Reichlklaus.rei...@gmail.com Danhausergasse 8/16 +43 6991 84 137 94 1040 Wien On Tue, Jun 5, 2012 at 9:33 PM, Zentai Andras <727...@bugs.launchpad.net>wrote: > Really clever way to invite all bug subscribers to your LinkedIn > network... ;) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/727620 > > Title: > [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in > normal boot (Hybrid graphics) > > Status in The Linux Kernel: > Confirmed > Status in X.org XServer - ATI gfx chipset driver: > Fix Released > Status in “linux” package in Ubuntu: > Fix Released > Status in “xserver-xorg-video-ati” package in Ubuntu: > Invalid > > Bug description: > [Problem] > On hybrid graphics hardware with this ATI chip and another (e.g. Intel), > a failure occurs resulting in a black screen and errors from the radeon > kernel module, as shown below. > > [Cause] > From upstream developer: > > "The switcheroo code needs more work to switch properly on some > systems it seems. There are a set acpi methods required to > activate/deactivate the respective gpus. The drivers need to load and > initialize active hw. If the hw is not active when the driver loads, > then the hw is not set up properly and it won't work. Probably some > ordering issues in how the switcheroo acpi methods are called." > > [Workarounds] > Several options: > > 1. If your BIOS includes functionality to disable the Intel card, use > BIOS settings to select which chip to load. > > 2. Disable KMS by adding `radeon.modeset=0` in the boot line. Note > that the default radeon gallium driver only works with KMS, so YMMV. > > [Original Report] > I'm running natty, and every since the upgrade to 6.14.0 I've been unable > to consistently boot. After some discussion in the forums, I tried > repeatedly to boot into recovery mode. In most cases, I got a black > screen. One time though, when I was able to successfully increase the > brightness, I saw some errors from the radeon module. I took a photo > (available at http://i.imgur.com/P0bQ0.jpg), and here's the stack and > call trace, as best as I can read it: > > Stack: > 880149eb8000 880149eb8000 0011 0911 > fff4 88014b6c7800 88014b0f7b58 a022aba0 > 8801460f7b58 880149eb8000 00410028 > Call Trace: > [] evergreen_cp_resume+0x3a0/0x630 [radeon] > [] evergreen_startup+0x157/0x260 [radeon] > [] ? r600_pcie_gart_init+0x60/0x70 [radeon] > [] evergreen_init+0x1ac/0x2d0 [radeon] > [] radeon_device_init+0x409/0x490 [radeon] > [] radeon_driver_load_kms+0xb2/0x1a0 [radeon] > [] drm_get_pci_dev+0x18e/0x300 [drm] > [] ? kmem_cache_alloc_trace+0xff/0x120 > [] radeon_pci_probe+0xb2/0xba [radeon] > [] local_pci_probe+0x5f/0xd0 > [] pci_device_probe+0x119/0x120 > [] ? driver_sysfs_add+0x7a/0xb0 > [] really_probe+0x68/0x190 > [] driver_probe_device+0x45/0x70 > [] __driver_attach+0xab/0xb0 > [] ? __driver_attach+0x0/0xb0 > [] bus_for_each_dev+0x5e/0x90 > [] driver_attach+0x1e/0x20 > [] bus_add_driver+0xc5/0x280 > [] ? radeon_init+0x0/0x1000 [radeon] > [] driver_register+0x76/0x140 > [] ? radeon_init+0x0/0x1000 [radeon] > [] __pci_register_driver+0x56/0xd0 > [] drm_pci_init+0xe4/0xf0 [drm] > [] ? mutex_lock+0x1e/0x50 > [] ? radeon_init+0x0/0x1000 [radeon] > [] drm_init+0x58/0x70 [drm] > [] radeon_init+0xc4/0x1000 [radeon] > [] do_one_initcall+0x45/0x190 > [] sys_init_module+0x103/0x260 > [] system_call_fastpath+0x16/0x1b > Code: 00 45 8b 84 24 e4 0a 00 00 45 85 c0 0f 8e c7 09 00 00 41 8b 84 24 > d4 0a 00 00 89 c2 83 c0 01 40 c1 e2 02 49 03 94 24 c8 0a 00 00 02 00 > 44 05 c0 41 8b 94 24 e4 0a 00 00 41 23 84 24 f4 0a 00 > RIP [] evergreen_cp_start+0x57/0xc80 [radeon] > RSP > CRZ: c90411ce1ffc > ---[ end trace 37702c56f2e23247 ]--- > udevd-work[94]: '/sbin/modprobe -bv > pci:v1002d68C1sv103Csd1436bc03sc00i00' unexpected exit with > status 0x0009 > > There is also some register info dumped at the top of the screen > visible in the photo, that I didn't bother to write, as I'd most > certainly get something wrong. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/727620/+subscriptions > -- You received this bug notification because you are a member of
[Ubuntu-x-swat] [Bug 727620] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Klaus Klaus Reichl Technology Expert at Thales Austria Confirm that you know Klaus Reichl: https://www.linkedin.com/e/-23x794-h2wwfi1a-25/isd/7319909931/SX7S-eb-/?hs=false&tok=1GQFJgiCAvq5g1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-23x794-h2wwfi1a-25/7rYzEsOVuzif46I3SgQu1HdVsk49QSkYAnntYjn/goo/727620%40bugs%2Elaunchpad%2Enet/20061/I2488425681_1/?hs=false&tok=0nTcgEXXAvq5g1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Unfortunately I don't have the laptop around where the bug showed up originally for me. I'll be there again on one of the next weekends. But be warned, I thought the bug has gone after updating natty a two weeks ago. I happily installed packages, got googleearth running, everything looked great, and than ... after next reboot - loose loose loose. Switched back to poor graphics with radeon blacklisted to have at least a base system working. Klaus -- Klaus Reichl klaus.rei...@gmail.com Danhausergasse 8/16 +43 6991 84 137 94 1040 Wien On Tue, Jun 21, 2011 at 9:21 PM, Seth Forshee wrote: > Yes, 2.6.39-1 is after 2.6.39-rc7. > > I've been looking between 2.6.39 and 3.0-rc1 now, but nothing stands out > as the change that potentially fixes this issue. The next step is to > perform a bisection to try and locate the commit that fixes the problem. > I'll provide a series of kernels, please test each one and let me know > whether or not it contains the issue. > > Everyone who is able to test please do so, as it can't hurt to have > multiple people testing. > > Bisect build #000 is available at: > > http://people.canonical.com/~sforshee/lp727620/bisect/ > > Bisect log so far (note that since we're hunting for the commit that > fixes the problem, the meanings of 'good' and 'bad' are swapped in the > log). > > # bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1 > # good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39 > git bisect start 'v3.0-rc1' 'v2.6.39' > > ** Changed in: linux (Ubuntu) > Status: In Progress => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/727620 > > Title: > [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in > normal boot (Hybrid graphics) > > Status in The Linux Kernel: > Confirmed > Status in X.org XServer - ATI gfx chipset driver: > Confirmed > Status in “linux” package in Ubuntu: > Incomplete > Status in “xserver-xorg-video-ati” package in Ubuntu: > Triaged > > Bug description: > [Problem] > On hybrid graphics hardware with this ATI chip and another (e.g. Intel), a > failure occurs resulting in a black screen and errors from the radeon kernel > module, as shown below. > > [Cause] > From upstream developer: > > "The switcheroo code needs more work to switch properly on some > systems it seems. There are a set acpi methods required to > activate/deactivate the respective gpus. The drivers need to load and > initialize active hw. If the hw is not active when the driver loads, > then the hw is not set up properly and it won't work. Probably some > ordering issues in how the switcheroo acpi methods are called." > > [Workarounds] > Several options: > > 1. If your BIOS includes functionality to disable the Intel card, use > BIOS settings to select which chip to load. > > 2. Disable KMS by adding `radeon.modeset=0` in the boot line. Note > that the default radeon gallium driver only works with KMS, so YMMV. > > [Original Report] > I'm running natty, and every since the upgrade to 6.14.0 I've been unable to > consistently boot. After some discussion in the forums, I tried repeatedly > to boot into recovery mode. In most cases, I got a black screen. One time > though, when I was able to successfully increase the brightness, I saw some > errors from the radeon module. I took a photo (available at > http://i.imgur.com/P0bQ0.jpg), and here's the stack and call trace, as best > as I can read it: > > Stack: > 880149eb8000 880149eb8000 0011 0911 > fff4 88014b6c7800 88014b0f7b58 a022aba0 > 8801460f7b58 880149eb8000 00410028 > Call Trace: > [] evergreen_cp_resume+0x3a0/0x630 [radeon] > [] evergreen_startup+0x157/0x260 [radeon] > [] ? r600_pcie_gart_init+0x60/0x70 [radeon] > [] evergreen_init+0x1ac/0x2d0 [radeon] > [] radeon_device_init+0x409/0x490 [radeon] > [] radeon_driver_load_kms+0xb2/0x1a0 [radeon] > [] drm_get_pci_dev+0x18e/0x300 [drm] > [] ? kmem_cache_alloc_trace+0xff/0x120 > [] radeon_pci_probe+0xb2/0xba [radeon] > [] local_pci_probe+0x5f/0xd0 > [] pci_device_probe+0x119/0x120 > [] ? driver_sysfs_add+0x7a/0xb0 > [] really_probe+0x68/0x190 > [] driver_probe_device+0x45/0x70 > [] __driver_attach+0xab/0xb0 > [] ? __driver_attach+0x0/0xb0 > [] bus_for_each_dev+0x5e/0x90 > [] driver_attach+0x1e/0x20 > [] bus_add_driver+0xc5
