From: Michael Buesch <mb@bu3sch.de>
To: steve szmidt <steve@szmidt.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Potential kernel lockup
Date: Fri, 21 Apr 2006 14:12:48 +0200 [thread overview]
Message-ID: <200604211412.49153.mb@bu3sch.de> (raw)
In-Reply-To: <200604210749.06295.steve@szmidt.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Friday 21 April 2006 13:49, you wrote:
> Hi,
>
> I thought it might be of value to know that I got what looks like a kernel
> lockup that instantly froze the system (incl mouse) and any network access,
> requiring a hard reset to recover.
>
> Using 2.6.16-1.2096_FC5, AMD 2700+ and KDE (all updated as of 4/20) 1.5G RAM
> and nVidia 4200 with binary only nVidia driver under Xinerama.
>
> Since the kernel really should not be able to be crashed like this someone
> here might be interested in tracking it, if nothing else to build up a number
> of common denominators.
>
> If this is of value I can be contacted off list for all the details.
Please contact the nvidia support.
--
Greetings Michael.
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-04-21 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 11:49 Potential kernel lockup steve szmidt
2006-04-21 12:12 ` Michael Buesch [this message]
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=200604211412.49153.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@szmidt.org \
/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