From: Jordan Neumeyer <jnengland77@gmail.com>
To: linux-ide@vger.kernel.org
Subject: pata_sis:sg_write errors
Date: Mon, 15 Jan 2007 19:05:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20070115T195130-154@post.gmane.org> (raw)
Well recently I've been using libata since my my distribution offered it when
they switched to 2.6.19( maybe? 18) in the initramfs image. I have a sis 5513
controller, which after a couple of days started acting up and coming up with
the following error:
sg_write: data in/out 30576/30576 bytes for SCSI command 0xbe--guessing data i$;
program grip not setting count and/or reply_len properly
printk: 319 messages suppressed.
sg_write: data in/out 30576/30576 bytes for SCSI command 0xbe--guessing data $n;
program grip not setting count and/or reply_len properly
printk: 321 messages suppressed.
sg_write: data in/out 16464/16464 bytes for SCSI command 0xbe--guessing data $n;
program grip not setting count and/or reply_len properly
printk: 323 messages suppressed.
sg_write: data in/out 16464/16464 bytes for SCSI command 0xbe--guessing data $n;
program grip not setting count and/or reply_len properly
printk: 323 messages suppressed.
sg_write: data in/out 16464/16464 bytes for SCSI command 0xbe--guessing data $n;
program grip not setting count and/or reply_len properly
printk: 324 messages suppressed.
It's repeated over, and over; differing amounts of bytes. I'm unsure what
invoked such errors, because it only started to happen a few days after use of
the kernel. Which was 2.6.19-beyond kernel. I don't believe any additions made
by the beyond kernel affected the libata system.
Has this been fixed in the 2.6.20-rcXs?
~Jordan Neumeyer
next reply other threads:[~2007-01-15 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 19:05 Jordan Neumeyer [this message]
2007-01-16 1:54 ` pata_sis:sg_write errors Tejun Heo
2007-01-16 23:04 ` jnengland77
2007-01-17 2:14 ` Tejun Heo
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=loom.20070115T195130-154@post.gmane.org \
--to=jnengland77@gmail.com \
--cc=linux-ide@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).