From: Lee Revell <rlrevell@joe-job.com>
To: thewade <pdman@aproximation.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64
Date: Wed, 15 Sep 2004 00:23:09 -0400 [thread overview]
Message-ID: <1095222189.2406.136.camel@krustophenia.net> (raw)
In-Reply-To: <200409150329.i8F3TtR4028133@sanctuary.aproximation.org>
On Tue, 2004-09-14 at 23:29, thewade wrote:
> Ive made no success on solving my kernel Oops/hdsploader problem. Ive
> posted a bug in the kernel bugzilla (http://bugzilla.kernel.org/show_bug.cgi?id=3388).
>
> Is there any value to using an earlier kernel release (like 2.6.4 which
> works on my other pIII laptop)?
>
Absolutely. If it works with a previous kernel, we can narrow down the
search to the things that changed between those releases.
> I imagine that an earlier release would have the same x86-64 bug though,
> right?
>
Only one way to find out...
> Is there eom way to dtermine if it was a kernel problem or a hdsploader
> problem?
>
Anytime you get an Oops it is by definition a kernel problem.
> Should I post a bug in the alsa bugtracker?
>
Yes. People are not blowing you off, it's just that there aren't many
ALSA developers, and even fewer that have the same hardware. I am sure
you will get a response soon.
Lee
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
next prev parent reply other threads:[~2004-09-15 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 3:29 hdsploader causes Ooops in kernel 2.6.8.1 and AMD64 thewade
2004-09-15 4:23 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 15:25 thewade
2004-09-11 3:19 thewade
2004-09-11 1:51 thewade
2004-09-11 2:32 ` Lee Revell
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=1095222189.2406.136.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pdman@aproximation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.