mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mail List <linux-kernel@vger.kernel.org>,
	George Georgalis <george@galis.org>
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops
Date: Fri, 25 Jun 2004 16:16:03 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406251602140.1844@ppc970.osdl.org> (raw)
In-Reply-To: <20040625213433.GB6502@trot.local>



On Fri, 25 Jun 2004, George Georgalis wrote:
> 
> However at about 3Gb (if that is relevant) top segfaulted with a
> non critical oops. top will not restart, but the box is otherwise
> functioning well considering the write load.

Ok, this is unlikely to be SATA-related, unless SATA just happened to 
corrupt something really strange.

> Unable to handle kernel NULL pointer dereference at virtual address 000000b4
>  printing eip:
> c017c78a
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT 
> CPU:    0
> EIP:    0060:[<c017c78a>]    Not tainted
> EFLAGS: 00010286   (2.6.7-sta-bk8) 
> EIP is at pid_alive+0xa/0x30

That's "p->pids[PIDTYPE_PID].pidptr", and it looks like "p" is NULL.

That in turn _shouldn't_ happen, since that comes from 

	struct task_struct *task = proc_task(inode);

and proc_task() should always be non-NULL for any /proc file that has one 
of the pid-based dentry ops. 

> Could this be related to "Unknown HZ value! (91) Assume 100." which
> started showing up with VIA motherboards on 2.5.x (I think) on top or ps
> commands.  When I researched it before, It never caused ill, had been
> identified as a "kernel bug" but benign. I know nothing more.

No, that's just a pstools bug. It shouldn't try to guess HZ at all.

> ATM, ps also seg faults, here is a corresponding oops,

Same problem. One of your existing /proc/<xxx>/ directories has a NULL 
"task" pointer, and that really shouldn't happen.

Hmm. I do worry that maybe it's the SATA thing that has written NULL 
somewhere, since the /proc code never clears that field once it is set 
(and it would always be set by the code that creates the inode in the 
first place). 

		Linus

  reply	other threads:[~2004-06-25 23:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 17:05 SIIMAGE sata fails with 2.6.7 George Georgalis
2004-06-22 20:25 ` Jeff Garzik
2004-06-23 14:16   ` George Georgalis
2004-06-23 15:32     ` Hugo Mills
2004-06-23 16:35       ` George Georgalis
2004-06-23 17:30         ` Ricky Beam
2004-06-23 20:25           ` George Georgalis
2004-06-23 21:23             ` Fabian Fenaut
2004-06-23 21:50               ` SIIMAGE and sata_sil with 2.6.7-bk George Georgalis
2004-06-24  0:59             ` SIIMAGE sata fails with 2.6.7 Ricky Beam
2004-06-24 15:59               ` SATA_SIL fails with 2.6.7-bk6 seagate drive George Georgalis
2004-06-24 18:46                 ` Ricky Beam
2004-06-25 21:34                   ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops George Georgalis
2004-06-25 23:16                     ` Linus Torvalds [this message]
2004-06-28  2:12                       ` George Georgalis
2004-06-29  8:28                         ` radix-tree.c or sata_sil.c 2.6.7-bk oops George Georgalis
2004-07-02 22:17                           ` George Georgalis
2004-06-29  8:46                     ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops Sebastian Slota
2004-06-30  4:43                       ` George Georgalis
2004-06-30  6:16                         ` Jeff Garzik
2004-07-02 23:01                           ` George Georgalis
2004-06-26 12:37 Albert Cahalan
2004-06-26 15:12 ` Arjan van de Ven
2004-06-26 16:00   ` Linus Torvalds
2004-06-26 16:14     ` Arjan van de Ven
2004-06-26 17:17     ` Albert Cahalan
2004-06-26 17:13   ` Albert Cahalan
2004-06-26 15:54 ` Linus Torvalds

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=Pine.LNX.4.58.0406251602140.1844@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=george@galis.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

all inboxes | Powered by JetHome®