Re: sio: lots of silo overflows on Asus K8V with Moxa Smartio C104H/PCI

Burkard Meyendriesch wrote:

> On Mon, 26 Apr 2004 23:48:46 +1000 (EST) Bruce Evans wrote:
>> On Mon, 26 Apr 2004, Burkard Meyendriesch wrote:
>> 
>> > on my Asus K8V with Moxa Smartio C104H/PCI I get lots of silo
>> > overflows when backing up my Palm over a serial line, even at 19.200
>> > baud.
>> >
>> > What's going wrong here? And what can I do?
>> > ...
>> 
>> You seem to have trimmed too much from the boot messages (I trimmed
>> the rest).  sio5 is not there.
>> 
>> > /var/log/messages after boot -v:
>> > Apr 24 14:09:00 Reineke kernel: Mounting root from ufs:/dev/ad10s1a
>> > Apr 24 14:09:00 Reineke kernel: ata6: spurious interrupt -
>> > status=0x50 error=0x00 Apr 24 14:09:00 Reineke last message repeated
>> > 4 times Apr 24 14:09:00 Reineke kernel: start_inata6: spurious
>> > interrupt - status=0x50 error=0x00 Apr 24 14:09:00 Reineke kernel:
>> > ata6: spurious interrupt - status=0x50 error=0x00 Apr 24 14:09:01
>> > Reineke last message repeated 666 times Apr 24 14:09:01 Reineke
>> > named[301]: starting BIND 9.2.3..
>> >
>> > Apr 26 11:03:12 Reineke kernel: sio5: 1 more silo overflow (total
>> > 43) Apr 26 11:03:12 Reineke kernel: ata6: spurious interrupt -
>> > status=0x50 error=0x00 Apr 26 11:03:32 Reineke last message repeated
>> > 172 times Apr 26 11:03:33 Reineke kernel: sio5: 1 more silo overflow
>> > (total 44) Apr 26 11:03:33 Reineke kernel: ata6: spurious interrupt
>> > - status=0x50 error=0x00 Apr 26 11:03:43 Reineke last message
>> > repeated 21 times Apr 26 11:03:44 Reineke kernel: sio5: 1 more silo
>> > overflow (total 45)
>> 
>> sio5's interrupt might be misconfigured.  If it has none, then it is
>> supposed to fall back to polled mode but should still get less
>> overflows than above.  ata6 seems to be getting sio5's interrupts.
>> 
>> In general, puc must be used with sio except for isa ports, and all
>> sio interrupts should be unshared.  For pci sio cards, making the
>> interrupt unshared may require juggling pci slots or using APIC mode.
>> 
> Sorry, I forgot to send the sio's boot message (I forgot it because it
> didn't say anything in boot -v mode). Here are the boot messages:
> 
> Apr 30 10:13:38 Reineke kernel: puc0: <Moxa Technologies, Smartio
> C104H/PCI> port 0xa000-0xa00f,0xa400-0xa43f,0xa800-0xa87f irq 19 at device
> 14.0 on pci0 Apr 30 10:13:38 Reineke kernel: puc0: Reserved 0x40 bytes for
> rid 0x18 type 4 at 0xa400 Apr 30 10:13:38 Reineke kernel: sio4: <Moxa
> Technologies, Smartio C104H/PCI> on puc0 Apr 30 10:13:38 Reineke kernel:
> sio4: type 16550A Apr 30 10:13:38 Reineke kernel: sio4: unable to activate
> interrupt in fast mode - using normal mode Apr 30 10:13:38 Reineke kernel:
> sio5: <Moxa Technologies, Smartio C104H/PCI> on puc0 Apr 30 10:13:38
> Reineke kernel: sio5: type 16550A Apr 30 10:13:38 Reineke kernel: sio5:
> unable to activate interrupt in fast mode - using normal mode Apr 30
> 10:13:38 Reineke kernel: sio6: <Moxa Technologies, Smartio C104H/PCI> on
> puc0 Apr 30 10:13:38 Reineke kernel: sio6: type 16550A Apr 30 10:13:38
> Reineke kernel: sio6: unable to activate interrupt in fast mode - using
> normal mode Apr 30 10:13:38 Reineke kernel: sio7: <Moxa Technologies,
> Smartio C104H/PCI> on puc0 Apr 30 10:13:38 Reineke kernel: sio7: type
> 16550A Apr 30 10:13:38 Reineke kernel: sio7: unable to activate interrupt
> in fast mode - using normal mode
> 
> Meanwhile I plugged the Moxa board into another PCI slot of my motherboard
> and the conflict with the ata6 interrupt seems to be solved. The silo
> over- flows are still there.
> 
> By the way: How should I set the BIOS parameters "PCPI 2.0 yes/no" and
> "ACPI APIC yes/no"? Do they have anything to do with the PCI interrupt
> behaviour?

I had to enable APIC to get my puc supported card to work.  W/o it the
interrupts were shared and I received a ton of silo overflows and lost data
on line.

so try the following in your kernel and rebuild

options COM_MULTIPORT
options PUC_FASTINTR

device apic



> Burkard
> 
> --
> Burkard Meyendriesch
> Stevern 2
> D-48301 Nottuln
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

-- 
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);