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 12:30:07 -0400	[thread overview]
Message-ID: <4718DB8F.3070903@rtr.ca> (raw)
In-Reply-To: <2c0942db0710190858n647192d6t270e43b2a3075320@mail.gmail.com>

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).

Cheers

  reply	other threads:[~2007-10-19 16:30 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 [this message]
2007-10-19 17:18     ` Ray Lee
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=4718DB8F.3070903@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