public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86-64 sporadic hang in 2.6.23rc7 and 2.6.22
Date: Sun, 30 Sep 2007 22:57:40 +0200	[thread overview]
Message-ID: <47000DC4.4040403@aitel.hist.no> (raw)
In-Reply-To: <alpine.LFD.0.9999.0709301755080.3142@localhost.localdomain>

Thomas Gleixner wrote:
> On Sat, 29 Sep 2007, Helge Hafting wrote:
>   
>> Thomas Gleixner wrote:
>>     
>>>> I have gone back to 2.6.22rc4, which seems to work.
>>>>
>>>> This is a single opteron, although on a dual-slot board.
>>>>     
>>>>         
>>> Can you switch to serial console, so we can get some information out of
>>> that box? Sysrq-B is working, so we can get info from other sysrq
>>> functions as well.
>>>   
>>>       
>> I didn't need the serial - it crashes during console work too.
>> I think a "make clean" was in progress at the time. There must be work going
>> on in order to crash.
>>
>> This time 2.6.22rc4 died on me with a general protection fault
>>
>> I got two reports, the first one scrolled partially off screen but
>> the whole trace was there:
>>     
>
> That's why I asked for a serial console. That way we can get all the
> information from the reports including the register dumps ...
>   
Sure. But I can't get a cable right now. Was the registers necessary
in this case? Often, the trace turns out to be enough.

Helge Hafting


  reply	other threads:[~2007-09-30 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 21:08 x86-64 sporadic hang in 2.6.23rc7 and 2.6.22 Helge Hafting
2007-09-24 21:29 ` Thomas Gleixner
2007-09-29 14:09   ` Helge Hafting
2007-09-30 15:58     ` Thomas Gleixner
2007-09-30 20:57       ` Helge Hafting [this message]
2007-10-08 22:35       ` Helge Hafting
2007-09-30 21:44     ` Andi Kleen
2007-10-01  8:41       ` Helge Hafting
2007-10-05 12:11       ` Helge Hafting

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=47000DC4.4040403@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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