From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Random SATA errors with SMP on a dual core machine.
Date: Thu, 4 Jun 2009 13:54:07 -0400 [thread overview]
Message-ID: <5be49f1c318c4347b6e506f30bf0ecd8@quanstro.net> (raw)
In-Reply-To: <aa7e41150906040903u7fae9fb3t3a6907b7c165a3dc@mail.gmail.com>
> correctly copied in pc/sdscsi.c (and /sys/include/fis.h). Btw: these
> drivers seem much more complete and robust than those in the
> distribution
thank you. my hope is that it will be included in the distribution.
i'm not sure if i've recapped this on the list or not. there are a
couple of main goals of the sd/libfis work:
- support for raw ata commands allowing, e.g., smart, atazz.
- generic lba/nblocks <-> sata fis / sas frame translation.
- support for 64-bit (scsi) or 48-bit (ata) lbas in all sd drivers.
- support for combined-mode sata/sas hardware; e.g. sdorion.
- cleanup; e.g. removing the translation from lba/nblocks ->
scsi cdb -> lba/nblocks for non-scsi devices.
other small things have been done as well like conformance
with acs-2 (the latest ata command set proposal) and updating
to ahci 1.3 and 3d generation/6gbps sata.
> Things seem to be working okay, except for some leaked blocks (which
> may have been due to an unclean shutdown), so perhaps it was a fluke.
> Regardless, I'll see about getting you those boot messages.
it occurred to me that i have also also seen some funnies when
"legacy usb" is enabled in bios with a usb keyboard or mouse.
this feature enables smm (system mgmt mode) and can cause
interrupt problems.
- erik
next prev parent reply other threads:[~2009-06-04 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 20:22 Dan Cross
2009-06-02 21:01 ` Steve Simon
2009-06-03 5:15 ` erik quanstrom
2009-06-04 16:03 ` Dan Cross
2009-06-04 17:54 ` erik quanstrom [this message]
2009-06-04 19:33 ` Venkatesh Srinivas
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=5be49f1c318c4347b6e506f30bf0ecd8@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).