All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25: random stalls on certain hardware - regression?
Date: Thu, 10 Jul 2008 11:04:55 +0400	[thread overview]
Message-ID: <4875B497.7060309@msgid.tls.msk.ru> (raw)
In-Reply-To: <20080709163618.GA5462@joi>

Marcin Slusarz wrote:
> On Wed, Jul 09, 2008 at 01:56:12AM +0400, Michael Tokarev wrote:

[random complete hangs on 2.6.25 but not 2.6.24]

> Definitely try 2.6.26-rc9 (which will soon become 2.6.26, so people will

Ok, tried 2.6.26-rc9 today night - after disabling some drivers which
were not compilable and fixing some places in core code.  It does the
same thing - i.e. it locks up the same way as 2.6.25 did, and locks up
hard as before (no keyboard and network working).

> probably ask you to test patches on top of this kernel) and if it will still 
> lock up, take a look at Documentation/nmi_watchdog.txt and maybe
> Documentation/networking/netconsole.txt in kernel sources.

Aha!.  That's very useful information, let me try just that... later
today, after work hours.  Added nmi_watchdog=1 and vga=0x5032 (in a
hope to see the whole thing on the screen) to 2.6.26pre lilo line...

Thanks!

  reply	other threads:[~2008-07-10  7:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 21:56 2.6.25: random stalls on certain hardware - regression? Michael Tokarev
2008-07-09  8:32 ` Oliver Neukum
2008-07-09  9:22   ` Michael Tokarev
2008-07-09 11:37     ` Oliver Neukum
2008-07-10  7:11       ` Michael Tokarev
2008-07-09 16:36 ` Marcin Slusarz
2008-07-10  7:04   ` Michael Tokarev [this message]
2008-08-12 10:21     ` Michael Tokarev

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=4875B497.7060309@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.