From: Jarek Poplawski <jarkao2@o2.pl>
To: David Johnson <dj@david-web.co.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hardware bug or kernel bug?
Date: Fri, 13 Oct 2006 12:58:07 +0200 [thread overview]
Message-ID: <20061013105807.GB1690@ff.dom.local> (raw)
In-Reply-To: <200610131020.48232.dj@david-web.co.uk>
On Fri, Oct 13, 2006 at 10:20:48AM +0100, David Johnson wrote:
> On Friday 13 October 2006 09:56, Jarek Poplawski wrote:
> >
> > I'd try with this:
> > - minimal workable config with a lot of debugging turned on (e.g. no:
> > smp, floppy, parport, mouse, ipv6, video, clock modulation, apm, acpi
> > buttons, thermal etc. - only base acpi or no if possible),
> > - 2.4 kernel,
> > - other distro e.g. live-cd knoppix,
> > - other transfer method like ftp (all superfluous services turned off).
> >
>
> I'll give that a go and I guess I should also see whether I can reproduce it
> under Windows too...
Sure! After all we shouldn't be system nazis and let others do
some secondary jobs...
Regards,
Jarek P.
PS: I hope you tested it also under internal stress (heavy
copying plus computing).
next prev parent reply other threads:[~2006-10-13 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:53 Hardware bug or kernel bug? David Johnson
2006-10-12 17:20 ` Arjan van de Ven
2006-10-12 19:13 ` Linus Torvalds
2006-10-13 9:20 ` David Johnson
2006-10-13 8:56 ` Jarek Poplawski
2006-10-13 9:20 ` David Johnson
2006-10-13 10:58 ` Jarek Poplawski [this message]
2006-10-13 11:56 ` David Johnson
2006-10-13 13:06 ` Jarek Poplawski
2006-10-13 16:24 ` David Johnson
2006-10-13 17:11 ` Alan Cox
2006-10-16 10:25 ` Jarek Poplawski
2006-10-16 14:32 ` David Johnson
2006-10-17 7:10 ` Jarek Poplawski
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=20061013105807.GB1690@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=dj@david-web.co.uk \
--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