From: Martin Schlemmer <azarah@nosferatu.za.org>
To: "Paweł Sikora" <pluto@pld-linux.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.7+current cset] *bug* in scheduler...
Date: Sun, 11 Jul 2004 20:11:14 +0200 [thread overview]
Message-ID: <1089569473.8708.3.camel@nosferatu.lan> (raw)
In-Reply-To: <200407080102.31766.pluto@pld-linux.org>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Thu, 2004-07-08 at 01:02, Paweł Sikora wrote:
> with cset-20040630_0514 everything works fine.
> with current cset xmms causing nice ooops ;)
>
Unfortunately you will have to try without the nVidia driver to get
somebody to have a look. I have similar issues with latest nvidia
driver and when fbdev in use - vga=normal works fine.
Cheers,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-07-11 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 23:02 [2.6.7+current cset] *bug* in scheduler Paweł Sikora
2004-07-11 18:11 ` Martin Schlemmer [this message]
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=1089569473.8708.3.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.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