public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Holger Hoffstätte" <holger@wizards.de>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Nasty regression from .27.7 to .27.8: idle samba goes crazy
Date: Thu, 11 Dec 2008 15:40:41 -0800	[thread overview]
Message-ID: <20081211234041.GA1119@kroah.com> (raw)
In-Reply-To: <49419A14.50402@wizards.de>

On Thu, Dec 11, 2008 at 11:54:12PM +0100, Holger Hoffstätte wrote:
> 
> Dear all -
> 
> Thanks for your efforts.
> 
> Manfred Spraul wrote:
> > Chuck Ebbert wrote:
> >> On Mon, 8 Dec 2008 23:22:46 +0100
> >> Jan Rekorajski <baggins@sith.mimuw.edu.pl> wrote:
> >>
> >>  
> >>> On Mon, 08 Dec 2008, Stefan Richter wrote:
> >>>
> >>>    
> >>>>>>> On Monday, 8 of December 2008, Holger Hoffstaette wrote:
> >>>>>>>            
> >>>>>>>> The system is a generic old single-core P4 box with a single
> >>>>>>>> SATA drive,
> >>>>>>>> Gentoo userland and Samba is 3.0.33 (in async mode). The kernel
> >>>>>>>> has no
> >>>>>>>> patches or binary drivers.
> >>>>>>>>               
> >>>> Holger, it may be unrelated to the issue, but to be sure:  Which
> >>>> network
> >>>> card driver do you use?
> >>>>       
> >>> I think you can safely rule out NIC, I'm also seeing this behaviour on a
> >>> brand new server with imap hanging in some busy-loop.
> >>> Network card in my case:
> >>> Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
> >>>
> >>> What I observer was one CPU doing 100% system work, and the number of
> >>> timer interrupts went from 1k per second to 4k (for the whole system).
> >>>
> > Could you try the attached patch?
> > It should fix the bug.
> 
> I just built 2.6.27.9-rc1 and disconnected the Windowz box several times.
> For now smbd does not seem to go into a death spin any more, even though
> as far as I can tell .9-rc1 does not contain Manfred'd latest patch. Not
> sure what that means, if anything.

.9-rc1 does contain a cifs patch, so perhaps that resolved the issue for
you.

thanks,

greg k-h

  reply	other threads:[~2008-12-11 23:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  6:18 Nasty regression from .27.7 to .27.8: idle samba goes crazy Holger Hoffstaette
2008-12-08  7:34 ` Rafael J. Wysocki
2008-12-08  8:07   ` Holger Hoffstaette
2008-12-08 16:46     ` Stefan Richter
2008-12-08 19:19       ` Stefan Richter
2008-12-08 20:08         ` Holger Hoffstaette
2008-12-08 22:22         ` Jan Rekorajski
2008-12-09 17:37           ` Chuck Ebbert
2008-12-09 19:16             ` Manfred Spraul
2008-12-09 19:30               ` Chuck Ebbert
2008-12-10 17:37             ` Manfred Spraul
2008-12-11 22:54               ` Holger Hoffstätte
2008-12-11 23:40                 ` Greg KH [this message]
2008-12-12 10:59                   ` [stable] " Holger Hoffstätte
2008-12-12  1:08               ` Jan Rekorajski
2008-12-12 18:26                 ` Jan Rekorajski
2008-12-12 14:01               ` Holger Hoffstätte
2008-12-08 16:32   ` Stefan Richter
2008-12-08 18:46     ` Rafael J. Wysocki
2008-12-08 19:14       ` Stefan Richter

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=20081211234041.GA1119@kroah.com \
    --to=greg@kroah.com \
    --cc=holger@wizards.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=stable@kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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