From: Jasper Bryant-Greene <jasper@unix.geek.nz>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-rc1 on Sun Ultra 40
Date: Thu, 14 Feb 2008 08:04:44 +1300 [thread overview]
Message-ID: <1202929484.10687.1.camel@phobos.jasper.bg> (raw)
In-Reply-To: <1202901908.11100.8.camel@phobos.jasper.bg>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
I can confirm neither the boot hang with HPET enabled nor the other
unexplained boot hang after "NET: Registered protocol family 2" occur on
2.6.24.2 on the same hardware. I still don't have an appropriate way to
debug the issue on 2.6.25-rc1, though...
-j
On Thu, 2008-02-14 at 00:25 +1300, Jasper Bryant-Greene wrote:
> I have been attempting to test 2.6.25-rc1 on my Sun Ultra 40 (two
> dual-core Opteron 2222 CPUs).
>
> There is some issue with the HPET clocksource which causes it to hang
> the boot process if enabled, which I will look into in due course (the
> HPET works fine on at least 2.6.19).
>
> More pressing is that the system will not boot at all even with HPET
> disabled - kernel gets no further than "NET: Registered protocol family
> 2".
>
> I cannot think of a way to find out what the problem is, because the
> system has only USB ports, and the USB keyboard is not working at this
> stage, either because the system has locked up hard, or because the USB
> support has not yet loaded (I tried both standard USB-HID and boot
> protocol keyboard support, both compiled in). Thus I cannot use
> magic-sysrq, or even scrollback to look at boot messages. There is also
> no serial port to assist with the latter...
>
> Any thoughts on a procedure for debugging this would be much
> appreciated.
>
> -j
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-13 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 11:25 Jasper Bryant-Greene
2008-02-13 19:04 ` Jasper Bryant-Greene [this message]
2008-02-17 22:51 ` Yinghai Lu
2008-03-28 10:17 ` Thomas Gleixner
2008-03-28 14:51 ` Yinghai Lu
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=1202929484.10687.1.camel@phobos.jasper.bg \
--to=jasper@unix.geek.nz \
--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
all inboxes | Powered by JetHome®