linux-kernel - Re: Linux 2.6.24-rc7

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: <478429B2.2030002@gmail.com>
Date:	Wed, 09 Jan 2008 10:56:02 +0900
From:	Tejun Heo <htejun@...il.com>
To:	"J.A. Magallón" <jamagallon@....com>
CC:	"Linux-Kernel, " <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.24-rc7

J.A. Magallón wrote:
> HI all...
> 
> On Sun, 6 Jan 2008 14:19:16 -0800 (PST), Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
>> It's been two weeks since rc6, but let's face it, with xmas and new years 
>> (and birthdays) in between, there hasn't actually been a lot of working 
>> days, and the incremental patch from -rc6 is about half the size of the 
>> one from rc5->rc6.
>>
>> And I'll be charitable and claim it's because it's all stabilizing, and 
>> not because we've all been in a drunken stupor over the holidays.
>>
>> The shortlog (appended below) is short and fairly informative. It's all 
>> really just a lot of rather small changes. The diffstat shows a lot of 
>> one- and two-liners, with just a few drivers (and the Cell platform) 
>> getting a bit more attention, and the SLUB support of /proc/slabinfo 
>> showing up as a blip.
>>
> 
> With this kernel I'm getting frequent temporary freezes (system comes
> back responsive after a minute or so...). I see this in dmesg:
> 
> ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata3.00: cmd ca/00:08:67:10:18/00:00:00:00:00/e2 tag 0 dma 4096 out
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: status: { DRDY }
> ata3: soft resetting link
> ata3.00: configured for UDMA/133
> ata3: EH complete
> sd 2:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB)
> sd 2:0:0:0: [sdb] Write Protect is off
> sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> 
> ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata4.00: cmd c8/00:08:ef:0b:c7/00:00:00:00:00/e7 tag 0 dma 4096 in
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4.00: status: { DRDY }
> ata4: soft resetting link
> ata4.00: configured for UDMA/133
> ata4: EH complete
> sd 3:0:0:0: [sdc] 625142448 512-byte hardware sectors (320073 MB)
> sd 3:0:0:0: [sdc] Write Protect is off
> sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> 
> See this are two different drives, I doubt both drives have gone nuts
> at the same time...

That's weird.  There hasn't been any related changes.  Does going back
to 2.6.24-rc6 fix the problem?

-- 
tejun
--
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/