public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.23.1 Freezes on GB data transfers
Date: Fri, 19 Oct 2007 13:35:49 -0400	[thread overview]
Message-ID: <4718EAF5.6000700@rtr.ca> (raw)
In-Reply-To: <2c0942db0710191018n894a773mc2b0400067c0fdf@mail.gmail.com>

Ray Lee wrote:
> On 10/19/07, Mark Lord <lkml@rtr.ca> wrote:
>
>> I believe this is now the forth report of blinking-leds lockup with 2.6.23.1.
>>
>> I wonder what's causing it?
>> My system has this as well, totally random, once every day or so.
>> New behaviour since 2.6.23-rc9 (I posted previously about this).
> 
> Boy, there's just not a lot between 2.6.23-rc9 and 2.6.23 proper.
> There are two things that kinda pop out, but this is at best a WAG.

Yeah, I looked at the changes and it's all very innocent looking.
More likely in my case, I suppose, is that the bug was there earlier
and then some timing changed somewhere and now it triggers more often.

One supporting evidence of that, is that with the powertop patches applied,
it crashes much less often.  And all that those do is adjust timings in
various places.

> First, are you on x86-32 and happen to have CONFIG_HIGHPTE set?

Core2Duo, 2GB, x86-32, CONFIG_HIGHPTE is not set.

> Second is another memory thing, where in filemap_fault we now do a
> page_cache_release where we didn't before, but that appears to only be
> in a case where we send a sigbus, so I wouldn't expect that to be
> hitting.

It seems to happen most often here on resume from suspend (RAM),
and when hotplugging hardware.  But it's infrequent enough that this
may not be a reliable clue.

Cheers

      reply	other threads:[~2007-10-19 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 11:20 PROBLEM: 2.6.23.1 Freezes on GB data transfers Giangiacomo Mariotti
2007-10-19 15:58 ` Ray Lee
2007-10-19 16:30   ` Mark Lord
2007-10-19 17:18     ` Ray Lee
2007-10-19 17:35       ` Mark Lord [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=4718EAF5.6000700@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=gg.mariotti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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