From: Willy Tarreau <w@1wt.eu>
To: Roland Kletzing <devzero@web.de>
Cc: linux-kernel@vger.kernel.org, ext-adrian.hunter@nokia.com
Subject: Re: mtd_stresstest module bricked my dockstar
Date: Mon, 24 Oct 2011 07:57:05 +0200 [thread overview]
Message-ID: <20111024055705.GA4020@1wt.eu> (raw)
In-Reply-To: <69501156.1798237.1319395066798.JavaMail.fmail@mwmweb003>
Hello Roland,
On Sun, Oct 23, 2011 at 08:37:46PM +0200, Roland Kletzing wrote:
> It may be that it`s not recommended or considered "best practise" to load all sorts of unkown modules (i.e. find /lib/modules.... -name "*.ko"....) - but people do (see https://bugzilla.novell.com/show_bug.cgi?id=224522[https://bugzilla.novell.com/show_bug.cgi?id=224522] ). And it`s not obvious that it`s THAT dangerous. And for me this is the first time Linux REALLY managed to badly brick my hardware in such a rigorous way. Maybe someone can understand that i`m not really amused, as there is no easy way to recover, as seen on http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/[http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/]
If you can't restore it with JTAG, it means the hardware is really dead.
JTAG is used when you blank the flash, and is supposed to work. I don't
know what the module does, but I fail to see how to could wear the flash
that fast. At worst it could have wiped it, or the flash was already bad.
I got one Iomega Iconnect with a faulty flash that I got replaced for a
good one, so it's more likely the case here.
> Luckily, i got that dockstar for cheap and have some more, so let`s call that "shit really happens".
>
> I don`t want to accuse anybody, that module has it`s purpose, but please consider adding more safeguard against such issues.
I agree with you. I remember the very old ISA NE2000 driver who used to
scan various addresses to find a NIC, causing some of them to reconfigure
their address to *none* and definitely stop responding on the bus to any
reconfiguration request. That was pretty annoying too. After killing a
few, I stopped using Linux on a machine with such a NIC for a long time!
> ps:
> Someone want the Dockstar for spending the hours and the money for debrick ? Or for extracting gold and other precious metals from electronic waste ? ;)
You should keep it and retry the JTAG adapter. You just need a boot loader
so if you manage to find a usable memory location that you can select by
soldering two pins together, you could manage to store it and bood from
another device.
Willy
next prev parent reply other threads:[~2011-10-24 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 18:37 mtd_stresstest module bricked my dockstar Roland Kletzing
2011-10-24 5:57 ` Willy Tarreau [this message]
2011-10-24 19:32 ` [BUG] " Roland Kletzing
2011-10-24 19:53 ` Wolfram Sang
2011-10-24 21:04 ` Artem Bityutskiy
2011-10-24 21:24 ` Wolfram Sang
2011-10-24 22:16 ` Artem Bityutskiy
2011-10-24 20:09 ` Willy Tarreau
2011-10-24 21:08 ` Artem Bityutskiy
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=20111024055705.GA4020@1wt.eu \
--to=w@1wt.eu \
--cc=devzero@web.de \
--cc=ext-adrian.hunter@nokia.com \
--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;
as well as URLs for NNTP newsgroup(s).