All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 14583] SSD system stall, HSM Violation
Date: Mon, 14 Dec 2009 20:10:00 GMT	[thread overview]
Message-ID: <200912142010.nBEKA0fv005256@demeter.kernel.org> (raw)
In-Reply-To: <bug-14583-11633@http.bugzilla.kernel.org/>

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


David Zeuthen <zeuthen@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zeuthen@gmail.com




--- Comment #34 from David Zeuthen <zeuthen@gmail.com>  2009-12-14 20:09:58 ---
(In reply to comment #33)
> I've been tracking a bug we've linked to this on Ubuntu, the most recent
> replies received from affected users do indicate that it's the
> devkit-disks-probe-ata-smart command that triggers the HSM Violations and death
> of their SSD.

This program is a user of libatasmart. You want to look at

 http://git.0pointer.de/?p=libatasmart.git;a=summary

Here's the libatasmart bug tracker

 http://bugs.freedesktop.org/enter_bug.cgi?product=libatasmart

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-12-14 20:10 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  6:24 [Bug 14583] New: SSD system stall, HSM Violation bugzilla-daemon
2009-11-11  6:24 ` [Bug 14583] " bugzilla-daemon
2009-11-11  6:25 ` bugzilla-daemon
2009-11-11  6:26 ` bugzilla-daemon
2009-11-11  6:27 ` bugzilla-daemon
2009-11-11  6:28 ` bugzilla-daemon
2009-11-11  8:59 ` bugzilla-daemon
2009-11-12  4:46 ` bugzilla-daemon
2009-11-12  4:47 ` bugzilla-daemon
2009-11-12  4:59 ` bugzilla-daemon
2009-11-12  5:03 ` bugzilla-daemon
2009-11-12 20:11 ` bugzilla-daemon
2009-11-13  5:58 ` bugzilla-daemon
2009-11-13  5:59 ` bugzilla-daemon
2009-11-18  5:24 ` bugzilla-daemon
2009-11-18  6:49 ` bugzilla-daemon
2009-11-18  7:59 ` bugzilla-daemon
2009-11-25 10:28 ` bugzilla-daemon
2009-11-25 10:57 ` bugzilla-daemon
2009-11-25 10:59 ` bugzilla-daemon
2009-11-26  4:23 ` bugzilla-daemon
2009-11-26  4:33 ` bugzilla-daemon
2009-12-06 23:18 ` bugzilla-daemon
2009-12-06 23:18 ` bugzilla-daemon
2009-12-08  6:27 ` bugzilla-daemon
2009-12-09  2:40 ` bugzilla-daemon
2009-12-09  6:29 ` bugzilla-daemon
2009-12-10  0:50 ` bugzilla-daemon
2009-12-10  6:05 ` bugzilla-daemon
2009-12-10 14:38 ` bugzilla-daemon
2009-12-10 14:44 ` bugzilla-daemon
2009-12-10 23:55 ` bugzilla-daemon
2009-12-14 16:51 ` bugzilla-daemon
2009-12-14 18:38 ` bugzilla-daemon
2009-12-14 20:10 ` bugzilla-daemon [this message]
2009-12-15  0:32   ` Bartlomiej Zolnierkiewicz
2009-12-15  0:34 ` bugzilla-daemon
2009-12-15  0:58 ` bugzilla-daemon
2009-12-15 14:37   ` Bartlomiej Zolnierkiewicz
2009-12-15 11:27 ` bugzilla-daemon
2009-12-15 14:39 ` bugzilla-daemon
2009-12-16 15:06 ` bugzilla-daemon
2009-12-18  8:22 ` bugzilla-daemon
2009-12-18  8:24 ` bugzilla-daemon
2009-12-18  8:45 ` bugzilla-daemon
2009-12-18  9:28 ` bugzilla-daemon
2009-12-18  9:42 ` bugzilla-daemon
2010-02-03  6:29 ` bugzilla-daemon

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=200912142010.nBEKA0fv005256@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.