public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Richter <richter@rus.uni-stuttgart.de>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: No boot console/Plane B assertion value on 945GM hardware
Date: Mon, 7 Jul 2014 19:51:11 +0200	[thread overview]
Message-ID: <20140707175111.GR5821@phenom.ffwll.local> (raw)
In-Reply-To: <53BACD74.2070708@rus.uni-stuttgart.de>

On Mon, Jul 07, 2014 at 06:40:20PM +0200, Thomas Richter wrote:
> On 07.07.2014 17:04, Daniel Vetter wrote:
> >On Sat, Jun 21, 2014 at 01:57:32PM +0200, Thomas Richter wrote:
> >>Hi Daniel, dear intel experts,
> >>
> >>this a bug report for the intel i945GM integrated graphics chipset (*NOT*
> >>the 830GM this time). Since at least 3.12.0, but also with the latest
> >>intel-drm-nightly, I have no boot console on the 945GM chipset, the screen
> >>just remains blank. /var/log/messages  shows an assertion failure, see the
> >>attached kernel log for details, booted with drm.debug=0x0e.
> >>
> >>The problem appears if the kernel is booted with the vga=792 option  - note
> >>that the panel in this laptop is a 1024x768 and thus this is the native
> >>resolution. The problem does not appear with a text console.
> >>
> >>This sounds remarkably similar to the deadlock the 830GM had a while ago
> >>when booting with a graphical console, also with vga=792.
> >
> >Should be unrelated - more likely it's some fumble in the modeset
> >sequence, i945 is known to be picky in that area. Just to confirm: Latest
> >3.16-rc kernels are still broken?
> 
> At least 3.16-rc from one and a half week ago is affected, too. I'm
> currently not in reach of the machine - actually almost as far appart as
> possible.
> 
> >Can you please boot with drm.debug=0xe and grab a new dmesg with the
> >backtrace?
> 
> I'll try next week. What do you mean by "backtrace" apart from
> drm.debug=0x0e?

Just the entire dmesg up to the WARNING.

> >>As soon as X is initialized, graphics work again, I just don't have a boot
> >>console.
> >
> >So once X is running fbcon also works again, i.e. it's only the initial
> >boot console that's black?
> 
> Exactly. Once X is up, the console is fine again, too.
> 
> Greetings from Sapporo (<- which explains my unavailability),

Ok, enjoy your stay then ;-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-07-07 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 11:57 No boot console/Plane B assertion value on 945GM hardware Thomas Richter
2014-07-07 15:04 ` Daniel Vetter
2014-07-07 15:10   ` Daniel Vetter
2014-07-07 16:40   ` Thomas Richter
2014-07-07 17:51     ` Daniel Vetter [this message]
2014-07-18 19:47       ` No boot console/Plane B assertion value on 945GM hardware [FIXED!] Thomas Richter

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=20140707175111.GR5821@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=richter@rus.uni-stuttgart.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