I finally set up pppd between 2 NetBSD-1.5.2/i386 using a cross serial
cable.  I was able to reproduce a problem but the sympton isn't the
same.
An ALTQ patched kernel hungs up when pppd starts, apparently just
after the first packet arrives.
It is strange that a KAME kernel which has almost identical ALTQ code
works fine.

	OK	stock GENERIC
	NG	GENERIC with altq-3.0 patch applied
	OK	GENERIC.KAME from a KAME snap

For the NG case, I can break into DDB by Alt-Ctrl-ESC and the trace
command shows it was in Xspllower() from pppintr().  Apparently, the
kernel loops in Xspllower().
I don't think ALTQ changes any interrupt handling but I'll take a
closer look tomorrow.
Does anyone have an idea about what's going on?

-Kenjiro

Hendra Widarta wrote:
> Hi Kenjiro,
> 
> NetBSD-1.5.2, altq-3.0, pppd-2.4.0 problem...
> 
> I think ALTQ has queued all outgoing PPP packets (from LCP), except the first LCP packet.
> LCP id=0x1 has successfully sent and received.
> 
> Here is the log: (/var/log/pppd.log)
> Using interface ppp0
> Connect: ppp0 <--> /dev/tty01
> sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x17f1582f> <pcomp> <accomp>]
> rcvd [LCP ConfReq id=0xa5 <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xa5 <auth pap>]
> rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x17f1582f> <pcomp> <accomp>]
> rcvd [LCP ConfReq id=0xa6 <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xa6 <auth pap>]
> rcvd [LCP ConfReq id=0xa7 <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xa7 <auth pap>]
> rcvd [LCP ConfReq id=0xa8 <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xa8 <auth pap>]
> rcvd [LCP ConfReq id=0xa9 <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xa9 <auth pap>]
> rcvd [LCP ConfReq id=0xaa <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xaa <auth pap>]
> rcvd [LCP ConfReq id=0xab <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xab <auth pap>]
> rcvd [LCP ConfReq id=0xac <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xac <auth pap>]
> rcvd [LCP ConfReq id=0xad <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xad <auth pap>]
> rcvd [LCP ConfReq id=0xae <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xae <auth pap>]
> rcvd [LCP ConfReq id=0xaf <asyncmap 0xa0000> <auth pap> <magic 0x3d971c90> <pcomp> <accomp>]
> sent [LCP ConfRej id=0xaf <auth pap>]
> Modem hangup
> Connection terminated.
> 
> After the connection terminated, 
> #netstat -I ppp0 -d
> Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls Drops
> ppp0* 1500  <Link>                                12     0        1     0     0     0
> 
> According to pppd.log file, there are 12 incoming/outgoing packets, 12 times sent and rcvd LCP.
> But netstat reported 12 Ipkts, and 1 Opkts.
> 
> So, It seems that ALTQ has queued all outgoing LCP packets, but ALTQ can NOT send them out.
> 
> Thanks,
> Hendra
> 
> __________________________________________________
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> http://promo.yahoo.com/videomail/