Bug 14801
Summary: | radeon.modeset=1 boot option crashes system with ATI rc410 card producing garbled system logs | ||
---|---|---|---|
Product: | Drivers | Reporter: | Evgeniy (eumospan) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | alan, alexdeucher, eumospan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | No | Bisected commit-id: | |
Attachments: | excerpts from the syslog of the crashed system, look for the garbled entries |
Description
Evgeniy
2009-12-13 20:53:25 UTC
Created attachment 24170 [details]
excerpts from the syslog of the crashed system, look for the garbled entries
Forgot to tell, that booting without the radeon.modeset=1 option does not seem to freeze the system. Wait and see... reported this bug in launchpad.net https://bugs.launchpad.net/linux/+bug/489447 Can you try 2.6.32 or Dave's drm-radeon-testing branch? http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing There have been a lot of bug fixes since 2.6.31. Thanks Alex, It might.... Sorry, I should have mentioned it before Since 1.6.32.rc7 when booting to GNOME I get no further than gdm. The system gets locked with a black screen and not SysRq keys working. Moreover, 2.6.32 stable and drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/ gave me this even worse situation. Please see this report http://bugzilla.kernel.org/show_bug.cgi?id=14331 Another thing is how can a bug be fixed, if no one knew of it, it seems, before I reported it? I have not seen garbled logs bugs since 2002, let me know if you had. Please let me know Thanks does booting with pci=nomsi fix the problem? If so, this is likely a duplicate of bug https://bugzilla.kernel.org/show_bug.cgi?id=15626 |