Fw: [Bugme-new] [Bug 4217] New: radeonfb makes system hang and LCD "burn"

Begin forwarded message:

Date: Tue, 15 Feb 2005 12:03:52 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4217] New: radeonfb makes system hang and LCD "burn"


http://bugme.osdl.org/show_bug.cgi?id=4217

           Summary: radeonfb makes system hang and LCD "burn"
    Kernel Version: 2.6.11-rc3
            Status: NEW
          Severity: high
             Owner: jsimmons@infradead.org
         Submitter: marc.poulhies@epfl.ch


Distribution: debian sid
Hardware Environment:i686, Radeon Mobility M7 LW [Radeon Mobility 7500]
Software Environment:
Problem Description:
When radeonfb gets loaded, system hangs and LCD display (this is a laptop)
"burns" (seems classic when noone handles the display).

Steps to reproduce:
Starts in single user, then "modprobe radeonfb"

I tried to get some debug information by compiling the debug support, but I
can't get kernel message to another computer (I tried with netcat).
This seems to cause some problem with DRI also. I boot without radeonfb, X
starts, then a switch to console has the same effect (freeze + "burn")

(same with -rc4)

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

On Tue, 2005-02-15 at 12:15 -0800, Andrew Morton wrote:

Begin forwarded message:

Date: Tue, 15 Feb 2005 12:03:52 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4217] New: radeonfb makes system hang and LCD "burn"

What if you load the module with option "default_dynclk=-1" ?

(Or if radeonfb is built-in, do radeonfb.default_dynclk=-1 on the kernel
command line). 

Ben.

http://bugme.osdl.org/show_bug.cgi?id=4217

           Summary: radeonfb makes system hang and LCD "burn"
    Kernel Version: 2.6.11-rc3
            Status: NEW
          Severity: high
             Owner: jsimmons@infradead.org
         Submitter: marc.poulhies@epfl.ch


Distribution: debian sid
Hardware Environment:i686, Radeon Mobility M7 LW [Radeon Mobility 7500]
Software Environment:
Problem Description:
When radeonfb gets loaded, system hangs and LCD display (this is a laptop)
"burns" (seems classic when noone handles the display).

Steps to reproduce:
Starts in single user, then "modprobe radeonfb"

I tried to get some debug information by compiling the debug support, but I
can't get kernel message to another computer (I tried with netcat).
This seems to cause some problem with DRI also. I boot without radeonfb, X
starts, then a switch to console has the same effect (freeze + "burn")

(same with -rc4)

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-- 
Benjamin Herrenschmidt [off-list ref]



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Benjamin Herrenschmidt [off-list ref] writes:

On Tue, 2005-02-15 at 12:15 -0800, Andrew Morton wrote:

quoted

Begin forwarded message:

Date: Tue, 15 Feb 2005 12:03:52 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4217] New: radeonfb makes system hang and LCD "burn"

What if you load the module with option "default_dynclk=-1" ?

(Or if radeonfb is built-in, do radeonfb.default_dynclk=-1 on the kernel
command line). 

Seems to work a bit more. Module loads correctly, system is still
responding, but display is not correct. System caret seems to be the
only thing displayed, and it moves when I type, but no characters get
displayed.

Do you need some more informations? (like debug output) 

Thanks,
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

On Tue, 2005-02-15 at 22:42 +0100, Marc Poulhiès wrote:

Benjamin Herrenschmidt [off-list ref] writes:

quoted

On Tue, 2005-02-15 at 12:15 -0800, Andrew Morton wrote:

quoted

Begin forwarded message:

Date: Tue, 15 Feb 2005 12:03:52 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4217] New: radeonfb makes system hang and LCD "burn"

What if you load the module with option "default_dynclk=-1" ?

(Or if radeonfb is built-in, do radeonfb.default_dynclk=-1 on the kernel
command line). 

Seems to work a bit more. Module loads correctly, system is still
responding, but display is not correct. System caret seems to be the
only thing displayed, and it moves when I type, but no characters get
displayed.

Do you need some more informations? (like debug output) 

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

The "dynclk" thing has issues, the upstream code from ATI has some bugs
plus there is something weird going on which I suspect might be a
miscompile of a bit of code in there. I'll send a patch working around
that today.

Ben.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click

Benjamin Herrenschmidt [off-list ref] writes:

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

The "dynclk" thing has issues, the upstream code from ATI has some bugs
plus there is something weird going on which I suspect might be a
miscompile of a bit of code in there. I'll send a patch working around
that today.

Ben.

Ok, did that. Same result. The only thing displayed is the system
caret. I can see it moving left and right while the system boots and
"displays" the messages (X is working nicely).

I did compile debug support, so I'm including the output.

Tell me if I can test something else,
Thanks very much,

Marc

debug output:

radeonfb (0000:01:00.0): Found 32768k of DDR 64 bits wide videoram
radeonfb (0000:01:00.0): mapped 16384k videoram
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=230.00 Mhz, System=166.00 MHz
radeonfb: PLL min 12000 max 35000
1 chips in connector info
 - chip 1 has 1 connectors
  * connector 0 of type 2 (CRT) : 2300
Starting monitor auto detection...
radeonfb: I2C (port 1) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 4) ... not found
Non-DDC laptop panel detected
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: QDI QD141F1LH01         
radeonfb: detected LVDS panel size from BIOS: 1400x1050
BIOS provided panel power delay: 1500
radeondb: BIOS provided dividers will be used
ref_divider = 6
post_divider = 4
fbk_divider = 48
Scanning BIOS table ...
 320 x 350
 320 x 400
 320 x 400
 320 x 480
 400 x 600
 512 x 384
 640 x 350
 640 x 400
 640 x 475
 640 x 480
 720 x 480
 720 x 576
 800 x 600
 848 x 480
 1024 x 768
 1152 x 864
 1280 x 1024
 1400 x 1050
Found panel in BIOS table:
  hblank: 288
  hOver_plus: 40
  hSync_width: 112
  vblank: 13
  vOver_plus: 0
  vSync_width: 3
  clock: 10800
Setting up default mode based on panel info
radeonfb (0000:01:00.0): ATI Radeon LW 
radeonfb_pci_register END


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

On Wed, 2005-02-16 at 19:43 +0100, Marc Poulhiès wrote:

Benjamin Herrenschmidt [off-list ref] writes:

quoted

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

The "dynclk" thing has issues, the upstream code from ATI has some bugs
plus there is something weird going on which I suspect might be a
miscompile of a bit of code in there. I'll send a patch working around
that today.

Ben.

Ok, did that. Same result. The only thing displayed is the system
caret. I can see it moving left and right while the system boots and
"displays" the messages (X is working nicely).

I did compile debug support, so I'm including the output.

Well... looks like radeonfb is actually working ... You can try booting
with radeonfb.noaccel=1 on your kernel command line and tell me what's
up ? I looks like your fbcon is having trouble actually. Not sure what's
up, I haven't had any report of that so far.

Ben.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click

Benjamin Herrenschmidt [off-list ref] writes:

On Wed, 2005-02-16 at 19:43 +0100, Marc Poulhiès wrote:

quoted

Benjamin Herrenschmidt [off-list ref] writes:

quoted

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

Ok, did that. Same result. The only thing displayed is the system
caret. I can see it moving left and right while the system boots and
"displays" the messages (X is working nicely).

Well... looks like radeonfb is actually working ... You can try booting
with radeonfb.noaccel=1 on your kernel command line and tell me what's
up ? I looks like your fbcon is having trouble actually. Not sure what's
up, I haven't had any report of that so far.

Same result as without (screen "burns").

Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

On Thu, 2005-02-17 at 09:02 +0100, Marc Poulhiès wrote:

Benjamin Herrenschmidt [off-list ref] writes:

quoted

On Wed, 2005-02-16 at 19:43 +0100, Marc Poulhiès wrote:

quoted

Benjamin Herrenschmidt [off-list ref] writes:

quoted

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

Ok, did that. Same result. The only thing displayed is the system
caret. I can see it moving left and right while the system boots and
"displays" the messages (X is working nicely).

Well... looks like radeonfb is actually working ... You can try booting
with radeonfb.noaccel=1 on your kernel command line and tell me what's
up ? I looks like your fbcon is having trouble actually. Not sure what's
up, I haven't had any report of that so far.

Same result as without (screen "burns").

Well, I sent a patch that might fix the "burning" effect, if you could
get the latest bk, and try again...

Thanks,
Ben.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click

Benjamin Herrenschmidt [off-list ref] writes:

quoted

quoted

quoted

quoted

Try building radeonfb in the kernel and booting with
radeonfb.default_dynclk=-1, let me know if that works. fbdev's in
modules have always been sort-of dodgy....

Ok, did that. Same result. The only thing displayed is the system
caret. I can see it moving left and right while the system boots and
"displays" the messages (X is working nicely).

Well... looks like radeonfb is actually working ... You can try booting
with radeonfb.noaccel=1 on your kernel command line and tell me what's
up ? I looks like your fbcon is having trouble actually. Not sure what's
up, I haven't had any report of that so far.

Same result as without (screen "burns").

Well, I sent a patch that might fix the "burning" effect, if you could
get the latest bk, and try again...

I tried with rc4-bk4 (hope this is correct. I checked changelog and saw
a change on radeonfb concerning some prob with laptop), but still the
same burning effect...

Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click