[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Tags added: kernel-key-gfxpayload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605614 Title: [ATI] GPU lockup with gfxpayload=keep -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I'm closing the Maverick linux kernel task for now as grub2 switched back to default to gfxpayload=text for Maverick. However, we do want to keep the linux task open for Natty. Thanks. ** Changed in: linux (Ubuntu Maverick) Status: New => Won't Fix -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Also affects: grub2 (Ubuntu Maverick) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Maverick) Importance: Undecided Status: New -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Branch linked: lp:ubuntu/grub2 -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
This bug was fixed in the package grub2 - 1.98+20100804-4ubuntu1
---
grub2 (1.98+20100804-4ubuntu1) maverick; urgency=low
* Resynchronise with Debian. Remaining changes:
- Adjust for default Ubuntu boot options ("quiet splash").
- Default to hiding the menu; holding down Shift at boot will show it.
- Set a monochromatic theme for Ubuntu.
- Apply Ubuntu GRUB Legacy changes to legacy update-grub script: title,
recovery mode, quiet option, tweak how memtest86+ is displayed, and
use UUIDs where appropriate.
- Fix backslash-escaping in merge_debconf_into_conf.
- Remove "GNU/Linux" from default distributor string.
- Add crashkernel= options if kdump and makedumpfile are available.
- If other operating systems are installed, then automatically unhide
the menu. Otherwise, if GRUB_HIDDEN_TIMEOUT is 0, then use keystatus
if available to check whether Shift is pressed. If it is, show the
menu, otherwise boot immediately. If keystatus is not available, then
fall back to a short delay interruptible with Escape.
- Allow Shift to interrupt 'sleep --interruptible'.
- Don't display introductory message about line editing unless we're
actually offering a shell prompt. Don't clear the screen just before
booting if we never drew the menu in the first place.
- Remove some verbose messages printed before reading the configuration
file.
- Suppress progress messages as the kernel and initrd load for
non-recovery kernel menu entries.
- Change prepare_grub_to_access_device to handle filesystems
loop-mounted on file images.
- Ignore devices loop-mounted from files in 10_linux.
- Show the boot menu if the previous boot failed, that is if it failed
to get to the end of one of the normal runlevels.
- Handle RAID devices containing virtio components.
- Don't generate /boot/grub/device.map during grub-install or
grub-mkconfig by default.
- Adjust upgrade version checks for Ubuntu.
- Don't display "GRUB loading" unless Shift is held down.
- Adjust versions of grub-doc and grub-legacy-doc conflicts to tolerate
our backport of the grub-doc split.
- Fix LVM/RAID probing in the absence of /boot/grub/device.map.
- Look for .mo files in /usr/share/locale-langpack as well, in
preference.
- Make sure GRUB_TIMEOUT isn't quoted unnecessarily.
- Probe all devices in 'grub-probe --target=drive' if
/boot/grub/device.map is missing.
- Adjust hostdisk id for hard disks, allowing grub-setup to use its
standard workaround for broken BIOSes.
- Build-depend on qemu-kvm rather than qemu-system for grub-pc tests.
- Use qemu rather than qemu-system-i386.
- Extend the EFI version of grub-install to be able to install into an
EFI System Partition mounted on /boot/efi in a location that complies
with the EFI specification.
- Upgrade the installed core image when upgrading grub-efi-ia32 or
grub-efi-amd64, although only if /boot/efi/EFI/ubuntu already exists.
- Make grub-efi-ia32 and grub-efi-amd64 depend on efibootmgr so that
grub-install works properly.
- Program vesafb on BIOS systems rather than efifb.
* Go back to gfxpayload=text by default for Ubuntu 10.10, as the kernel
needs more work to avoid lockups with some video cards
(LP: #605614, #608429, #612626).
grub2 (1.98+20100804-4) unstable; urgency=low
[ Updated translations ]
* Italian (it.po) by Luca Monducci (closes: #593685).
* Finnish (fi.po) by Esko Arajärvi (closes: #593921).
[ Colin Watson ]
* Run update-grub from kernel hooks if DEB_MAINT_PARAMS is unset, for
compatibility with old kernel packages. This may produce duplicate runs
of update-grub, but that's better than not running it at all (closes:
#594037).
grub2 (1.98+20100804-3) unstable; urgency=low
[ Updated translations ]
* Brazilian Portuguese (pt_BR.po) by Flamarion Jorge (closes: #592156).
* Asturian (ast.po) by Maacub (closes: #592313).
* Galician (gl.po) by Jorge Barreiro (closes: #592816).
[ Robert Millan ]
* Backport ZFS bugfixes from upstream Bazaar:
- zfs_fix_chroot.patch: Fix breakage when running grub-probe inside chroot.
- zfs_fix_label_arg.patch: Fix grub-probe fs_label argument.
- zfs_fix_pathname.patch: Fix pathname for non-root ZFS filesystems.
- zfs_fix_segfault.patch: Fix segfault when /dev is not mounted.
[ Colin Watson ]
* Escape single quotes when removing them from $mode in zz-update-grub, so
that this works when /bin/sh is bash (thanks, Will Dyson; closes:
#593242).
* Add support for ext2 root on GNU/kFreeBSD (thanks, Aurelien Jarno;
closes: #593467).
grub2 (1.98+20100804-2) unstable; urgency=low
[ Colin Watson ]
* Make /etc/kernel/postrm.d/zz-update-grub a real file rather than a
symlink (closes: #592076).
[ Updated translations ]
* Norwegian Bokmål (nb.po
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Branch linked: lp:~ubuntu-core-dev/ubuntu/maverick/grub2/maverick -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Still having the same startup problems. Just did the last Maverick Meerkat partial upgrade. Then I tried to reinstall VMWare Tools, but it failed. On reboot I got a black sccreen. Then I restarted aagain and got the reboot menu. there I was able to adjust gfxpayload=text and boot up the latest kernel again FYI: $ uname -a Linux ubuntu 2.6.35-15-generic #21-Ubuntu SMP Wed Aug 11 16:41:40 UTC 2010 i686 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.10 DISTRIB_CODENAME=maverick DISTRIB_DESCRIPTION="Ubuntu maverick (development branch)" -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
This is still happening for me on 2.6.35-12.17 ; just get a black screen, removing the set gfxpayload and I'm back in business. (Hd4350 on i7) Dave -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
This here is with 2.6.35-12.17 and "set gfxpayload=keep". At first boot I get some garbage when X starts (on both my monitors) but after a reboot X starts up fine. Here is some kernel log from the first unsuccessful boot: Jul 30 09:19:48 vorlon kernel: [ 21.819264] [ cut here ] Jul 30 09:19:48 vorlon kernel: [ 21.819288] WARNING: at /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x365/0x3d0 [radeon]() Jul 30 09:19:48 vorlon kernel: [ 21.819290] Hardware name: M56S-S3 Jul 30 09:19:48 vorlon kernel: [ 21.819292] GPU lockup (waiting for 0x0003 last fence id 0x0001) Jul 30 09:19:48 vorlon kernel: [ 21.819293] Modules linked in: snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec radeon snd_hwdep snd_seq_midi snd_pcm ttm snd_rawmidi drm_kms_helper snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse drm snd serio_raw i2c_algo_bit k8temp i2c_nforce2 soundcore ppdev edac_core edac_mce_amd snd_page_alloc parport_pc lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath ahci firewire_ohci firewire_core crc_itu_t linear forcedeth pata_amd libahci Jul 30 09:19:48 vorlon kernel: [ 21.819329] Pid: 1086, comm: Xorg Tainted: G D 2.6.35-12-generic #17-Ubuntu Jul 30 09:19:48 vorlon kernel: [ 21.819331] Call Trace: Jul 30 09:19:48 vorlon kernel: [ 21.819338] [] warn_slowpath_common+0x7f/0xc0 Jul 30 09:19:48 vorlon kernel: [ 21.819341] [] warn_slowpath_fmt+0x46/0x50 Jul 30 09:19:48 vorlon kernel: [ 21.819354] [] radeon_fence_wait+0x365/0x3d0 [radeon] Jul 30 09:19:48 vorlon kernel: [ 21.819358] [] ? autoremove_wake_function+0x0/0x40 Jul 30 09:19:48 vorlon kernel: [ 21.819370] [] radeon_sync_obj_wait+0x11/0x20 [radeon] Jul 30 09:19:48 vorlon kernel: [ 21.819378] [] ttm_bo_wait+0x103/0x1c0 [ttm] Jul 30 09:19:48 vorlon kernel: [ 21.819392] [] radeon_gem_wait_idle_ioctl+0x97/0x140 [radeon] Jul 30 09:19:48 vorlon kernel: [ 21.819407] [] drm_ioctl+0x34a/0x4c0 [drm] Jul 30 09:19:48 vorlon kernel: [ 21.819421] [] ? radeon_gem_wait_idle_ioctl+0x0/0x140 [radeon] Jul 30 09:19:48 vorlon kernel: [ 21.819425] [] ? _raw_spin_lock_irq+0x15/0x20 Jul 30 09:19:48 vorlon kernel: [ 21.819430] [] ? handle_signal+0x131/0x280 Jul 30 09:19:48 vorlon kernel: [ 21.819432] [] ? do_signal+0x81/0x1a0 Jul 30 09:19:48 vorlon kernel: [ 21.819436] [] vfs_ioctl+0x3d/0xd0 Jul 30 09:19:48 vorlon kernel: [ 21.819438] [] do_vfs_ioctl+0x81/0x340 Jul 30 09:19:48 vorlon kernel: [ 21.819441] [] ? sys_rt_sigreturn+0x235/0x250 Jul 30 09:19:48 vorlon kernel: [ 21.819444] [] sys_ioctl+0x81/0xa0 Jul 30 09:19:48 vorlon kernel: [ 21.819447] [] system_call_fastpath+0x16/0x1b Jul 30 09:19:48 vorlon kernel: [ 21.819449] ---[ end trace d3627d239cbe15f9 ]--- Jul 30 09:19:48 vorlon kernel: [ 21.819456] [drm] Disabling audio support Jul 30 09:19:48 vorlon kernel: [ 21.820513] radeon :02:00.0: GPU softreset Jul 30 09:19:48 vorlon kernel: [ 21.820516] radeon :02:00.0: R_008010_GRBM_STATUS=0xA0003030 Jul 30 09:19:48 vorlon kernel: [ 21.820518] radeon :02:00.0: R_008014_GRBM_STATUS2=0x0003 Jul 30 09:19:48 vorlon kernel: [ 21.820521] radeon :02:00.0: R_000E50_SRBM_STATUS=0x200208C0 Jul 30 09:19:48 vorlon kernel: [ 21.968630] radeon :02:00.0: Wait for MC idle timedout ! Jul 30 09:19:48 vorlon kernel: [ 21.968633] radeon :02:00.0: R_008020_GRBM_SOFT_RESET=0x7FEE Jul 30 09:19:48 vorlon kernel: [ 21.983646] radeon :02:00.0: R_008020_GRBM_SOFT_RESET=0x0001 Jul 30 09:19:48 vorlon kernel: [ 21.999644] radeon :02:00.0: R_008010_GRBM_STATUS=0x3030 Jul 30 09:19:48 vorlon kernel: [ 21.999647] radeon :02:00.0: R_008014_GRBM_STATUS2=0x0003 Jul 30 09:19:48 vorlon kernel: [ 21.999649] radeon :02:00.0: R_000E50_SRBM_STATUS=0x200208C0 Jul 30 09:19:48 vorlon kernel: [ 22.000665] radeon :02:00.0: GPU reset succeed Jul 30 09:19:48 vorlon kernel: [ 22.002215] [drm] Clocks initialized ! Jul 30 09:19:49 vorlon kernel: [ 22.150225] radeon :02:00.0: Wait for MC idle timedout ! Jul 30 09:19:49 vorlon kernel: [ 22.298149] radeon :02:00.0: Wait for MC idle timedout ! Jul 30 09:19:49 vorlon kernel: [ 22.481493] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD) Jul 30 09:19:49 vorlon kernel: [ 22.481498] [drm:r600_resume] *ERROR* r600 startup failed on resume And after that many lines: Jul 30 09:20:00 vorlon kernel: [ 33.458963] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). Jul 30 09:20:00 vorlon kernel: [ 33.458965] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! Jul 30 09:20:00 vorlon kernel: [ 33.459062] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). Jul 30 09:20:00 vorlon kernel: [ 33.459064] [drm:radeon_cs_ioctl] *ERROR* Fa
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I have just installed the new 2.6.35-12.17 kernel. It is now hit and miss as to whether I can boot to a graphical desktop. I sometimes get corruption at shutdown. The weird thing is that if I get corruption at shutdown, it will boot to gdm, yet when the ubuntu logo is displayed at shutdown, the next boot locks and I have to ctl-alt-f2 and restart. I also have updated mesa to 7.9.0+git20100727. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I am able to boot now with 2.6.35-11 kernel, but I do get a moment of screen corruption when the ubuntu splash is supposed to be displayed ( it is not) and then a normal procession to gdm login screen. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I've checked linux-image-2.6.35-11-generic 2.6.35-11.16 and with "set gfxpayload=keep" my box boots again into X. If only bug 605843 would get fixed soon too, then I could use this kernel and gfxpayload=keep. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Tags removed: kernel-candidate -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
We believe that this may be fixed by updates in the latest Maverick kernel. Could you test that (it should work with lucid userspace). Please test and report back here. Thanks. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I appear to have the same problem with my plain vanilla Compaq C700 laptop (Celeron 560 processor, integrated graphics), except for the small oddity that the boot process stalls with two side-by-side static Ubuntu logos displayed in the top half of the screen, rather than having an entirely dark screen. I can't now be certain which version of the kernel introduced the problem. I know that 2.6.35.6 (the original Alpha 2 version) worked OK, and I know that the problem has persisted through versions -9 and -10. To date, I have worked around the issue simply by booting in recovery mode and manually restarting the X system. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
** Tags added: kj-triage -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
no image on the monitor after booting Maverick with a newly inserted ATI Radeon HD 3450. cannot switch to the text consoles I'm going to try some workarounds and post back. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Have them same Issue using Maverick Meerkat and 2.6.35.x kernel in VmWare Fusion Virtual Box 3.1.0 . I have attached the latest 100 syslog lines. I can startup Ubuntu MM using set gfxpayload=text instead of set gfxpayload=keep , but loading is still slow. And of course I would prefer a more permanent fix. ** Attachment added: "syslog latest 100 lines" http://launchpadlibrarian.net/52121078/syslog.text -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Have them same Issue using Maverick Meerkat and 2.6.35.x kernel in VmWare Fusion Virtual Box 3.1.0 . I have attached the latest 1oo syslog lines. I can startup Ubuntu MM using set gfxpayload=text instead of set gfxpayload=keep , but loading is still slow. And of course I would prefer a more permanent fix. ** Attachment added: "syslog latest 100 lines" http://launchpadlibrarian.net/52121071/syslog.text -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Also happens for me; upgrade from Lucid - Radeon HD4350 on an ASRock P55M Pro Dave -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
One more stupid question: Where would this syslog be located? Also I want to make a note on the VM I'm using. It's being used on VMware Workstation 7.1 which have my own personal flavor of open-vm- tools (located here: https://launchpad.net/~n-muench/+archive/ppa/+packages), since the packages currently available in Maverick aren't compatible with Maverick. My flavor is the one from Maverick's repos, but with the necessary patches (from this bug report: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/598542) to make it work with Maverick. I also a forthcoming build of open-vm-tools which is the newest version (from June), and comes with the Debian config (there's been 2 revisions for this release so far), and the updated patches (to make it work with Maverick). -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
On Thu, Jul 15, 2010 at 07:45:11PM -, Nate Muench wrote: > 1) How do it extract the syslog? Assuming that it doesn't lock up so badly that it can't write to the syslog, then you should just be able to boot again with 'set gfxpayload=text' and then look back in the syslog to the previous boot attempt. > 2) I assume you want the the log with the GRUB that works, not the one > that doesn't. No - logs of things working are boring. Logs of things failing are interesting. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Colin, 2 questions: 1) How do it extract the syslog? 2) I assume you want the the log with the GRUB that works, not the one that doesn't. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
It would be far simpler to add this line to /etc/default/grub: GRUB_GFXPAYLOAD_LINUX=text Doing that is fine to get things going again for you - it would be good if you could be available to revert that once the kernel folks have a candidate fix to test, though. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
# Use a simple linear framebuffer appropriate to the platform if support
# for it is known to be built into the kernel. We need it to be built-in
# rather than modular, as otherwise early output from the kernel won't
# work.
Sorry I made an error in my cut and paste
if [ "x$GRUB_GFXPAYLOAD_LINUX" = x ]; then
cat << EOF
load_video
EOF
if [ "x$LINUX_CONFIG_FB" != x ] \
&& grep -qx "$LINUX_CONFIG_FB=y" /boot/config-${version} 2> /dev/null \
&& grep -qx "CONFIG_VT_HW_CONSOLE_BINDING=y" /boot/config-${version} 2>
/dev/null; then
cat << EOF
set gfxpayload=text# change keep to text?
EOF
fi
else
cat << EOF
set gfxpayload=$GRUB_GFXPAYLOAD_LINUX
EOF
fi
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Would it be a bad idea for me to edit /etc/grub.d/10_linux to change:
# Use a simple linear framebuffer appropriate to the platform if support
# for it is known to be built into the kernel. We need it to be built-in
# rather than modular, as otherwise early output from the kernel won't
# work.
if [ "x$GRUB_GFXPAYLOAD_LINUX" = x ]; then
cat << EOF
load_video
EOF
if [ "x$LINUX_CONFIG_FB" != x ] \
&& grep -qx "$LINUX_CONFIG_FB=y" /boot/config-${version} 2> /dev/null \
&& grep -qx "CONFIG_VT_HW_CONSOLE_BINDING=y" /boot/config-${version} 2>
/dev/null; then
cat << EOF
EOF
fi
else
cat << EOF
set gfxpayload=$GRUB_GFXPAYLOAD_LINUX
EOF
fi
changing set gfxpayload=keep to set gfxpayload=text?
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
In addition to comment #4 When I try to use 'set gfxpayload=keep' after my screen goes bad I can get a terminal with ctl-alt-f2 and login and reboot. On f1 I get this [drm_radeon_cs_ioctl] *ERROR* Faild to schedult IB! followed by a bunch of similar messages. In logs I have this: log attached. ** Attachment added: "radeon-log-payload-keep" http://launchpadlibrarian.net/51977678/radeon-log-payload-keep -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
Nate, it's interesting that you're seeing this in a VM. Perhaps you could file a separate bug for that, and extract the syslog from that boot attempt and attach it? (It may be the same type of issue, but this will probably be driver- specific to some extent, so I'd like to keep instances for different drivers separate.) -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605614] Re: [ATI] GPU lockup with gfxpayload=keep
I'd like to give the kernel guys an opportunity to debug this; we did expect some problems switching from VESA to native, but we were never going to shake them out without giving it a try. I expect it's possible to blacklist cards from gfxpayload=keep with a bit of work, although I'd like to save that for a last resort. -- [ATI] GPU lockup with gfxpayload=keep https://bugs.launchpad.net/bugs/605614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
