LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 64-bit AMD panic
Date: Mon, 3 Mar 2008 19:45:52 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803031942040.5974@sheep.housecafe.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0803031205030.5874@chaos.analogic.com>

On Mon, 3 Mar 2008, linux-os (Dick Johnson) wrote:
> We have 64-bit production machines that use the kernel shipped with
> a RedHat distribution, linux-2.6.11-1.1369_FC4smp.

Try asking on the Fedora lists or perhaps it's even in their bugzilla...

> There have been
> no problems until we received recent hardware. With the latest hardware,
> which the vendor claims hasn't changed,

I'm not following: you changed the hardware, but the vendor said, the hard 
did not change?

> the machines panic when either
> a USB mouse or USB keyboard are plugged in.

If you're stuck to this hardware (changed or not): did you try a more 
recent kernel? 2.6.11 is pretty old for lkml....

C.

> The information transmitted in this message is confidential and may
> be privileged.  Any review, retransmission, dissemination, or other

damn, I retransmitted it :)
-- 
BOFH excuse #154:

You can tune a file system, but you can't tune a fish (from most tunefs man pages)

  reply	other threads:[~2008-03-03 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 17:06 linux-os (Dick Johnson)
2008-03-03 18:45 ` Christian Kujau [this message]
2008-03-03 21:22   ` Rik van Riel
2008-03-03 22:10     ` linux-os (Dick Johnson)
2008-03-03 22:21       ` Rik van Riel
2008-03-04  0:11       ` Jesper Juhl
2008-03-04 14:21         ` linux-os (Dick Johnson)
2008-03-06 16:41 ` Chris Snook

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=alpine.DEB.1.00.0803031942040.5974@sheep.housecafe.de \
    --to=lists@nerdbynature.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --subject='Re: 64-bit AMD panic' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).