Hi List,
I'v rebuild the latest kernel (2.6.18-92.1.10.el5) with patch BZ#453094 included.
That new kernel is build as a kernel variant named "SoC" (like "xen" or "PAE")
so it can be installed whithout replacing any stock kernel.
There is a sligth difference with the default kernel : for use in my lab I've to
enable Samba/CIFS & IEEE1394 Firewire support (can be cheked in the ".config")
The kernel variant can be found here :
ftp://ftp.lip6.fr/pub/linux/distributions/slsoc/5x/i386/i386/SL/kernel-SoC-2.6.18-92.1.10.el5.i686.rpm
ftp://ftp.lip6.fr/pub/linux/distributions/slsoc/5x/i386/i386/SL/kernel-SoC-devel-2.6.18-92.1.10.el5.i686.rpm
Hope this helps.
On Sat, Aug 30, 2008 at 03:02:37PM +0200, Klaus Steinberger wrote:
> Hi,
>
> >Greetings. FWIW, I was about to send a similar note to the SL list when
> >I read your note. I think the discussion to this point has nailed the
> >issue, but, for the record, here's what we see:
> >
> > Aug 29 15:18:24 client-sys kernel: lockd: server xxxxxx not
> > responding, still trying
> >
> >While on the server we see:
> >
> > root 3569 0.0 0.0 0 0 ? D Aug27 0:00 [lockd]
> >
> >The process is not a user-land process and evidently cannot be stopped
> >except by killing the kernel, i.e., rebooting.
> Yep, the lockd hungs somewhere in a semaphore.
>
> >The user-level ramification is that some, but maybe not all (?),
> Only locking do not work ;-))
> But that blocks some applications, and definitly blocks logins under KDE.
>
> >And, yes, it WOULD be sweet if somebody could patch this.
> Yep.
>
> Sincerly,
> Klaus
--
.-. J e a n - P a u l C h a p u t
/v\ A d m i n i s t r a t e u r S y s t e m e
/(___)\ |
^^ ^^ |-- e-mail : [log in to unmask]
`-- Tel : (33) 01.44.27.53.99 [prof.]
06.66.25.35.55 [port.]
01.47.46.01.31 [pers.]
U P M C Universite Pierre & Marie Curie
L I P 6 Laboratoire d'Informatique de Paris VI
A S I M Architecture des Systemes Integres et Micro-electronique
|
