public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: putter <spam@perlpimp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: reiserfs autofix?
Date: Mon, 30 Apr 2001 00:07:04 -0700	[thread overview]
Message-ID: <20010430000704.A2313@vancouver.yi.org> (raw)
In-Reply-To: <20010429144827.A751@vancouver.yi.org> <621300000.988584911@tiny>
In-Reply-To: <621300000.988584911@tiny>; from mason@suse.com on Sun, Apr 29, 2001 at 06:55:11PM -0400

I think I have tracked down the problem to the card itself. My machine is on @ graphics mode all the time,
like 24hrs a day, and it seems that it is somewhat taxing on the cards performance. So now I switch down to
text mode, everytime I leave the machine. How did I find out? I placed my finger of heatsink of my GeForce DDR.
It was HOT! Fan works alright, so if I was to run computer a while, stress accumilates, and when I run GeForce
understress of maximum resolutions, it craps out. So much for NVidia eh?

BTW, I don't question graphical subsystem crashes. I question reiserfs that suppose to leave my partitions
in consistent state, no matter how trigger happy with power switch I am, or is my judgement is clouded? >=)

So here's details....: Offending reiserfs messages, after last boot.

  2376  Apr 29 15:23:28 candle fancylogin: from /dev/tty1: ACCESS GRANTED: pavel logged in 
  2377  Apr 29 15:23:33 candle kernel: NVRM: loading NVIDIA kernel module version 1.0-769 
  2378  Apr 29 16:24:29 candle kernel: mtrr: no MTRR for e4000000,2000000 found 
  2379  Apr 29 16:24:45 candle kernel: mtrr: no MTRR for e4000000,2000000 found 
  2380  Apr 29 16:24:50 candle fancylogin: from /dev/tty1: ACCESS GRANTED: pavel logged in 
  2381  Apr 29 16:31:18 candle modprobe: modprobe: Can't locate module net-pf-10
  2382  Apr 29 18:01:02 candle kernel: vs-13042: reiserfs_read_inode2: [7772 8013 0x0 SD] not found 
  2383  Apr 29 18:01:02 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2384  Apr 29 19:01:01 candle kernel: vs-13042: reiserfs_read_inode2: [7772 8013 0x0 SD] not found 
  2385  Apr 29 19:01:01 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2386  Apr 29 20:01:00 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2387  Apr 29 21:01:00 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2388  Apr 29 22:01:01 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2389  Apr 29 23:01:01 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 
  2390  Apr 29 23:52:55 candle sudo:    pavel : TTY=pts/1 ; PWD=/home/pavel ; USER=root ; COMMAND=/bin/su -
  2391  Apr 29 23:52:55 candle PAM_pwdb[2242]: (su) session opened for user root by pavel(uid=0)
  2392  Apr 29 23:53:07 candle PAM_pwdb[2263]: (su) session opened for user spam by pavel(uid=0)
  2393  Apr 29 23:54:42 candle PAM_pwdb[2263]: (su) session closed for user spam
  2394  Apr 29 23:54:44 candle PAM_pwdb[2285]: (su) session opened for user spam by pavel(uid=0)
  2395  Apr 30 00:00:14 candle sudo:    pavel : TTY=pts/0 ; PWD=/home/pavel ; USER=root ; COMMAND=/bin/su -
  2396  Apr 30 00:00:14 candle PAM_pwdb[2320]: (su) session opened for user root by pavel(uid=0)
  2397  Apr 30 00:01:00 candle kernel: vs-13048: reiserfs_iget: bad_inode. Stat data of (7772 8013) not found 

  reply	other threads:[~2001-04-30  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-29 21:48 reiserfs autofix? putter
2001-04-29 22:55 ` Chris Mason
2001-04-30  7:07   ` putter [this message]
2001-04-30 12:02     ` Chris Mason
2001-04-30 17:09     ` Alan Cox

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=20010430000704.A2313@vancouver.yi.org \
    --to=spam@perlpimp.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