mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gregory Davis" <gregdavis@ieee.org>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.10 thru 2.6.11-rc3 hang
Date: Sat, 12 Feb 2005 11:33:29 -0500	[thread overview]
Message-ID: <000601c51120$98b8ca00$04000100@JUPITER15> (raw)

This is probably an isolated incident, but I am having kernel hangs using
2.6.10 thru 2.6.11-rc3.  I have tried all different patchsets (mm, ck, cko),
and all produce the same behavior.  2.6.8.1 does not produce the behavior.
Basically, after a few minutes, the kernel hangs, and interrupts are
apparently not working as the keyboard leds don't respond anymore.  I
recently swapped out a cdrom for a dvdrom drive, and was able to use it fine
for a while with ck4 patched to 2.6.10.  Then I got gutsy and tried the mm
patch for 2.6.10, to start using reiser4.  That was when the kernel started
doing this hanging.  One surefire way to trigger a hang is to start a dvd
with mplayer:  the dvd reads the first few frames of any dvd, then hang;
however, hangs happen randomly otherwise.  I am running KDM as a login
manager, and X obviously when this happens, but without DRI.  I also have
tried going back to vanilla kernel, reformatting my drive to reiserfs3, and
an otherwise previous state, but the kernel still hangs.  I even unplugged
lots of stuff inside the PC to see if it was a current draw issue, but that
had no effect; besides 2.6.8.1 works (although X got really really really
slow and jerky for some reason).  I made sure all the CFLAGS were unset
before compiling, and this is with gcc-3.4.1, as have been the past umpteen
kernel builds for me.  I think I screwed up my system, or triggered some
obscure bug, but please send any ideas my way, and CC gregdavis@ieee.org as
I am not subscribed to the list.

Thanks,
Greg Davis



                 reply	other threads:[~2005-02-12 16:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000601c51120$98b8ca00$04000100@JUPITER15' \
    --to=gregdavis@ieee.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®