From: Brian Gerst <bgerst@didntduck.org>
To: Alejandro Conty <zz01f074@etsiig.uniovi.es>
Cc: Gergely Tamas <dice@mfa.kfki.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] again: Re: Athlon kernel crash (i686 works)
Date: Tue, 09 Oct 2001 10:19:01 -0400 [thread overview]
Message-ID: <3BC30755.30F47321@didntduck.org> (raw)
In-Reply-To: <LAW2-OE29ilTmbtQVi0000079ef@hotmail.com> <Pine.LNX.4.33.0110091347001.12835-100000@falka.mfa.kfki.hu> <20011009155907.6c9e0b98.zz01f074@etsiig.uniovi.es>
Alejandro Conty wrote:
>
> Could my random kernel oopses be caused by that bug?
>
> I have a VIA (ASUS A7V) cipset an K7 1000Mhz, and sometimes the kernel crash.
> I just updated to kernel 2.4.10, and the first problem is that I get a random
> oops if I try to load analog.o with modprobe. I sent a report of this problem
> two days ago.
>
> Could that patch solve my problem?
The oops with the analog joystick driver is fixed in 2.4.11-preX.
--
Brian Gerst
next prev parent reply other threads:[~2001-10-09 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 9:32 Athlon kernel crash (i686 works) Marco Berizzi
2001-10-09 11:45 ` [PATCH] again: " VDA
2001-10-09 11:04 ` Marco Berizzi
2001-10-09 11:55 ` Gergely Tamas
2001-10-09 13:59 ` Alejandro Conty
2001-10-09 14:19 ` Brian Gerst [this message]
[not found] ` <Pine.LNX.4.33.0110091611050.20120-100000@falka.mfa.kfki.hu>
2001-10-09 14:52 ` Alejandro Conty
2001-10-09 14:52 ` Gergely Tamas
2001-10-09 21:12 ` Dan Hollis
2001-10-09 22:22 ` Luigi Genoni
2001-10-09 14:27 ` Fabio Coatti
2001-10-09 21:11 ` Dan Hollis
2001-10-09 22:19 ` Luigi Genoni
2001-10-09 17:37 ` Roberto Jung Drebes
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 13:00 [PATCH] again: " Bryan Mayland
2001-10-09 14:28 ` Bill Davidsen
[not found] <fa.efssf0v.146031s@ifi.uio.no>
2001-10-10 4:06 ` Dan Maas
2001-10-10 8:09 ` VDA
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=3BC30755.30F47321@didntduck.org \
--to=bgerst@didntduck.org \
--cc=dice@mfa.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=zz01f074@etsiig.uniovi.es \
/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