https://bugs.freedesktop.org/show_bug.cgi?id=56561
Priority: medium Bug ID: 56561 Assignee: dri-devel@lists.freedesktop.org Summary: kernel > 3.4.7 breaks KMS on rv515 (r300) Severity: major Classification: Unclassified OS: Linux (All) Reporter: inaudible@simplesuperlativ.es Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI
I performed a system update (arch linux) but have experienced issues with KMS on any kernel past 3.4.7 (all of 3.5 up till the current 3.6.3). The boot sequence stalls at the point where the KMS hooks usually kick in and referesh the screen. I can make the kernel boot with 'nomodeset' option.
https://bugs.freedesktop.org/show_bug.cgi?id=54662 looks similar, but the none of the 3.6 kernels i've tried resove this issue.
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #1 from dmotd inaudible@simplesuperlativ.es --- I'm not sure how to provide debugging info for this problem, the boot just stalls at the point of starting KMS, a blinking cursor is active but nothing loads beyond this point, there are no errors printed to screen and there are no logs saved from the failed session.
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #2 from dmotd inaudible@simplesuperlativ.es --- Created attachment 69269 --> https://bugs.freedesktop.org/attachment.cgi?id=69269&action=edit dmesg - successful boot kernel 3.4.7
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #3 from dmotd inaudible@simplesuperlativ.es --- Created attachment 69270 --> https://bugs.freedesktop.org/attachment.cgi?id=69270&action=edit Xorg.0.log - successful boot kernel 3.4.7
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #4 from dmotd inaudible@simplesuperlativ.es --- Created attachment 69271 --> https://bugs.freedesktop.org/attachment.cgi?id=69271&action=edit dmesg - failing kernel 3.6.3 running with 'nomodeset'
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #5 from dmotd inaudible@simplesuperlativ.es --- Created attachment 69272 --> https://bugs.freedesktop.org/attachment.cgi?id=69272&action=edit Xorg.0.log - failing kernel 3.6.3 running with 'nomodeset'
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #6 from Michel Dänzer michel@daenzer.net --- Do newer kernels work without radeon driver options on the kernel command line, in particular without radeon.msi=0?
If not, can you bisect which kernel change introduced the problem?
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #7 from Alex Deucher agd5f@yahoo.com --- Make sure you have the radeon firmware installed and available in your initrd if you are using one.
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #8 from dmotd inaudible@simplesuperlativ.es --- (In reply to comment #6)
Do newer kernels work without radeon driver options on the kernel command line, in particular without radeon.msi=0?
If not, can you bisect which kernel change introduced the problem?
The kernel command line options do not effect the later kernels.
I will need some spare time to bisect, although this bug report looks to be relevant, -- https://bugzilla.redhat.com/show_bug.cgi?id=845745 -- user 'Richard Gration' is running the exact same laptop setup as here and experiencing identical issues.
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #9 from dmotd inaudible@simplesuperlativ.es --- (In reply to comment #7)
Make sure you have the radeon firmware installed and available in your initrd if you are using one.
The firmware should be loading (I am using stock arch linux kernels), when 3.4.7 or 3.6.3-nomodeset boots I see '[drm] Loading R500 Microcode' in the logs. (Sorry I wrote r300 in the bug title which should be r500).
https://bugs.freedesktop.org/show_bug.cgi?id=56561
--- Comment #10 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #9)
The firmware should be loading (I am using stock arch linux kernels), when 3.4.7 or 3.6.3-nomodeset boots I see '[drm] Loading R500 Microcode' in the logs. (Sorry I wrote r300 in the bug title which should be r500).
The ums driver loads later (when the filesystem is available). If there is no firmware in your initrd, the kernel firmware loader will wait several minutes to timeout before continuing. Can you boot into a non-X runlevel with nomodeset and then try and modprobe radeon manually from the console?
https://bugs.freedesktop.org/show_bug.cgi?id=56561
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #11 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/309.
dri-devel@lists.freedesktop.org