public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerry Geis <geisj@pagestation.com>
To: Tarkan Erimer <tarkan@netone.net.tr>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG in 2.6.23.9
Date: Mon, 10 Dec 2007 06:40:13 -0500	[thread overview]
Message-ID: <475D259D.3080909@pagestation.com> (raw)
In-Reply-To: <475D0387.1070609@netone.net.tr>

Tarkan Erimer wrote:
> Arjan van de Ven wrote:
>> On Sun, 09 Dec 2007 14:49:16 -0500
>> Jerry Geis <geisj@pagestation.com> wrote:
>>
>>  
>>> I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day.
>>> Then sometime through the night the kernel dies, the trace is below.
>>>     
>>
>> is this when a 3D screensaver is active?
>> Probably worth running without the proprietary nvidia driver.... it
>> also tends to get more people to pay attention :)
>>
>>
>> In addition to this suspicion; you're the first one to report this oops
>> since at least a year as shown in
>> http://www.kerneloops.org/guilty.php?guilty=journal_dirty_data&version=2.6.23-release&start=1540096&end=1572863 
>>
>>
>> so it might well be something weird on your side (like the binary
>> driver or some heat problem created by having a 3D screensaver)
>>
>>   
> Hi,
>
> For a while, I have the same behavior. I tested under 2.6.23.9, 
> 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, 
> I don't use any proprietary driver. My video card is Intel-945 and I 
> use the "intel" driver. I use 3D screensavers as well. These kernels 
> die after some long idles like 1 or 2 days after. My distribution is 
> Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. 
> So, how to track this interesting problem ? Any ideas welcomed :-)
>
> Cheers,
>
> Tarkan Erimer
>
>
>
>
>
I am not running a 3D screen saver. I was just using blank screen.
However, I did turn off the screen saver and last night my machine did 
not crash.

I am still using the NVIDIA driver.
All I changed was the screen saver.

Any ideas on that?

Jerry


  reply	other threads:[~2007-12-10 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09 19:49 Kernel BUG in 2.6.23.9 Jerry Geis
2007-12-09 21:44 ` Arjan van de Ven
2007-12-10  9:14   ` Tarkan Erimer
2007-12-10 11:40     ` Jerry Geis [this message]
2007-12-10 12:02     ` Tarkan Erimer
2007-12-10 14:45     ` Arjan van de Ven
2007-12-10 15:37       ` Tarkan Erimer
2007-12-10 15:42         ` Jerry Geis

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=475D259D.3080909@pagestation.com \
    --to=geisj@pagestation.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tarkan@netone.net.tr \
    /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