From: Adrian Bunk <bunk@stusta.de>
To: Erik Slagter <erik@slagter.name>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: OOPS 2.6.16 and 2.6.16-git14
Date: Fri, 31 Mar 2006 15:18:24 +0200 [thread overview]
Message-ID: <20060331131824.GD3893@stusta.de> (raw)
In-Reply-To: <1143810088.15258.1.camel@localhost.localdomain>
On Fri, Mar 31, 2006 at 03:01:28PM +0200, Erik Slagter wrote:
>...
> As I have a laptop without serial ports, I'd have to write down the
> oops, so please forgive that I didn't write down ALL the output, I think
> I have the most important stuff, though.
>...
Nowadays, the common solution for this problem is to capture the output
using a digital camera and posting an URL to the picture (or to submit
this bug at http://bugzilla.kernel.org/ which is anyways a good idea
for issues that might be ACPI related and attach the picture there).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-03-31 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 13:01 OOPS 2.6.16 and 2.6.16-git14 Erik Slagter
2006-03-31 13:18 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-01 10:04 Erik Slagter
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=20060331131824.GD3893@stusta.de \
--to=bunk@stusta.de \
--cc=erik@slagter.name \
--cc=linux-acpi@vger.kernel.org \
--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