[parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[joel.soete]

In NCR5380.c failled to compile because 'io_request_lock' undeclare.

'&io_request_lock' seems to became 'q->queue_lock' (include/linux/nbd.h)(with
request_queue_t *q).
Is it right?

Joel


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[Matthew Wilcox]

On Wed, Jul 24, 2002 at 02:32:01PM +0200, joel.soete@freebel.net wrote:
> In NCR5380.c failled to compile because 'io_request_lock' undeclare.

why are you trying to compile this driver?  do you _really_ have an NCR5380?

-- 
Revolutions do not require corporate support.

[parisc-linux] PAM unable to resolve symbol: pam_sm_cha uthtok

[phi]

Hi All,

I have setup pam.d/rlogind pam.d/login in such way that I could rlogin to my
palinux machine.

All is configured ok (since it works sometimes).

Here is a login attempt.

iws1pb05:/home/phi> rlogin iws1pb02
Connection closed.
iws1pb05:/home/phi> rlogin iws1pb02
Kill is %.
Interrupt is control-C (^C).
iws1pb02:/home/phi>

After some attempt it works, I don't understand what make it fail several time
before success.

Here is the log of this session

Jul 24 15:38:33 iws1pb02 pam_rhosts_auth[7889]: allowed to phi@iws1pb05 as phi
Jul 24 15:38:36 iws1pb02 PAM_unix[7672]: (cron) session closed for user mail
Jul 24 15:38:36 iws1pb02 rlogind[7919]: PAM unable to resolve symbol:
pam_sm_cha
uthtok
Jul 24 15:38:36 iws1pb02 rlogind[7919]: PAM unable to resolve symbol:
pam_sm_cha
uthtok
Jul 24 15:38:36 iws1pb02 pam_rhosts_auth[7919]: allowed to phi@iws1pb05 as phi
Jul 24 15:38:37 iws1pb02 PAM_unix[7923]: (login) session opened for user phi
by
(uid=0)

Sounds like rlogind is not able to always map pam_sm_chauthtok, when it
succeed, the login session is opened.

Dunno if the order have importance here, sounds like when it fail the
pam_rhosts_auth[7889]: allowed to phi@iws1pb05 came first while when it fail
it cam after.

Any ideas
Thanx in advance
Phi

Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[joel.soete]

Quoting Matthew Wilcox <willy@debian.org>:

> On Wed, Jul 24, 2002 at 02:32:01PM +0200, joel.soete@freebel.net wrote:
> > In NCR5380.c failled to compile because 'io_request_lock' undeclare.
> 
> why are you trying to compile this driver?  do you _really_ have an
> NCR5380?
> 
> -- 
> Revolutions do not require corporate support.
> 
inheritance from config-2.4.17-32 (of Debian kernel image of this time) :)

Too lasy to analyse exactly what I need for my 712, b180, b2000 I continue to
use it.

Joel


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[joel.soete]

Quoting Alan Cox <alan@lxorguk.ukuu.org.uk>:

> On Wed, 2002-07-24 at 13:32, joel.soete@freebel.net wrote:
> > In NCR5380.c failled to compile because 'io_request_lock' undeclare.
> > 
> > '&io_request_lock' seems to became 'q->queue_lock'
> (include/linux/nbd.h)(with
> > request_queue_t *q).
> > Is it right?
> 
> In the general case for NCR5380 no. There is a lot more that needs to
> be
> fixed to make that driver work on 2.5
> 
> 

Well it seems that I do not realy need it right now. So I will simply try to use
make oldconfig (just a test).

Joel


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[Alan Cox]

On Wed, 2002-07-24 at 13:32, joel.soete@freebel.net wrote:
> In NCR5380.c failled to compile because 'io_request_lock' undeclare.
> 
> '&io_request_lock' seems to became 'q->queue_lock' (include/linux/nbd.h)(with
> request_queue_t *q).
> Is it right?

In the general case for NCR5380 no. There is a lot more that needs to be
fixed to make that driver work on 2.5

Re: [parisc-linux] PAM unable to resolve symbol: pam_sm_cha uthtok

[Grant Grundler]

phi wrote:
> Jul 24 15:38:36 iws1pb02 rlogind[7919]: PAM unable to resolve symbol:
> pam_sm_chauthtok

This stinks alot like the other d-cache issues we've seen.
(eg syslogd faulting at boot time)

Which system model is this happening on? (/me guesses J5000 or PA2.0 K-class)

I don't know where the problem is though.

grant

Re: [parisc-linux] PAM unable to resolve symbol: pam_sm_cha uthtok

[phi]

Grant Grundler wrote:
> 
> phi wrote:
> > Jul 24 15:38:36 iws1pb02 rlogind[7919]: PAM unable to resolve symbol:
> > pam_sm_chauthtok
> 
> This stinks alot like the other d-cache issues we've seen.
> (eg syslogd faulting at boot time)

Ouch didn't suspect this was that deep, I was focusing on this f. pam to
setup.

> 
> Which system model is this happening on? (/me guesses J5000 or PA2.0 K-class)

This is a C180 running
Linux iws1pb02 2.4.18-pa22 #48

This old version was from my 'stable' 712, then I instaled the C180 via a
brute 
cpio -p onto the C180. Then it is a narrow kernel.

My plan (tomorow?) is to get the linux CVS source and recompile...


BTW I think I saw the exact same behavior on a 712 does the dcache problem
present there too? 

Well will see what I got tomorow.
Cheers,
Phi

Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?

[kenneth westelinck]

# CONFIG_SCSI_GENERIC_NCR5380 is not set
I'm not using it on my 712/60. So I guess you can remove this from your
config for your 712.

----- Original Message -----
From: <joel.soete@freebel.net>
To: "Matthew Wilcox" <willy@debian.org>
Cc: <joel.soete@freebel.net>; <parisc-linux@lists.parisc-linux.org>
Sent: Wednesday, July 24, 2002 3:46 PM
Subject: Re: [parisc-linux] K-2.5.26-pa0: NCR5380.c ?


> Quoting Matthew Wilcox <willy@debian.org>:
>
> > On Wed, Jul 24, 2002 at 02:32:01PM +0200, joel.soete@freebel.net wrote:
> > > In NCR5380.c failled to compile because 'io_request_lock' undeclare.
> >
> > why are you trying to compile this driver?  do you _really_ have an
> > NCR5380?
> >
> > --
> > Revolutions do not require corporate support.
> >
> inheritance from config-2.4.17-32 (of Debian kernel image of this time) :)
>
> Too lasy to analyse exactly what I need for my 712, b180, b2000 I continue
to
> use it.
>
> Joel
>
>
> -------------------------------------------------
> This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>

Re: [parisc-linux] PAM unable to resolve symbol: pam_sm_cha uthtok

[Grant Grundler]

phi wrote:
> Ouch didn't suspect this was that deep, I was focusing on this f. pam to
> setup.

It may not be.

> BTW I think I saw the exact same behavior on a 712 does the dcache problem
> present there too? 

No - and I don't expect it on C180 either.
So far I've only see it on SMP machines (with SMP kernel).

thanks,
grant