On 7/17/06, Roman Zippel <zippel@xxxxxxxxxxxxxx> wrote:
> 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 22.214.171.124 (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?
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.