From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: "Dmitry D. Khlebnikov" <galaxy@openwall.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 3.2 crashes too early on HP dc7700 and HP t5000 series
Date: Thu, 19 Jan 2012 19:08:01 +0100 [thread overview]
Message-ID: <201201191908.01122.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20120110114905.GC13535@openwall.com>
On wtorek, 10 stycznia 2012 o 12:49:05 Dmitry D. Khlebnikov wrote:
> Hello,
>
> I've tried to test the recently released 3.2 version on a couple of my
> PCs (one is HP dc7700, an SFF PC running on Intel E6300, another is HP
> t5710 thin client running Transmeta's Efficeon). In both cases the
> kernel crashed during the first seconds the control was given to it by
> the bootloader.
>
> I decided to investigate, so I've compiled a version using 'make
> allnoconfig' - and it has crashed with the same symptoms: once the
> kernel gets the execution control a screen is filled up with random colour
> rubbish and after 15 seconds or so my LCD turns off into the power
> saving state. The machine looks to be locked up since it doesn't react
> on the keyboard.
>
> Well, I thought that an early printk's may help me to determine what's
> going on so I recompiled the kernel with them + a couple of other
> debugging options (like x86 bootup debugging code), but after I rebooted
> into the newly compiled kernel I got the very same lock-up.
>
> Both these PCs are running fine with 3.1.5 and I'm now downloading
> 3.1.8 (just to confirm that 3.1 series are working on this hardware).
>
> This message is just to notify the community that there is some issue
> with 3.2 on old HP hardware. I'll try to figure out what's wrong and if
> I find anything I'll post a follow-up.
>
> I'd appreciate any hints on how to debug this kind of crashes. Right
> now, I'm thinking re: adding some dirty debugging code into the kernel
> initialisation just to figure out where it crashes.
>
> Please include me into CC if you are going to reply to this message
> since I'm not subscribed to LKML.
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=42611
for your bug report, please add your address to the CC list in there, thanks!
--
Maciej Rutecki
http://www.mrutecki.pl
next prev parent reply other threads:[~2012-01-19 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 11:49 kernel 3.2 crashes too early on HP dc7700 and HP t5000 series Dmitry D. Khlebnikov
2012-01-19 18:08 ` Maciej Rutecki [this message]
2012-01-21 12:22 ` Dmitry D. Khlebnikov
2012-01-22 7:44 ` Maciej Rutecki
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=201201191908.01122.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=galaxy@openwall.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).