From: "Mohammad A. Haque" <mhaque@haque.net>
To: tommy@teatime.com.tw
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic for nfsd access for test12
Date: Sun, 17 Dec 2000 14:03:43 -0500 [thread overview]
Message-ID: <3A3D0E0F.9B617E76@haque.net> (raw)
In-Reply-To: <3A3D00A7.87F6051F@teatime.com.tw>
Do you use netfilter? It's a known bug if you do.
Tommy Wu wrote:
>
> Does anyone use nfsd on kernel 2.4.0-test12 ?
>
> Usually, I backup my linux box via another machine use nfs to mount it, then run
> afio to backup file to mo. It is work very fine through kernel 2.4.0-test7 to test11.
>
> But this week, I change my linux box's kernel to 2.4.0-test12, I found when I use
> another linux box (kernel 2.2.18pre21) to mount the directory in the linux server
> running kernel 2.4.0-test12, it can be mounted, but if I do any file access, the
> server will show kernel panic screen.... and there is no any log write down to file.
> All system will be halt, just can be power down. (SysRq don't work)
>
> I change the kernel back to 2.4.0-test11, everything is ok. So, I think it should be
> a bug in 2.4.0-test12. (I use the same .config to build both kernel, nfsd is make as
> a module)
>
> Because I can't see all of the kernel trace dump screen, so I can't give any ksymoops
> for that...
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-17 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 18:06 Kernel panic for nfsd access for test12 Tommy Wu
2000-12-17 19:03 ` Mohammad A. Haque [this message]
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=3A3D0E0F.9B617E76@haque.net \
--to=mhaque@haque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tommy@teatime.com.tw \
/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