From: Tejun Heo <htejun@gmail.com>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: "Linux-Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.24-rc7
Date: Wed, 09 Jan 2008 10:56:02 +0900 [thread overview]
Message-ID: <478429B2.2030002@gmail.com> (raw)
In-Reply-To: <20080108015012.2e518dd4@werewolf>
J.A. Magallón wrote:
> HI all...
>
> On Sun, 6 Jan 2008 14:19:16 -0800 (PST), Linus Torvalds <torvalds@linux-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
next prev parent reply other threads:[~2008-01-09 1:56 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 22:19 Linux 2.6.24-rc7 Linus Torvalds
2008-01-06 23:52 ` Mark Lord
2008-01-07 0:08 ` Linus Torvalds
2008-01-07 0:35 ` Tejun Heo
2008-01-07 8:48 ` Linux 2.6.24-rc7 Build Failure on headers_install Kamalesh Babulal
2008-01-07 10:12 ` Sam Ravnborg
2008-01-08 10:51 ` Kamalesh Babulal
2008-01-08 13:10 ` Sam Ravnborg
2008-01-07 10:36 ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Kamalesh Babulal
2008-01-07 18:07 ` Andrew Morton
2008-01-07 18:31 ` Christoph Lameter
2008-01-07 19:38 ` Andrew Morton
2008-01-08 9:56 ` Jean Delvare
2008-01-08 10:44 ` Kamalesh Babulal
2008-01-08 12:34 ` Fix for __you_cannot_kmalloc_that_much failure with gcc 3.2 Jean Delvare
2008-01-08 4:20 ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Arjan van de Ven
2008-01-08 5:23 ` Christoph Lameter
2008-01-08 8:20 ` Kamalesh Babulal
2008-01-08 9:27 ` Balbir Singh
2008-01-08 7:48 ` Jean Delvare
2008-01-07 12:13 ` Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156! Kamalesh Babulal
2008-01-08 16:16 ` [powerpc crash] " Ingo Molnar
2008-01-07 15:53 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:27 ` smpboot_64 section mismatch warning Sam Ravnborg
2008-01-07 16:31 ` section mismatch warning in head_64.S Sam Ravnborg
2008-01-15 10:18 ` Alejandro Riveira Fernández
2008-01-07 23:27 ` smpboot_64 section mismatch warning David Howells
2008-01-08 9:14 ` Alejandro Riveira Fernández
2008-01-08 11:17 ` David Howells
2008-01-07 16:14 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:24 ` Michael Buesch
2008-01-07 16:52 ` Alejandro Riveira Fernández
2008-01-07 17:30 ` Michael Buesch
2008-01-07 20:23 ` Alejandro Riveira Fernández
2008-01-08 15:30 ` Michael Buesch
2008-01-08 15:55 ` Alejandro Riveira Fernández
2008-01-08 0:50 ` J.A. Magallón
2008-01-09 1:32 ` Avuton Olrich
2008-01-09 1:56 ` Tejun Heo [this message]
2008-01-10 9:25 ` J.A. Magallón
2008-01-10 13:10 ` Tejun Heo
2008-01-13 23:19 ` J.A. Magallón
2008-01-13 23:57 ` Tejun Heo
2008-01-14 23:38 ` J.A. Magallón
2008-01-14 23:56 ` Tejun Heo
2008-01-08 18:42 ` Linux 2.6.24-rc7: sparc64: WARNING: at kernel/lockdep_proc.c:267 lockdep_stats_show() Mariusz Kozlowski
2008-01-08 21:00 ` Randy Dunlap
2008-01-08 22:39 ` Mariusz Kozlowski
2008-01-08 22:45 ` Randy Dunlap
2008-01-09 16:31 ` Mariusz Kozlowski
2008-01-08 22:50 ` David Miller
2008-01-08 22:56 ` Ingo Molnar
2008-01-08 23:06 ` David Miller
2008-01-09 0:52 ` Ingo Molnar
2008-01-09 1:17 ` Linux 2.6.24-rc7 Willy Tarreau
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=478429B2.2030002@gmail.com \
--to=htejun@gmail.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).