[lkml]   [1998]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.1.125 Show stopper list: Draft

no, experimenting on our mail spool would draw MY attention almost
immediately. however through the marvels of technology, I might be able to
help out on the mail server end. if alan and you can more accurate
pinpoint the problem, I can probably hook something up that simulates a
busy mailserver.


On Tue, 13 Oct 1998, Bill Hawes wrote:

> Alan Cox wrote:
> > Put a busy mail spool on it and wait. I suspect its because the
> > lockd thread wasnt doing any kind of lock_kernel() request. This was 2.1.121
> > I'll ask the previous victim to try again with 2.1.125 (shall I ask with
> > or without HJ's patches)
> Hi Alan,
> Actually lockd does do a lock_kernel when the kernel thread is
> started, so that's not the problem.
> Do we know what kind of locking requests the mail server is doing? I'd
> like to be able to reproduce the problem here, and setting up a "busy
> mail server" isn't very feasible for me.
> If you could have the original reporter try again (with or without any
> other patches), and then file an oops report or whatever if the
> problem still exists.
> Regards,
> Bill

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:45    [W:0.121 / U:0.356 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site