public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Sousa <ls.luis_sousa@yahoo.com.br>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata io freeze, 2.6.18 and also 2.6.24
Date: Fri, 28 Mar 2008 21:22:30 -0300 (ART)	[thread overview]
Message-ID: <610674.43534.qm@web46002.mail.sp1.yahoo.com> (raw)


--- Luis Sousa <ls.luis_sousa@yahoo.com.br> escreveu:

> --- Jeff Garzik <jeff@garzik.org> escreveu:
> 
> > Luis Sousa wrote:
> > > I've been having consistent hard system freezes for a
> > > long time, every 2 days or so, and finally decided to
> > > move to the most recent stable kernel. Unfortunatelly
> > > that didn't fix it. The freezes seem to be io-related;
> > > they started since I moved my drive to sata. They seem
> > > to happen mostly when there's an io-intensive operation,
> > > like extracting a big archive; a reboot is needed.
> > 
> > We need more info, namely full 'dmesg', 'lspci -v', and your kernel config.
> > 
> > Also, make /sure/ you are not running closed-source modules known to 
> > crash the system, like ndiswrapper or nvidia graphics driver.
> > 
> > 	Jeff
> 
> I'm quite sure.

Oops. My bad. I seem to actually be running the "nv" driver in xorg.conf. 
I had searched for "nvidia" before and so thought I had cleared that.
I didn't recall manually installing it this time. I'll try not using it.

--
Luis


      Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/


             reply	other threads:[~2008-03-29  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  0:22 Luis Sousa [this message]
2008-03-29 17:09 ` sata io freeze, 2.6.18 and also 2.6.24 Parag Warudkar
  -- strict thread matches above, loose matches on Subject: below --
2008-04-12  7:30 devzero
2008-04-12  0:59 Luis Sousa
2008-04-05  5:44 Luis Sousa
2008-03-28 22:24 Luis Sousa
2008-03-28 22:46 ` Jeff Garzik
2008-03-28 23:03   ` Luis Sousa

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=610674.43534.qm@web46002.mail.sp1.yahoo.com \
    --to=ls.luis_sousa@yahoo.com.br \
    --cc=jeff@garzik.org \
    --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