On Thu, 5 Aug 1999, hoi wrote:
> hi,
>
> can somebody help me in urgent!!!
> pls pls pls
>
> Now, i have found a problem,
> it 's due to the SMP support in kernel,
>
> i am using the SuSE 6.1 with kernel 2.2.7,
> and my machine have dual PII 400 CPU, and i need to config and recomplie
> the kernel to support this SMP, when this SMP support is tackle in the
> kernel,
> the pppd can't run!
> if the SMP support is not compiled in the kernel, the pppd function pretty
> good!
>
> for the case of the SMP in kernel, the /var/log/messages shows:
>
> Aug 4 20:47:13 pop3 kernel: PPP: version 2.3.7 (demand dialling)
> Aug 4 20:47:13 pop3 kernel: PPP line discipline registered.
> Aug 4 20:47:13 pop3 kernel: registered device ppp0
> Aug 4 20:47:13 pop3 pppd[179]: pppd 2.3.8 started by a_ppp, uid 0
> Aug 4 20:47:13 pop3 pppd[179]: ioctl(PPPIOCGUNIT): Operation not
> permitted(1)
> Aug 4 20:47:13 pop3 pppd[179]: tcsetattr: Operation not permitted
> Aug 4 20:47:13 pop3 pppd[179]: Exit.
>
It should work fine. I have a quad xeon (redhat 6) running 2.2.10
and pppd is working fine (I am on my notebook running linux) connected
to my quad xeon via a 56kb ppp connection...
> if no SMP, others setting the same, and recompile, after that, the
> /var/log/messages/shows:
>
> Aug 4 20:58:09 pop3 kernel: PPP: version 2.3.7 (demand dialling)
> Aug 4 20:58:09 pop3 kernel: PPP line discipline registered.
> Aug 4 20:58:09 pop3 kernel: registered device ppp0
> Aug 4 20:58:09 pop3 pppd[188]: pppd 2.3.8 started by a_ppp, uid 0
> Aug 4 20:58:09 pop3 pppd[188]: Using interface ppp0
> Aug 4 20:58:09 pop3 pppd[188]: Connect: ppp0 <--> /dev/ttyQ1a1
> Aug 4 20:58:09 pop3 pppd[188]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
> <auth pap> <magic 0x2c2393a8> <pcomp> <accomp>]
> Aug 4 20:58:12 pop3 pppd[188]: rcvd [LCP ConfReq id=0x3 <asyncmap 0xa0000>
> <magic 0x672056> <pcomp> <accomp> <callback CBCP>]
> Aug 4 20:58:12 pop3 pppd[188]: sent [LCP ConfRej id=0x3 <callback CBCP>]
> Aug 4 20:58:12 pop3 pppd[188]: rcvd [LCP ConfReq id=0x4 <asyncmap 0xa0000>
> <magic 0x672056> <pcomp> <accomp>]
> Aug 4 20:58:12 pop3 pppd[188]: sent [LCP ConfAck id=0x4 <asyncmap 0xa0000>
> <magic 0x672056> <pcomp> <accomp>]
>
> do u know what's going on and if yes , how to fix it?
here is what I normally see on the quad xeon end (I dial into the
quad from home using my notebook):
Aug 5 21:02:12 crafty mgetty[24474]: data dev=ttyS2, pid=24474,
caller='none', conn='26400/ARQ/V34/LAPM/V42BIS', name='',
cmd='/bin/login', user='ppp'
Aug 5 21:02:12 crafty PAM_pwdb[24474]: (login) session opened for user
ppp by (uid=0)
Aug 5 21:02:12 crafty pppd[24636]: pppd 2.3.7 started by ppp, uid 19
Aug 5 21:02:12 crafty pppd[24636]: Using interface ppp0
Aug 5 21:02:12 crafty pppd[24636]: Connect: ppp0 <--> /dev/ttyS2
Aug 5 21:02:13 crafty pppd[24636]: found interface eth0 for proxy arp
Aug 5 21:02:13 crafty pppd[24636]: local IP address 138.26.65.12
Aug 5 21:02:13 crafty pppd[24636]: remote IP address 138.26.65.13
SMP shouldn't affect this at all unless you broke ppp (didn't include
it) when you built your SMP kernel... (this is a kernel config option
to include ppp support).
>
>
>
>
>
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]