mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Shoemaker <chris.shoemaker@cox.net>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.4] Bad swap file entry, then kernel BUG at mm/shmem.c:475
Date: Sat, 3 Apr 2004 13:35:51 -0500	[thread overview]
Message-ID: <20040403183551.GA1342@cox.net> (raw)
In-Reply-To: <200404020838.09566.vda@port.imtp.ilyichevsk.odessa.ua>

On Fri, Apr 02, 2004 at 08:38:09AM +0300, Denis Vlasenko wrote:
> On Friday 02 April 2004 02:27, Chris Shoemaker wrote:
> > and I haven't found evidence of off-by-bit errors.  However, 2 days
> > running memtest86 with all tests, gave no errors.  (BTW, does anyone
> > have a suggestion of a more rigorous general hardware stress-test for
> > detecting flakiness?)  If my hardware is bad it's pretty intermittent
> 
> cpuburn.

  Thanks for the tip.  I ran burnBX, burnP5, and burnMMX overnight.  No 
problems at all.  But at least I'll know about cpuburn next time I want 
to test a CPU.

> 
> Also try to slightly underclock your hardware,
> downgrade DMA mode, etc (although it seems you use SCSI...).

  Actually, the SCSI drives aren't active.  root and swap are on a 13GB
Fujitsu IDE drive.  That got me thinking though...  it seems maybe there
is a common thread to my oopses.  I think they tend to happen during
disk i/o.  Either I'm loading a program, or closing X or even during
boot-up ( 3 times oopsed during boot now. ) -- all i/o activities.

  My disk is using udma2 mode, according to 'hdparm -I'.  I guess it's
getting set that way from the BIOS, which is set to Auto for the PIO/DMA
mode.  I'll follow your suggestion and try to force it lower in the
BIOS, but first I checked more carefully over the CONFIG options related
to IDE and found some things that maybe shouldn't have been set:

CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_IDE_TASK_IOCTL=y
CONFIG_IDE_TASKFILE_IO=y
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_OFFBOARD=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEDMA_ONLYDISK=y

	As far as I can tell, I don't really need any of those.  So, I 
disabled all of the above.  I'm running with this new config for a few 
hours now.  If it oopses, I'll try the lower dma mode.

-Chris

> 
> vda

  reply	other threads:[~2004-04-03 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 23:27 Chris Shoemaker
2004-04-02  5:38 ` Denis Vlasenko
2004-04-03 18:35   ` Chris Shoemaker [this message]
2004-04-12 20:47     ` [2.6.4] Oops in filp_close (partial SOLUTION) Chris Shoemaker

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=20040403183551.GA1342@cox.net \
    --to=chris.shoemaker@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®