From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Computer issues...
Date: Tue, 31 Oct 2017 17:13:02 +0200 [thread overview]
Message-ID: <20171031151302.GJ16127@mtr-leonro.local> (raw)
In-Reply-To: <36640bfe-850b-a857-1cc9-58939ac50946-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]
On Tue, Oct 31, 2017 at 10:32:03AM -0400, Doug Ledford wrote:
> My primary computer had a sudden failure yesterday. I was working, I
> turned around to grab something, and the whole thing just powered down
> while I was looking away. I tried everything to power it back up, but
> nothing worked. However, it wasn't *completely* dead because two LEDs
> on the motherboard came on, just nothing else. So, I started to pull it
> apart and do some investigation. I pulled another power supply and
> plugged just the motherboard into it, and viola, it came up. So, I guess
> the 12v rail on my other power supply died. I went to Best Buy to buy a
> new power supply (the one I tested with really wasn't big enough for
> this machine), bring it back home, and got to work replacing the entire
> power supply.
>
> I happen to always buy fully modular power supplies if I can, so I was
> in the process of swapping things out, and I didn't realize I had
> plugged a Corsair modular SATA power cable in the SATA connector on the
> new power supply and ran it to the bank of 4 SSDs I have in my main
> computer. Until I powered the new EVGA power supply and immediately
> heard some odd crackling followed by the unmistakable smell of magic
> smoke (quite strong I might add). So, moral of this story is, while the
> EVGA and Corsair modular connectors for SATA power cables use identical
> physical connectors and will happily plug in on each other's power
> supplies, how they wire them up most definitely is *not* identical, and
> all four SSDs that were plugged into that modular SATA power cable are
> now toast. This includes my primary workstation and all data that was
> on it. Fortunately, I keep backups and what not, but I am currently
> sending this email from my laptop and I will likely loose the next day
> to two days to the task of reinstalling from scratch, then restoring
> from backup (even as I write this, my laptop is writing a Fedora 27 Beta
> USB boot key). Joy!
Hi Doug,
Thank you for keeping us in the loop, as far as I can see there are no -rc
material except this one: https://patchwork.kernel.org/patch/10032391/
This patch is extremely important to forward to Linus in this cycle,
before -rc is closed, because NLDEV was added in v4.14 merge window.
Will it be OK from you side if I forward this to Linus immediately?
Thanks
>
> --
> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> GPG KeyID: B826A3330E572FDD
> Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
>
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-31 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+mK3=-v-nMb-cRO2hGEmirxbNnRuW-OZWGC8d+sUoTcxKmt7w@mail.gmail.com>
[not found] ` <1509363152.2295.5.camel@redhat.com>
[not found] ` <5b0fbfd7-6747-da76-91a9-3fa4dc173bb0@redhat.com>
[not found] ` <d6ab43f7-9698-7164-441b-02c1f5560abd@redhat.com>
[not found] ` <CAKkHt7W_Cv_qGRs_R3zn6_PaXd7xAE0+D_Qghn7KUq+bzRHHjg@mail.gmail.com>
[not found] ` <f3a0d17b-1a5c-b97c-e544-5b4524e71424@redhat.com>
[not found] ` <783cf656-3cd7-c40d-48cf-a749f022a161@redhat.com>
[not found] ` <e4fc7d4e-5295-caf9-be5b-6ac5a57a5d2d@redhat.com>
[not found] ` <e4fc7d4e-5295-caf9-be5b-6ac5a57a5d2d-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-31 14:32 ` Computer issues Doug Ledford
[not found] ` <36640bfe-850b-a857-1cc9-58939ac50946-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-31 15:13 ` Leon Romanovsky [this message]
[not found] ` <20171031151302.GJ16127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-31 17:33 ` Doug Ledford
[not found] ` <6803be08-bc2c-63fa-251c-eb73c2c74fd2-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-31 17:50 ` Leon Romanovsky
2017-10-31 17:51 ` Linus Torvalds
[not found] ` <CA+55aFyrYa83R12Ov2z1vsRx03yBNARR82Ftrpsx3BTz0MJrDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-31 18:10 ` Leon Romanovsky
2017-11-09 16:44 ` Doug Ledford
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=20171031151302.GJ16127@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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