Re: Re: i686 hang on boot in userspace

[gmu 2k6]

On 7/17/06, gmu 2k6 <gmu2006@xxxxxxxxx> wrote:
> On 7/17/06, Roman Zippel <zippel@xxxxxxxxxxxxxx> wrote:
> > Hi,
> >
> > On Mon, 17 Jul 2006, gmu 2k6 wrote:
> >
> > > I was preparing a post to lkml about a similar hang which happens
> > > during init. I also saw an error while ntpdate tried to set the
> > > time/get the time. this only happens after I've enabled the NX bit on
> > > the dual 32bit Xeons installed in the HP Proliant Server. it works
> > > flawlessly with 2.6.17.6 (CONFIG_X86_PAE and CONFIG_HIGHMEM_64) but
> > > since 2.6.18-rc2-git4 (including 2.6.18-rc2) it hangs late in the init
> > > process.
> > >
> > > could this be related?
> >
> > Well, it could, but without further information it's impossible to say.
> > What error did you see with ntpdate? Could you post the kernel messages
> > and also insert a few stack traces as mentioned earlier?
> > Thanks.
>
> ok, the error printed from ntpdate has to do with networking:
> Running ntpdate to synchronize clockError : Temporary failure in name resolution
>
> it then stops after printing the following tg3 initialization line:
> tg3: eth0 Flow control is on for TX and on for RX.
>
> right now I'm trying to get SysRq working (my first try with it) so
> that I see where it's hanging.

either I'm too dumb or there is an undocumented way to enable SysRq on
bootup or the machine is really hanging hard. I'm not able use
Alt+Print as nothing happens besides console showing the typed in
characters ^[t.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/