From: Thomas Schwinge <thomas@codesourcery.com>
To: Borislav Petkov <bp@alien8.de>
Cc: debian-kernel@lists.debian.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD
Date: Mon, 16 Jun 2014 12:33:55 +0200 [thread overview]
Message-ID: <87ppi9ywh8.fsf@schwinge.name> (raw)
In-Reply-To: <20140616094324.GA8170@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Hi Borislav!
On Mon, 16 Jun 2014 11:43:24 +0200, Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Jun 16, 2014 at 09:13:20AM +0200, Thomas Schwinge wrote:
> > The problem "solved itself": the machine recently died of hardware
> > failure. ;-|
>
> How convenient. :-P
;-P
> What happened?
The power supply and/or mainboard didn't "wake up" after a recent power
cycle. As both these aren't standard form factors (and the
machine/architecture had some issues, as discussed, and see also
<http://news.gmane.org/find-root.php?message_id=%3C87r45fajun.fsf%40schwinge.name%3E>
for another issue), I didn't bother looking for spare parts. Want me to
ship it to you? ;-)
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2014-06-16 10:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 10:14 Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD Thomas Schwinge
2012-06-16 13:40 ` Ben Hutchings
2012-06-18 5:29 ` Thomas Schwinge
2012-06-16 18:10 ` Borislav Petkov
2012-06-18 5:28 ` Thomas Schwinge
2012-06-18 14:29 ` Borislav Petkov
2012-06-18 14:52 ` Thomas Schwinge
2012-06-18 15:51 ` Borislav Petkov
2012-09-07 9:14 ` Thomas Schwinge
2012-09-13 12:58 ` Borislav Petkov
2012-09-17 17:23 ` Borislav Petkov
2012-09-22 11:53 ` Thomas Schwinge
2014-06-16 7:13 ` Thomas Schwinge
2014-06-16 9:43 ` Borislav Petkov
2014-06-16 10:33 ` Thomas Schwinge [this message]
2014-06-16 10:46 ` Borislav Petkov
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=87ppi9ywh8.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=bp@alien8.de \
--cc=debian-kernel@lists.debian.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).