public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Bad behaviour after hdparm -M  128
Date: Mon, 11 Jun 2007 11:22:40 +0200	[thread overview]
Message-ID: <20070611092240.GC29775@dose.home.local> (raw)
In-Reply-To: <20070608015004.GA16785@khazad-dum.debian.net>

On Thu, Jun 07, 2007 at 22:50:04 -0300, Henrique de Moraes Holschuh wrote:

[...]

> I just tracked it down to hdparm.  Version 6.9 (the one in Debian stable)
> doesn't work right with libata.  Version 7.5 (the one in Debian unstable)
> works fine.
> 
> So, at least in my side, there are *no* kernel bugs.  Maybe this is also the
> case for the poster that reported the problem?

I also use Debian unstable.

Here is the relevant part of the hdparm -I output:

/dev/sda:

ATA device, with non-removable media
        Model Number:       ST98823AS                               
        Serial Number:      5PK0GTK8
        Firmware Revision:  7.01    
Standards:
        Supported: 7 6 5 4 
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  156301488
        LBA48  user addressable sectors:  156301488
        device size with M = 1024*1024:       76319 MBytes
        device size with M = 1000*1000:       80026 MBytes (80 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific
        minimum
        R/W multiple sector transfer: Max = 16  Current = ?
        Advanced power management level: unknown setting (0x8080)
        Recommended acoustic management value: 128, current value: 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5
        *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    DOWNLOAD_MICROCODE
           *    Advanced Power Management feature set
                SET_MAX security extension
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    WRITE_{DMA|MULTIPLE}_FUA_EXT
           *    IDLE_IMMEDIATE with UNLOAD
           *    SATA-I signaling speed (1.5Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
                Device-initiated interface power management
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set

Regards,
Tino

  reply	other threads:[~2007-06-11  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.DWgGSeKzniALToNSyX9W5NibA1w@ifi.uio.no>
2007-06-06 14:29 ` Bad behaviour after hdparm -M 128 Robert Hancock
2007-06-06 15:44   ` Henrique de Moraes Holschuh
2007-06-06 16:24     ` Björn Steinbrink
2007-06-06 16:48       ` Henrique de Moraes Holschuh
2007-06-06 17:51         ` Björn Steinbrink
2007-06-06 21:03           ` Henrique de Moraes Holschuh
2007-06-06 21:36             ` Björn Steinbrink
2007-06-06 21:52               ` Henrique de Moraes Holschuh
2007-06-07 15:45                 ` Mark Lord
2007-06-08  1:50                   ` Henrique de Moraes Holschuh
2007-06-11  9:22                     ` Tino Keitel [this message]
2007-06-06  6:47 Tino Keitel

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=20070611092240.GC29775@dose.home.local \
    --to=tino.keitel@gmx.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