From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac12
Date: Tue, 8 Feb 2005 10:43:58 +0100 [thread overview]
Message-ID: <20050208094358.GA1831@sommrey.de> (raw)
On Sun, Feb 06, 2005 at 04:02:42PM +0000, Alan Cox wrote:
>Arjan van de Ven is now building RPMS of the kernel and those can be found
>in the RPM subdirectory and should be yum-able. Expect the RPMS to lag the
>diff a little as the RPM builds and tests do take time.
>Nothing terribly exciting here security wise but various bugs for problems
>people have been hitting that are now fixed upstream, and also the ULi
>tulip variant should now work. If you are running IPv6 you may well want
>the networking fixes.
Something broke my box after 2.6.10-ac8. Both -ac11 and -ac12 cause
problems when backing up sata/md-raid/dm-snapshots/reiserfs to a SCSI
tape drive. (Works fine when writing to /dev/null :-)
Backup started 1:30 a.m., errors messges start with:
Feb 8 01:34:07 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }Feb 8 01:34:07 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Feb 8 01:34:07 bear kernel: FMK Current sdc: sense = 70 99
Feb 8 01:34:07 bear kernel: ASC=26 ASCQ=c0
Feb 8 01:34:07 bear kernel: end_request: I/O error, dev sdc, sector 52294166
Feb 8 01:34:07 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }Feb 8 01:34:07 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Feb 8 01:34:07 bear kernel: FMK Current sdc: sense = 70 99
Feb 8 01:34:07 bear kernel: ASC=26 ASCQ=c0
Feb 8 01:34:07 bear kernel: end_request: I/O error, dev sdc, sector 52294174
Feb 8 01:34:07 bear kernel: raid1: Disk failure on sdc2, disabling device.
Feb 8 01:34:07 bear kernel: ^IOperation continuing on 1 devices
Feb 8 01:34:07 bear kernel: raid1: sdc2: rescheduling sector 12099536
Feb 8 01:34:07 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }Feb 8 01:34:07 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Feb 8 01:34:07 bear kernel: FMK Current sdc: sense = 70 99
Feb 8 01:34:07 bear kernel: ASC=26 ASCQ=c0
Feb 8 01:34:07 bear kernel: end_request: I/O error, dev sdc, sector 52294182
Feb 8 01:34:07 bear kernel: raid1: sdc2: rescheduling sector 12099552
etc. until hard reboot via sysrq-b
I found only one patch that seems to be related:
>2.6.10-ac11
>* Fix oops with md over dm (Jens Axboe)
Can this by any chance cause my problems?
-jo
--
-rw-r--r-- 1 jo users 63 2005-02-08 01:47 /home/jo/.signature
next reply other threads:[~2005-02-08 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 9:43 Joerg Sommrey [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-06 16:02 Linux 2.6.10-ac12 Alan Cox
2005-02-06 17:50 ` Al Viro
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=20050208094358.GA1831@sommrey.de \
--to=jo@sommrey.de \
--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