[lkml]   [2005]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.13-rc6-mm1
On Fri, 2005-08-19 at 18:36 -0700, Andrew Morton wrote:
> Reuben Farrelly <> wrote:
> >
> > ...
> > >> 4. PAM is complaining about "PAM audit_open() failed: Protocol not suppor
> > >> ted" and I can't log in as any user including root. I would have picked this
> > >> was a userspace problem, but it doesn't break with -rc5-mm1, yet reproduceably
> > >> breaks with -rc6-mm1. Weird.
> > >
> > > hm. How come you're able to use the machine then?
> >
> > Machine was booting up ok, and things were being written to syslog. Rebooted
> > into -rc5-mm1 to investigate, and of course could boot into rc6-mm1 in single
> > user mode, test and bring services up one by one from there. Having two boxes
> > helped too.
> >
> > > Is it possible to get an strace of this failure somehow?
> >
> > Not sure if this is needed anymore, as I found that the problem goes away when
> > I compile in kernel auditing. This not required for -rc5-mm1. Is that change
> > intended?
> >
> Sounds wrong to me, especially if 2.6.13-rc6 doesn't do that.

Hm. It sounds like you'd configured PAM to require the pam_loginuid
module even though you didn't have auditing enabled in your kernel. That
seems strange and wrong to me, and _is_ a userspace problem.

I'd also agree that it shouldn't have changed with the new kernel though
-- and I can't think of anything I changed recently which would have
that effect. An strace would still be useful.

Can you double-check that you didn't have auditing enabled in your
older, working kernel?


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

 \ /
  Last update: 2005-08-20 15:47    [W:0.064 / U:7.152 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site