From: Andris Pavenis <pavenis@lanet.lv>
To: haiquy@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre9-ac3 still OOPS when exiting X with i810 chipset
Date: Sat, 01 Jun 2002 18:53:19 +0300 [thread overview]
Message-ID: <3CF8EDEF.3070708@lanet.lv> (raw)
> I hope the problem has been fixed but not, Exactly the
> same oop message as I posted before; from 2.4.19-pre7
> up ; it always happen.
Same hardware as I'm using, but I haven't seen any OOPSes
already for a long time.
Currently I'm using the same kernel 2.4.19-pre9-ac3, XFree86-4.2.0
(with one i810 chipset related fix applied), KDE-3.0.1
All these are compiled with gcc-3.1 release. I haven't seen
any kernel OOPS'es already for a rather long time.
Andris
PS. i810 fix I mentioned dos not fix kernel OOPS, but only
X11 fatal error when switching from X11 to console (especially nasty
with new KDE versions, haven't seen with GNOME)
Andris
next reply other threads:[~2002-06-01 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 15:53 Andris Pavenis [this message]
2002-06-02 0:34 ` 2.4.19-pre9-ac3 still OOPS when exiting X with i810 chipset Steve Kieu
2002-06-02 14:52 ` Alan Cox
2002-06-03 7:41 ` Andris Pavenis
-- strict thread matches above, loose matches on Subject: below --
2002-06-01 5:36 Steve Kieu
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=3CF8EDEF.3070708@lanet.lv \
--to=pavenis@lanet.lv \
--cc=haiquy@yahoo.com \
--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