From: Lou Langholtz <ldl@aros.net>
To: Udo Hoerhold <maillists@goodontoast.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hard lockups with 2.5.75
Date: Sat, 12 Jul 2003 12:43:00 -0600 [thread overview]
Message-ID: <3F1056B4.30208@aros.net> (raw)
In-Reply-To: <200307121425.29939.maillists@goodontoast.com>
Udo Hoerhold wrote:
>I switched from 2.5.73 to 2.5.75 yesterday, and I've encountered three hard
>lockups in the 24 hours I've been running the new kernel. When I reset the
>machine, I don't see anything unusual in the logs.
>
>The machine is a dual PIII with aic7899 SCSI and 3c905c network on the
>motherboard. In all three cases where I locked up, there was network and
>disk IO going on. I don't really have any more info.
>
>If anyone would like to give me a list of things to try, I'd be happy to do
>some testing.
>
Do you already have all the kernel hacking options turned on?
Particularly the CONFIG_DEBUG_* options? If not, rebuilding and getting
the same lockup may provide some additional info. You may also want to
try with the PREEMPT option turned on (if not aleady).
prev parent reply other threads:[~2003-07-12 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 18:25 hard lockups with 2.5.75 Udo Hoerhold
2003-07-12 18:43 ` Lou Langholtz [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=3F1056B4.30208@aros.net \
--to=ldl@aros.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maillists@goodontoast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox