[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#650090: marked as done (Failed to load firmware "radeon/R520_cp.bin")

Your message dated Sun, 27 Nov 2011 18:53:11 +0000
with message-id <1322419991.7454.23.camel@deadeye>
and subject line Re: Bug#650090: Failed to load firmware "radeon/R520_cp.bin"
has caused the Debian Bug report #650090,
regarding Failed to load firmware "radeon/R520_cp.bin"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
650090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650090
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package:firmware-linux-nonfree
Dear Maintainer,

I'm on a pc x86-32 Debian testing updated almost every day.
Laptop Sony Vaio VGN-CR31S (Intel Core 2 Duo Processor T8100, Ati Mobility
Radeon X2300).

When I changed some settings on screen saver option, I had a crash (error
message on all the screen) and impossible to use Ctrl+alt+F1 or something, so I
did a reboot.
I noticed these lines in dmesg :
[    9.080838] radeon_cp: Failed to load firmware "radeon/R520_cp.bin"
[    9.080898] [drm:r100_cp_init] *ERROR* Failed to load firmware!
[    9.080955] radeon 0000:01:00.0: failed initializing CP (-2).
[    9.081011] radeon 0000:01:00.0: Disabling GPU acceleration
[    9.081068] [drm] radeon: cp finalized
[    9.081677] radeon 0000:01:00.0: f7193e00 unpin not necessary
[    9.081862] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 245
[    9.081920] Raw EDID:
[    9.081973]          36 7f 40 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082027]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082081]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082135]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082189]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082243]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082297]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082351]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    9.082405] [drm:radeon_atombios_get_lvds_info] *ERROR* Bad LCD record 127

I google searched a little and found this could be a pb of loading order
between udev and kms.
see https://bugzilla.novell.com/show_bug.cgi?id=596268

I'm on kernel 3.1.0-1-686-pae  but I'm pretty sure I've seen this log with
previous version 3.0

Hope it helps.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)

PS : I tried to send this report with reportbug but surely something is bad configured about mail on my laptop.

--- End Message ---
--- Begin Message --- 
On Sun, 2011-11-27 at 10:00 +0100, Julien Nabet wrote:
> Le 27/11/2011 01:01, Ben Hutchings a écrit :
> > On Sat, 2011-11-26 at 18:05 +0100, Julien Nabet wrote:
> >> Le 26/11/2011 17:41, Ben Hutchings a écrit :
> >>> Which version of firmware-linux-nonfree is installed?
> >>>
> >> Hi,
> >>
> >> Version is 0.34.
> > Well the file is definitely still included in this version, so the bug
> > must be somewhere else.  But can you check that it's properly installed,
> > by running 'debsums -c firmware-linux-nonfree'?
> I'm really confused, I thought it was installed and it wasn't.

OK.  The driver should not crash just because the firmware is missing,
and from what you have said I don't believe that was what happened.

If the system crashes again, please take a photograph of the screen such
that the error message is readable, report a bug against the kernel
package (linux-image-3.1.0-1-686-pae or whatever you are running then)
and attach the photograph.

> Here the logs now :
> [    8.203611] [drm] radeon: ring at 0x0000000008001000
> [    8.203643] [drm] ring test succeeded in 9 usecs
> [    8.203785] [drm] radeon: ib pool ready.
> [    8.203864] [drm] ib test succeeded in 0 usecs
> [    8.204051] [drm:drm_edid_block_valid] *ERROR* EDID checksum is 
> invalid, remainder is 245
> [    8.204112] Raw EDID:
> [    8.204164]          36 7f 40 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204220]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204276]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204331]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204386]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204442]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204497]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204552]          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [    8.204607] [drm:radeon_atombios_get_lvds_info] *ERROR* Bad LCD 
> record 127
> Since it's a closed source firmware, I'm not astonished about this kind 
> error.

This error message is unrelated to the firmware; the driver is having
trouble reading the capabilities of the laptop screen.

[...]
> Thank you for the information, I attached the webpage even if now it's 
> no more useful.
[...]

Thanks.  We used to have a bug like that but it was fixed long ago.

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: