From: Keith Packard <keithp@keithp.com>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: Pekka Enberg <penberg@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>, Robse <rob-se@live.de>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Bug #37472] Lenovo U160 (i915 black screen)
Date: Tue, 12 Jul 2011 08:47:19 -0700 [thread overview]
Message-ID: <yunei1vec1k.fsf@aiko.keithp.com> (raw)
In-Reply-To: <gioc0z6gn2.fsf@karga.hank.lab>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Tue, 12 Jul 2011 10:35:13 +0200, Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> wrote:
> I'm sorry for the noise, I did not check new comments in the bug report
> where Robse noted that the workaround works for him. I'm not sure if
> that means the bug can be closed.
A kernel commandline workaround isn't ideal; we should at least provide
a quirk that does this automatically for this hardware. Can we get the
PCI information for the graphics device on this hardware (lspci -v -n)?
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-07-12 15:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 10:54 3.0-rc6-git6: Reported regressions 2.6.38 -> 2.6.39 Rafael J. Wysocki
2011-07-10 10:54 ` [Bug #33242] Lockdep splat in autofs with 2.6.39-rc2 Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #35242] NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot) Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #35642] On resume, I sometimes get a kernel oops with led_trigger_unregister_simple Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #35662] softlockup with kernel 2.6.39 Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE Rafael J. Wysocki
2011-07-10 12:06 ` Pekka Enberg
2011-07-10 12:25 ` Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #35142] 2.6.39-rc7-git1 boot error message (no crash) Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #36392] 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #36332] Intel gpu turns external monitor off when X starts Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #35922] SND_USB_AUDIO recording device not initializing correctly Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #36182] Erroneous package power limit notification since kernel 2.6.39 Rafael J. Wysocki
2011-07-10 17:03 ` Olaf Freyer
2011-07-10 20:20 ` Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works Rafael J. Wysocki
2011-07-10 11:58 ` Pekka Enberg
2011-07-10 18:34 ` Jeff Layton
2011-07-10 20:23 ` Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37292] kernel BUG at fs/ecryptfs/read_write.c:47! Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37312] Intel 5100 wifi stopped working with 2.6.39.1 Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37042] linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37692] Linux 2.6.39.x fails to boot - unable to mount root fs Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37622] Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965 Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37322] high load, unresponsive system spinning in rcu_kthread Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37472] Lenovo U160 (i915 black screen) Rafael J. Wysocki
2011-07-10 11:56 ` Pekka Enberg
2011-07-10 20:46 ` Keith Packard
2011-07-12 8:27 ` Dirk Gouders
2011-07-12 8:35 ` Dirk Gouders
2011-07-12 15:47 ` Keith Packard [this message]
2011-07-12 16:12 ` Dirk Gouders
2011-07-10 10:58 ` [Bug #37772] Sometimes, sound disappears and doesn't want to idle Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller Rafael J. Wysocki
2011-07-11 18:35 ` Martin
2011-07-11 19:21 ` Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #37712] reboot / "shutdown -r now" hangs ; works fine on 2.6.38.7-1 Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #38132] [Warning] 2.6.39.x latencytop Rafael J. Wysocki
2011-07-10 11:53 ` Pekka Enberg
2011-07-10 12:35 ` Rafael J. Wysocki
2011-07-10 21:25 ` Steven Rostedt
2011-07-11 7:34 ` Pekka Enberg
2011-07-10 10:58 ` [Bug #38102] BUG kmalloc-2048: Poison overwritten Rafael J. Wysocki
2011-07-10 11:29 ` Alexey Zaytsev
2011-07-10 12:32 ` Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #38742] After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel Rafael J. Wysocki
2011-07-10 10:58 ` [Bug #38842] panic in elv_completed_request on safe remove usb hard drive Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2011-06-26 22:26 3.0-rc4: Reported regressions 2.6.38 -> 2.6.39 Rafael J. Wysocki
2011-06-26 22:35 ` [Bug #37472] Lenovo U160 (i915 black screen) Rafael J. Wysocki
2011-06-27 7:14 ` Dirk Gouders
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yunei1vec1k.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=chris@chris-wilson.co.uk \
--cc=florian@mickler.org \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=penberg@kernel.org \
--cc=rjw@sisk.pl \
--cc=rob-se@live.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox