All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Madru <jdm64@gawab.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Mon, 24 Mar 2008 20:07:12 -0700	[thread overview]
Message-ID: <47E86C60.5040706@gawab.com> (raw)
In-Reply-To: <200803191648.59400.jbarnes@virtuousgeek.org>

Jesse Barnes wrote:
> Good luck with the upgrade...

Well, the upgrade went ok, and compiling the reg_dumper using the libpciaccess .deb from Bryce worked.
Then I tried to add to the boot scripts a call to reg_dumper...
...To make a long story short...
I somehow killed my boot scripts! Anyways, I did a fresh reinstall of Ubuntu 8.4 Beta.

I'm still getting the blank screen problem with the 2.6.25-rc6 kernel,
so I guess it wasn't a Ubuntu software problem (or I hope not, because that could be really hard to find).

What I did was created a script that took a reg_dump every 6 secs for 1 min.
I made that as rc2.d/S01regdump so it should've been the very first thing called.
So, I hope there's enough "data points" to see what's happening.

Reg Dump Information
	http://jdserver.homelinux.org/linux/reg_dump.tar.bz2
Detailed System Information
	http://jdserver.homelinux.org/linux/sysinfo-2.6.25-rc6
Kernel Config
	http://jdserver.homelinux.org/linux/config-2.6.25-rc6

Hope that can help find the problem. If you need me to test anything else I'll try.

Justin


  parent reply	other threads:[~2008-03-25  3:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:02 [Regression: 2.6.25-rc5: Blank Screen: Intel 945] Justin Madru
2008-03-12 19:36 ` Jesse Barnes
     [not found]   ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09     ` Jesse Barnes
2008-03-14  4:22       ` Justin Madru
2008-03-14 17:29         ` Jesse Barnes
2008-03-15  3:48           ` Justin Madru
2008-03-15 17:35             ` Jesse Barnes
2008-03-15 18:16               ` Bryce Harrington
2008-03-17  1:28               ` Justin Madru
2008-03-18 19:07                 ` Bryce Harrington
2008-03-18 20:00                   ` Jesse Barnes
2008-03-18 20:53                     ` Bryce Harrington
2008-03-18 21:14                     ` Bryce Harrington
2008-03-18 21:17                       ` Jesse Barnes
2008-03-19 23:38                         ` Justin Madru
2008-03-19 23:48                           ` Jesse Barnes
2008-03-20  2:00                             ` Bryce Harrington
2008-03-25  3:07                             ` Justin Madru [this message]
2008-03-25 20:08                               ` Jesse Barnes
2008-03-25 20:08                                 ` Jesse Barnes
2008-03-26 18:32                                 ` Justin Madru
2008-03-31 19:24                                 ` Justin Madru
2008-04-01 20:22                                   ` Jesse Barnes
2008-04-01 20:22                                     ` Jesse Barnes
2008-04-09  4:56                                     ` Justin Madru
2008-04-09 15:24                                       ` Jesse Barnes
2008-04-14  3:46                                         ` Justin Madru

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=47E86C60.5040706@gawab.com \
    --to=jdm64@gawab.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.