From: Andrew Morton <akpm@osdl.org>
To: paterley <paterley@DrunkenCodePoets.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.74-mm2
Date: Sat, 5 Jul 2003 16:04:45 -0700 [thread overview]
Message-ID: <20030705160445.2ab1e0ec.akpm@osdl.org> (raw)
In-Reply-To: <20030705182359.269b404d.paterley@DrunkenCodePoets.com>
paterley <paterley@DrunkenCodePoets.com> wrote:
>
> ok, I get 4 of a kernel oops during boot, but the kernel seems to stay happy.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
EIP: 0060:[<00000000>] Not tainted VLI
[<c01637ab>] __lookup_hash+0x9b/0xd0
[<c0163ff7>] open_namei+0x2e7/0x420
[<c0153751>] filp_open+0x41/0x70
[<c0153bd3>] sys_open+0x53/0x90
[<c010945f>] syscall_call+0x7/0xb
inode->i_op->lookup() is NULL. Not good.
> according to dmesg, immediately prior to the first oops, smbfs was
> unloaded due to unsafe usage.
Well no, it say it cannot be unloedad.
Could you please unconfigure smbfs in the kernel build? And any other
less commonly used filesytems?
Does it still oops if smbfs is build into the kernel (not a module).
Please send a copy of your /etc/fstab.
Thanks.
next prev parent reply other threads:[~2003-07-05 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 20:25 2.5.74-mm2 Andrew Morton
2003-07-05 21:58 ` 2.5.74-mm2 paterley
2003-07-05 22:23 ` 2.5.74-mm2 paterley
2003-07-05 23:04 ` Andrew Morton [this message]
2003-07-06 0:01 ` 2.5.74-mm2 paterley
2003-07-06 0:49 ` 2.5.74-mm2 Andrew Morton
2003-07-06 1:40 ` 2.5.74-mm2 [kernel BUG at include/linux/list.h:148!] Ramón Rey Vicente
2003-07-06 13:49 ` Nick Orlov
2003-07-08 0:43 ` Mike Fedyk
2003-07-08 23:17 ` Ramón Rey Vicente
2003-07-09 0:18 ` Mike Fedyk
2003-07-09 0:32 ` Ramón Rey Vicente
2003-07-09 0:34 ` Mike Fedyk
2003-07-09 0:44 ` Ramón Rey Vicente
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=20030705160445.2ab1e0ec.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paterley@DrunkenCodePoets.com \
/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;
as well as URLs for NNTP newsgroup(s).