Bug 31292
|
Description
David Sterratt
2011-03-17 15:33:33 UTC
Created attachment 51052 [details]
output of lspci with screen detached at boot
I've linked to this bug from here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/751453 Just a quick note that I can reproduce this with 3.1-rc4 It's great that the kernel bugzilla is back. Can you please verify if the problem still exists in the latest upstream kernel? > It's great that the kernel bugzilla is back. Indeed it is :-) I'll have a go with the latest release. Over Christmas I figured out a work-around relating to a BIOS setting. Note that Windows DTRT regardless of which way the BIOS setting is flipped, and I think that would be preferred behaviour on Linux: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/751453 Confirmed with 3.2.1 Zhang Rui, if you (or anyone else) has the slightest hunch to which area of code (which driver or system or whatever) this bug is living, please let me know and I'll start reading. I'm keen to get more involved in kernel bug fixes but I don't know my way around the kernel well enough yet. Thanks! I suppose this is a graphics issue rather than ACPI. re-assign to the graphics experts. Ok, we need an info-dump here: Please attach - full dmesg with drm.debug=0xe added to your kernel commandline - the output of intel_reg_dumper from intel-gpu-tools - and xrandr --verbose for both the broken case (i.e. hotplug not working) and with the bios workaround applied. Reporter seems to have disappeared, closing. If this is still an issue with latest kernels, please reopen with the requested info-dump, thanks. Hi Daniel, sorry for the delay in responding. I still have access to the laptop in question although I have long since moved on to a newer model for my primary machine. The laptop is on loan at the moment and I will have it back next week, after which I can put a modern Linux back on it and start work. (I actually tried, and failed, to sell it recently; I hope to try again). If I may be completely frank for a moment. When I get it back I can put time aside to get the information you have requested. However, on many occasions I've invested a lot of time to triage bugs, particularly kernel bugs, and the issue has never been picked up by a developer afterwards. Once the debug information is provided, are you committing yourself to look at the issue? Alternatively do you know of a kernel hacker who could, or would, commit themselves? If not, then sadly it doesn't seem worth my while (I could spend the same several hours more productively on other bugs). Thanks for your time! Original reporter back on the thread - apologies for going AWOL. The BIOS setting Jon mentioned at #5 has worked for me & I've been very busy with other things, hence my absence. If, as Jon says, there is likely to be the developer time to take this forward, I'd be happy to provide the dump information provided asked for at #9 for the kernel provided with Ubuntu 12.04, or possibly a newer kernel if required. Well, in any case we still need that info-dump to even figure out whether there's anything we can do here. Also, please check whether this is also broken when using the plain xrandr cmdline interface - "pressing the video button" has tons of other layers in between which can break things, since on linux the design is to forward these special buttons as input events and let userspace deal with things. Whereas on Windows the idea is to let the firmware do stupid things (in coordination with the intel gfx driver) without userspace being aware of it. Which is pretty much broken by design (but what can you do if you can't change your OS ...). Ping. David, please try the more recent kernels, and attach the information requested in comment #9. Hi, after a tour around some colleagues I've had my R600 returned. I should be able to supply the requested information this week. I started building a kernel from Linus' git master this morning. Created attachment 100451 [details]
dmesg output with BIOS workaround on
Created attachment 100461 [details]
intel_reg_dumper output with no VGA attached, BIOS workaround on
Created attachment 100471 [details]
xrandr --verbose output : BIOS workaround on, no VGA attached
Created attachment 100481 [details]
intel_reg_dumper output with VGA attached, BIOS workaround on
Created attachment 100491 [details]
xrandr --verbose output : BIOS workaround on, VGA attached
Created attachment 100501 [details]
dmesg output with BIOS workaround off
Created attachment 100511 [details]
intel_reg_dumper output with no VGA attached, BIOS workaround off
Created attachment 100521 [details]
xrandr --verbose output : BIOS workaround off, no VGA attached
Created attachment 100531 [details]
intel_reg_dumper output with VGA attached, BIOS workaround off
Created attachment 100541 [details]
xrandr --verbose output : BIOS workaround off, VGA attached
************************************************************
3.9.0-rc8+ (4cbbd1d55dd9375a455d12fc7e844809fbb795c0)
BIOS workaround applied
************************************************************
dmesg: dmesg-1.txt
intel_reg_dumper: intel_reg_dumper-1.txt (no VGA attached)
xrandr --verbose: xrandr-1.txt (no VGA attached)
Attach VGA (works, display wakes up)
xrandr --verbose: xrandr-2.txt (VGA attached)
intel_reg_dumper: intel_reg_dumper-2.txt (VGA attached)
************************************************************
3.9.0-rc8+ (4cbbd1d55dd9375a455d12fc7e844809fbb795c0)
BIOS workaround NOT applied
************************************************************
dmesg: dmesg-2.txt
intel_reg_dumper-3.txt (no VGA attached)
xrandr --verbose: xrandr-3.txt (no VGA attached)
Attach VGA (laptop panel reconfigures, but ext display stays
off)
xrandr --verbose: xrandr-4.txt (VGA attached)
intel_reg_dumper: intel_reg_dumper-4.txt (VGA attached)
Hi folks — is the above info any good to try and diagnose this further? Thanks! (In reply to Daniel Vetter from comment #13) > Also, please check whether this is also > broken when using the plain xrandr cmdline interface - "pressing the video > button" has tons of other layers in between which can break things, since on > linux the design is to forward these special buttons as input events and let > userspace deal with things. Hmm, I don't think we ever got a response on this bit. Can you change outputs using xrandr on the command line? Hi, On Wed, Dec 11, 2013 at 03:22:30PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > Hmm, I don't think we ever got a response on this bit. Can you change > outputs using xrandr on the command line? I am 99% sure that the external display was visible in xrandr, operations to switch/enable/disable screens completed without the xrandr tool reporting any problem, but the display did not turn on no matter what. I still have this laptop, although it's on loan to someone at the moment, I should get it back in the next week. This bug seems to have been neglected a bit, apologies. I'm afraid we don't have much clues on it either; it smells like a bios and driver cooperation issue. I can only ask you to try a recent kernel. I'd appreciate a dmesg with drm.debug=0xe from early boot, running a recent kernel (preferrably v3.17-rc or drm-intel-nightly) with: 1) bios w/a off (since IIUC there's no problem with another BIOS setting) 2) boot with vga disconnected (since IIUC there's no problem booting it connected) 3) connect vga 4) run xrandr --verbose (and attach the output too). Hi Jani, thanks; I've got my R600 set up as a testing rig now so I should be able to provide this very soon. Created attachment 154841 [details]
dmesg for a recent kernel, bios w/a off, no vga connected on boot, drm.debug
Dear Jani - please find attached as requested. This is with drm-intel-nightly, specifically b727735732d5b2.
Created attachment 154851 [details]
xrandr --verbose output ofr a recent drm-intel-next kernel, vga attached (no signal)
Dear Jani - please find attached as requested. This is with drm-intel-nightly, specifically b727735732d5b2.
Long time no updates, closing. If the problem persists with latest kernels, please file a bug at the freedesktop.org bugzilla [1], referencing this bug. Thank you. [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel |