mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Hughes <mhughes@mhughes.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1 hangs silently in under an hour
Date: 15 Jul 2003 19:56:05 -0700	[thread overview]
Message-ID: <1058324165.27867.16.camel@mhughes.dhs.org> (raw)
In-Reply-To: <1057119402.23657.16.camel@mhughes.dhs.org>

I've got a desktop machine which is hanging regularly with 
recent 2.5 and now 2.6.0-test1 releases. It seems very solid 
running 2.4.20 ...

The machine functions as a normal desktop (email, X, web browser,
etc) and as an NFS server for music served to a machine attached to 
the stereo (so light but consistent disk and network activity).

The symptom is simply a totally hung system - no response to keyboard, 
mouse, network pings, ctrl-alt-del, or magic sysrq. There is no output
to /var/log/messages that survives a reboot. I've compiled the kernel
with all the kernel debugging options set to true with no difference in
behavior:
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_PAGEALLOC=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

Some general info - 
Distribution: Red Hat 8.0
Hardware Environment: Athlon XP1900
Software Environment: gcc 3.2
The motherboard is an Asus A7V266-E. 

I'd be happy to run test patches, change config options, etc if that
would help ... also, if there's anything else I should be doing to 
track this down before reporting, please let me know or point me 
to a document.

I'm not a subscriber to lkml, so please CC me on any replies.
						Thanks!
						Matt Hughes
					mhughes@mhughes.dhs.org


      reply	other threads:[~2003-07-16  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  4:16 Advice on hangs in 2.5.73-bk6? Matthew Hughes
2003-07-16  2:56 ` Matthew Hughes [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=1058324165.27867.16.camel@mhughes.dhs.org \
    --to=mhughes@mhughes.dhs.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®