public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommy Wu <tommy@teatime.com.tw>
To: linux-kernel@vger.kernel.org
Subject: Kernel panic for nfsd access for test12
Date: Mon, 18 Dec 2000 02:06:31 +0800	[thread overview]
Message-ID: <3A3D00A7.87F6051F@teatime.com.tw> (raw)


  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...

-- 

    Tommy Wu
    mailto:tommy@teatime.com.tw
    http://www.teatime.com.tw/~tommy
    ICQ: 22766091
    Mobile Phone: +886 936 909490
    TeaTime BBS +886 2 3151964 24Hrs V.Everything

-
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/

             reply	other threads:[~2000-12-17 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17 18:06 Tommy Wu [this message]
2000-12-17 19:03 ` Kernel panic for nfsd access for test12 Mohammad A. Haque

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=3A3D00A7.87F6051F@teatime.com.tw \
    --to=tommy@teatime.com.tw \
    --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