linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Stromsoe <cbs@cts.ucla.edu>
To: Willy Tarreau <willy@w.ods.org>
Cc: Roberto Nibali <ratz@drugphish.ch>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
Date: Sun, 15 Jan 2006 13:18:20 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601151313590.5053@potato.cts.ucla.edu> (raw)
In-Reply-To: <20060115121242.GA20277@w.ods.org>

On Sun, 15 Jan 2006, Willy Tarreau wrote:
> On Sun, Jan 15, 2006 at 03:29:15AM -0800, Chris Stromsoe wrote:
>>
>> I've been running stable with the propsed changes since the 10th.  The 
>> original config and the currently running config are both at 
>> <http://hashbrown.cts.ucla.edu/pub/oops-200512/>.  This is the diff:
>>
>> cbs@hashbrown:~ > diff config-2.4.32 config-2.4.32-20060115
>>
>> 65c65
>> < CONFIG_HIGHIO=y
>> ---
>> > # CONFIG_HIGHIO is not set
>
> I wonder if this change could be suspected of affecting stability. With 
> this unset, data will be sent from the card to low memory, then bounced 
> to high mem when needed. Maybe the card, northbridge or anything else 
> sometimes corrupts memory during direct highmem I/O from PCI ? :-/

I'll let it run for another week as it is. If it would be useful 
information, I can switch CONFIG_HIGHIO back to =y and let that kernel run 
for a while.  Otherwise, I'll probably switch permanently to 2.6.


-Chris

  reply	other threads:[~2006-01-15 21:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 16:58 bad pmd filemap.c, oops; 2.4.30 and 2.4.32 Chris Stromsoe
2005-12-28  0:10 ` Marcelo Tosatti
2005-12-29  2:52   ` Chris Stromsoe
2005-12-29  5:12     ` Willy Tarreau
2005-12-29  9:33       ` Chris Stromsoe
2005-12-29 10:08         ` Willy Tarreau
2005-12-29 12:01           ` Chris Stromsoe
2005-12-31  0:12     ` Chris Stromsoe
2005-12-31  1:48       ` Chris Stromsoe
2005-12-31  4:00         ` Chris Stromsoe
2005-12-31  7:25           ` Willy Tarreau
2005-12-31 11:06             ` Chris Stromsoe
2005-12-31  7:12         ` Willy Tarreau
2005-12-31 10:39           ` Chris Stromsoe
2005-12-31 10:56             ` Willy Tarreau
2005-12-31 12:08         ` Alan Cox
2005-12-31 13:01           ` Willy Tarreau
2006-01-05  3:52             ` Chris Stromsoe
2006-01-05  5:43               ` Willy Tarreau
2006-01-06 21:54                 ` Chris Stromsoe
2006-01-06 22:14                   ` Chris Stromsoe
2006-01-06 22:16                     ` Chris Stromsoe
2006-01-07  9:19                     ` Roberto Nibali
2006-01-09 18:28                       ` Chris Stromsoe
2006-01-09 20:16                         ` Roberto Nibali
2006-01-09 20:22                           ` Chris Stromsoe
2006-01-09 22:22                             ` Roberto Nibali
2006-01-10  0:59                               ` Chris Stromsoe
2006-01-15 11:29                                 ` Chris Stromsoe
2006-01-15 12:12                                   ` Willy Tarreau
2006-01-15 21:18                                     ` Chris Stromsoe [this message]
2006-01-15 22:38                                   ` Chris Stromsoe
2006-01-15 22:46                                     ` Willy TARREAU
2006-01-15 22:54                                       ` Chris Stromsoe
2006-01-16 20:52                                         ` Roberto Nibali
2006-01-16 21:32                                           ` Chris Stromsoe
2006-02-08  6:32                                         ` Chris Stromsoe
2006-02-08  6:37                                           ` Willy Tarreau
2006-01-08  9:45                   ` Willy Tarreau
2006-01-09 18:33                     ` Chris Stromsoe

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=Pine.LNX.4.64.0601151313590.5053@potato.cts.ucla.edu \
    --to=cbs@cts.ucla.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=ratz@drugphish.ch \
    --cc=willy@w.ods.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;
as well as URLs for NNTP newsgroup(s).