linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: uwe.koziolek@gmx.net, Jeff Garzik <jgarzik@pobox.com>
Cc: Alexey Fisher <bug-track@fisher-privat.net>,
	Andrew Morton <akpm@osdl.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: regarding sata_sis kernel freeze when BIOS is not updated to support LBA48
Date: Fri, 20 Oct 2006 17:36:23 +0900	[thread overview]
Message-ID: <45388A87.1010304@gmail.com> (raw)

Hello, Uwe Koziolek, Jeff.

Alexey Fisher has filed bug #7314 and resolved it by himself.  :-)

http://bugzilla.kernel.org/show_bug.cgi?id=7314

The problem seems that the BIOS isn't updated to support LBA48 but 
libata doesn't know about it and issue LBA48 commands anyway.  I suppose 
there's a way to detect this mechanism.  We can either force LBA28 mode 
or at least print warning message urging the user to upgrade BIOS if 
such condition is detected.

Any ideas on how to detect this?

Thanks.

-- 
tejun

                 reply	other threads:[~2006-10-20  8:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45388A87.1010304@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bug-track@fisher-privat.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=uwe.koziolek@gmx.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).