public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean E. Russell" <ser@germane-software.com>
To: Mark Nipper <nipsy@bitgnome.net>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.1[01] freeze on x86_64
Date: Tue, 17 May 2005 07:37:25 -0400	[thread overview]
Message-ID: <200505170737.26227.ser@germane-software.com> (raw)
In-Reply-To: <20050322131116.GA15512@king.bitgnome.net>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

On Tuesday 22 March 2005 08:11, Mark Nipper wrote:
> 	I've actually got old dumb terminals sitting around.
> I'll hook one up and set the oops=panic option also.  Maybe we
> can nail this down as I've pretty much avoided using my x86-64
> desktop ever since.  I'd been torn trying to decide whether or
> not to migrate to a different file system.

Hah!

I haven't seen Mark post any follow-ups to this, but I have some more 
information of my own.

Mark, are you running the IPW2200 drivers, by any chance?  I'm pretty sure 
that's what is causing the lock-ups on my end; that, or something in the the 
kernel's wireless handlers.

I did hook up an ethernet cable and started doing netconsole traces... only 
then the problem disappeared!  To make a long story short, the system is 
entirely stable when running network over ethernet, but when I use the 
wireless network interface, it eventually locks up.  There are no error 
messages that I can associate with the wireless device or network traffic.

-- 
--- SER

"As democracy is perfected, the office of president represents, 
more and more closely, the inner soul of the people.  On some 
great and glorious day the plain folks of the land will reach 
their heart's desire at last and the White House will be adorned 
by a downright moron."        -  H.L. Mencken (1880 - 1956)

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2005-05-17 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 22:57 2.6.1[01] freeze on x86_64 Sean Russell
2005-03-22  9:02 ` Andi Kleen
2005-03-22  7:02   ` Sean Russell
2005-03-22 12:20     ` Jan Engelhardt
2005-03-22  8:15       ` Sean Russell
2005-03-22 13:11       ` Mark Nipper
2005-05-17 11:37         ` Sean E. Russell [this message]
2005-05-17 11:55           ` Andi Kleen

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=200505170737.26227.ser@germane-software.com \
    --to=ser@germane-software.com \
    --cc=ak@muc.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nipsy@bitgnome.net \
    /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