linux-kernel - Re: PROBLEM: 2.6.23.1 Freezes on GB data transfers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2c0942db0710191018n894a773mc2b0400067c0fdf@mail.gmail.com>
Date:	Fri, 19 Oct 2007 10:18:04 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Mark Lord" <lkml@....ca>
Cc:	"Giangiacomo Mariotti" <gg.mariotti@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: 2.6.23.1 Freezes on GB data transfers

On 10/19/07, Mark Lord <lkml@....ca> wrote:
> Ray Lee wrote:
> > On 10/17/07, Giangiacomo Mariotti <gg.mariotti@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/