From: Greg KH <greg@kroah.com>
To: roma1390 <roma1390@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] nfs kernel server causes: kernel BUG at include/linux/module.h:386!
Date: Fri, 7 May 2010 09:56:07 -0700 [thread overview]
Message-ID: <20100507165606.GA795@kroah.com> (raw)
In-Reply-To: <4BE3BCDF.4080604@gmail.com>
On Fri, May 07, 2010 at 10:10:23AM +0300, roma1390 wrote:
> Greg KH wrote:
> > On Thu, May 06, 2010 at 08:47:27AM +0300, roma1390 wrote:
> >> Hello,
> >>
> >> after some nfs server start/stop i hit kernel bug on 2.6.26.
> There is hope[1] that this bug is fixed[2], and fix is merged[3]
> into 2.6.29. But there is missing bugfix for older stable kernels.
> >
> > 2.6.26 is not supported by the community anymore.
>
> Sadly, the debian 5.0 (current stable) chose 2.6.26 as distribution
> kernel. Of course they do kernel as part of distribution support by
> them self.
>
> > Is this a problem on the latest 2.6.27-stable kernel release? If so,
> > which specific patches in Linus's tree do you think resolves this? Is
> > it just the 22945e4a1c7454c97f5d8aee1ef526 commit that is needed to be
> > added there?
>
> Currently there isn't any free resources to do 2.6.27-stable
> testing. Switching from distribution kernel to custom one adds much
> more work for system admin, so this options is the last one none
> other will work.
>
> If there is any demand to test 22945e4a1c7454c97f5d8aee1ef526, there
> can be such test done. But this issue was found only once, and on
> first hour after nfs server configuration was started.
If you can't test it, if I add that commit id to .27, I don't see how
that would help you out at all, right?
Can you poke the debian developers about this?
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-07 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:47 nfs kernel server causes: kernel BUG at include/linux/module.h:386! roma1390
2010-05-06 6:03 ` [stable] " Greg KH
2010-05-07 7:10 ` roma1390
2010-05-07 16:56 ` Greg KH [this message]
2010-05-10 6:33 ` roma1390
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=20100507165606.GA795@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roma1390@gmail.com \
--cc=stable@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