mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Mark Lord" <lkml@rtr.ca>
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 10:18:04 -0700	[thread overview]
Message-ID: <2c0942db0710191018n894a773mc2b0400067c0fdf@mail.gmail.com> (raw)
In-Reply-To: <4718DB8F.3070903@rtr.ca>

On 10/19/07, Mark Lord <lkml@rtr.ca> wrote:
> Ray Lee wrote:
> > On 10/17/07, Giangiacomo Mariotti <gg.mariotti@gmail.com> wrote:
> >> Linux Kernel 2.6.23.1 freezes on GB data transfers.
> >>
> >> Pc completely freezed while transferring 4Gb of data from
> >> dvd(/dev/hdc) to hd(nothing else was happening, cpu general usage at
> >> 5-6%).Except for this,it has been working flawlessly for 1 day,but
> >> when I tried to transfer 4Gb of data from the dvd to the hd,after
> >> having completed 60% of the transfer, the system became completely
> >> freezed,no keyboard,no mouse,no consoles,nothing, and the Caps Lock
> >> LED started to blink.
> >
> > The blinking Caps lock LED means that your system is Oopsing. Please
> > try your test again from a console (not from X), and see if an oops
> > message is printed out. If it is, you'll need to either copy it down
> > or take a photograph of it with a digital camera, then post the text
> > of it or post a link to the image.
>
>
> 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.

First, are you on x86-32 and happen to have CONFIG_HIGHPTE 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.

Everything else looks to be for uncommon hardware or relatively safe
(such as a few networking changes).

I'll hunt around for the other reports.

Ray

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 11:20 Giangiacomo Mariotti
2007-10-19 15:58 ` Ray Lee
2007-10-19 16:30   ` Mark Lord
2007-10-19 17:18     ` Ray Lee [this message]
2007-10-19 17:35       ` Mark Lord

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=2c0942db0710191018n894a773mc2b0400067c0fdf@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=gg.mariotti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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®