From: Diego Calleja <diegocg@gmail.com>
To: nickpiggin@yahoo.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with current linus' git tree
Date: Wed, 18 Jan 2006 01:20:29 +0100 [thread overview]
Message-ID: <20060118012029.db6bf538.diegocg@gmail.com> (raw)
In-Reply-To: <20060117141725.d80a1221.diegocg@gmail.com>
El Tue, 17 Jan 2006 14:17:25 +0100,
Diego Calleja <diegocg@gmail.com> escribió:
> > Can you apply the attached patch and try to reproduce the oops?
>
> You're saying that I'll have to spend all the afternoon watching
> DVDs? Well, if the linux kernel needs it!
I've been running kaffeine for hours and i didn't triggered it, it's
hard to reproduce :/
I'll continue trying to hit it, even if it was a hardware error
it should happen again!
next prev parent reply other threads:[~2006-01-18 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 18:15 Oops with current linus' git tree Diego Calleja
2006-01-17 4:20 ` Nick Piggin
2006-01-17 4:24 ` Nick Piggin
2006-01-17 13:17 ` Diego Calleja
2006-01-18 0:20 ` Diego Calleja [this message]
2006-01-18 3:23 ` Nick Piggin
2006-01-19 19:31 ` Diego Calleja
2006-01-18 3:25 ` Nick Piggin
2006-01-18 14:02 ` Diego Calleja
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=20060118012029.db6bf538.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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