Hi,

I had just started a ppp connection (to a NetBSD/i386 system, over
ser02 at 57600), and began ftp'ing a file to my TT.  About 5 seconds
into the transfer, I got some strange syslog messages.  The system
continued running (no crash or panic).  The transfer running at the
time the messages were generated completed OK.  I did some more
transfers, and the messages were not repeated.

What do the messages mean?  Should I be concerned?  Do I have a
possible hardware problem or configuration problem, or is this a
potential software bug, or is it harmless?

The kernel is a stock 1.3_ALPHA BOOTX kernel.  Here is my SCSI
configuration:

sd0 at scsibus0 targ 0 lun 0: <QUANTUM, LIGHTNING 730S, 241E> SCSI2 0/direct fixed
sd0: 699MB, 3658 cyl, 4 head, 97 sec, 512 bytes/sect x 1431760 sectors
st0 at scsibus0 targ 3 lun 0: <ARCHIVE, Python 01931-XXX, 5.63> SCSI2 1/sequential removable
st0: density code 0x13, 512-byte blocks, write-enabled
sd1 at scsibus0 targ 4 lun 0: <DEC, RZ25     (C) DEC, 0700> SCSI2 0/direct fixed
sd1: 406MB, 1476 cyl, 9 head, 62 sec, 512 bytes/sect x 832527 sectors

The syslog entries are appended below.

Thanks,
entropy

Dec  2 09:21:16 seki pppd[270]: pppd 2.3.1 started by root, uid 0
Dec  2 09:21:16 seki pppd[270]: Using interface ppp0
Dec  2 09:21:16 seki pppd[270]: Connect: ppp0 <--> /dev/ser02
Dec  2 09:21:19 seki pppd[270]: local  IP address 206.20.83.203
Dec  2 09:21:19 seki pppd[270]: remote IP address 206.20.83.195
Dec  2 09:24:00 seki /netbsd: -->scsi_show: scsi_main is not running
Dec  2 09:24:00 seki /netbsd: REQ-ISSUED: 0 0x11ee000[8192] cmd[0]=a S=0 M=ff R=0 resid=8192 dr_flag=8 
Dec  2 09:24:00 seki /netbsd: REQ-DISCONNECTED: 0 0xa5e000[1024] cmd[0]=a S=0 M=4 R=0 resid=1024 dr_flag=8 
Dec  2 09:24:01 seki /netbsd: Bus signals (00/00): 
Dec  2 09:24:01 seki /netbsd: Dma status (10): IRQ
Dec  2 09:24:01 seki /netbsd: busy:1, spl:2104
Dec  2 09:24:01 seki /netbsd: 	0	tpio1
Dec  2 09:24:01 seki /netbsd: 	1	tpio2
Dec  2 09:24:01 seki /netbsd: 	2	scsi_select10
Dec  2 09:24:01 seki /netbsd: 	3	info_transf1
Dec  2 09:24:01 seki /netbsd: 	4	tpio1
Dec  2 09:24:01 seki /netbsd: 	5	tpio2
Dec  2 09:24:01 seki /netbsd: 	6	info_transf5
Dec  2 09:24:01 seki /netbsd: 	7	info_transf1
Dec  2 09:24:01 seki /netbsd: 	8	tpio1
Dec  2 09:24:01 seki /netbsd: 	9	tpio2
Dec  2 09:24:01 seki /netbsd: 	10	hmessage1
Dec  2 09:24:02 seki /netbsd: 	11	hmessage7
Dec  2 09:24:02 seki /netbsd: 	12	scsi_main2
Dec  2 09:24:02 seki /netbsd: 	13	scsi_main4
Dec  2 09:24:02 seki /netbsd: 	14	scsi_main5
Dec  2 09:24:02 seki /netbsd: ncrscsi0: Spurious interrupt.
Dec  2 09:24:02 seki /netbsd: -->scsi_show: scsi_main is not running
Dec  2 09:24:02 seki /netbsd: REQ-DISCONNECTED: 0 0x11ee000[8192] cmd[0]=a S=0 M=4 R=0 resid=8192 dr_flag=8 
Dec  2 09:24:02 seki /netbsd: Bus signals (00/00): 
Dec  2 09:24:02 seki /netbsd: Dma status (10): IRQ
Dec  2 09:24:02 seki /netbsd: busy:1, spl:2104
Dec  2 09:24:02 seki /netbsd: 	0	tpio1
Dec  2 09:24:02 seki /netbsd: 	1	tpio2
Dec  2 09:24:02 seki /netbsd: 	2	scsi_select10
Dec  2 09:24:02 seki /netbsd: 	3	info_transf1
Dec  2 09:24:02 seki /netbsd: 	4	tpio1
Dec  2 09:24:03 seki /netbsd: 	5	tpio2
Dec  2 09:24:03 seki /netbsd: 	6	info_transf5
Dec  2 09:24:03 seki /netbsd: 	7	info_transf1
Dec  2 09:24:03 seki /netbsd: 	8	tpio1
Dec  2 09:24:03 seki /netbsd: 	9	tpio2
Dec  2 09:24:03 seki /netbsd: 	10	hmessage1
Dec  2 09:24:03 seki /netbsd: 	11	hmessage7
Dec  2 09:24:03 seki /netbsd: 	12	scsi_main2
Dec  2 09:24:03 seki /netbsd: 	13	scsi_main4
Dec  2 09:24:03 seki /netbsd: 	14	scsi_main5
Dec  2 09:24:03 seki /netbsd: ncrscsi0: Spurious interrupt.

--
entropy -- it's not just a good idea, it's the second law.