Re: sio problems?
In message <[EMAIL PROTECTED]>, Wesley Morgan writes: >The sio driver was touched recently for the PUC stuff... Not sure if that >is the source of my problem, but suddenly I am seeing many many many of >these: > >sio1: 22 more interrupt-level buffer overflows (total 2943) > >Just started recently. Seems to happen most often when I cvsup. Happens >with and without ACPI, with and without using a shared interrupt. The changes to the PUC driver does not have anything to do with this I think. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sio problems?
The sio driver was touched recently for the PUC stuff... Not sure if that is the source of my problem, but suddenly I am seeing many many many of these: sio1: 22 more interrupt-level buffer overflows (total 2943) Just started recently. Seems to happen most often when I cvsup. Happens with and without ACPI, with and without using a shared interrupt. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio problems?
On Sat, Oct 07, 2000 at 08:03:12PM -0500, Mike Meyer wrote: > I recently got my digital camera back out, and started pulling the old > pictures from it. I noticed something I hadn't ever seen before - silo > overflows from the sio port. At the moment, I'm wondering if this is a > known problem that is being investigated (SMPNG comes to mind), or > something new. The sio device doesnt work well at high speed because of the recent SMPng changes. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re: sio problems?
attila! writes: > on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer <[EMAIL PROTECTED]> said: > > I recently got my digital camera back out, and started pulling the old > > pictures from it. I noticed something I hadn't ever seen before - silo > > overflows from the sio port. At the moment, I'm wondering if this is a > > known problem that is being investigated (SMPNG comes to mind), or > > something new. > Other than the sio irq overflows, which does not seem to > particularly impact performance and which I am sure will be > solved, I think team has done a superb job with the SMPNG > cutover. Well, it's making a serious impact on performance for camera. I wasn't able to reliably download images at even half speed. I gave up and dropped from 115K to 9.6K. I can probably get better speed than that, but even if it's 28K, that's noticable :-(. On the other hand, that's the only real problem I've seen. Unfortunately, I haven't used the thing since the hardware was cutover from -stable, so I can't pin it down either.
re: sio problems?
on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer <[EMAIL PROTECTED]> said: > I recently got my digital camera back out, and started pulling the old > pictures from it. I noticed something I hadn't ever seen before - silo > overflows from the sio port. At the moment, I'm wondering if this is a > known problem that is being investigated (SMPNG comes to mind), or > something new. > sio0/irq4 and sio1/irq3 are inactive sio2/irq5 is ppp 121 ?? Ss 4:55.69 /usr/sbin/ppp -quiet -ddial -nat papchap sio2 has also shown 7500+ irq buffer over-flows in 85 hours; this problem predates PRE_SMPNG; I don't remember when exactly since I was having problems with SCSI/da ahc (aic 7880 onboard --ASUS P2L97S-440BX-- driving 2 IBM 68 pin UltraWides) driver stalling with SCB block 6 timeouts which made my -current compiles unusable from roughly 25 Aug until it cleared with a build on 24 Sep after the SMPNG cutover (I am not holding at PRE_SMPNG). Other than the sio irq overflows, which does not seem to particularly impact performance and which I am sure will be solved, I think team has done a superb job with the SMPNG cutover. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sio problems?
I recently got my digital camera back out, and started pulling the old pictures from it. I noticed something I hadn't ever seen before - silo overflows from the sio port. At the moment, I'm wondering if this is a known problem that is being investigated (SMPNG comes to mind), or something new. Thanx,
pccard sio problems (Re: HEADSUP: wd driver will be retired!)
Zitiere Daniel Eischen <[EMAIL PROTECTED]>: > > In message <[EMAIL PROTECTED]> Christopher Masto > writes: > > : Right now, I have no sound (not detected), no USB (panic on removal), > > : can\\\'t use my sio pccard, can\\\'t eject my ed pccard, my IDE drives are > > : taking hours to dump and fsck, and my TV card is missing every other > > : line if I try to use the (not working anyway) closed caption decoder. > > > > I have some patches for the can\'t eject the network cards from a user > > that I\'m trying out and would then need to get committed to the > > network layer to properly support if_detach(). > > > > What\'s wrong with your sio pccard? Mine works well enough... > > Mine hasn\'t worked since a kernel built from Nov 23 sources. It > broke sometime between then and December 4th. Just built a new > kernel from todays sources, and still no go. > > pccardd[47]: driver allocation failed for Motorola (MONTANA 33.6 FAX/MODEM): > Device not configured > I also had problems with latest -current. After a little debugging I noticed that sio.c doesn\'t include \"card.h\" which defines NCARD, so the pccard stuff isn\'t compiled in. I added that line to sio.c, recompiled, and sio for pccard was at least again partially functional. I have two pccard sio devices, one seems to work, the other one freezes the machine during a simple \"stty -a < /dev/cuaaX\". I have attached the CIS information of these cards with my pccard.conf. Ejecting sio also doesn\'t seem to work. The machine is freezed afterwards. I can eject my DLink ed card, but after a re-insertion the driver isn\'t attached any more. Daniel Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 32 000: 04 01 49 6e 74 65 6c 6c 69 67 65 6e 74 00 50 43 010: 4d 43 49 41 20 46 41 58 2b 4d 4f 44 45 4d 00 ff Version = 4.1, Manuf = [Intelligent],card vers = [PCMCIA FAX+MODEM] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 02 01 00 PCMCIA ID = 0x200, OEM ID = 0x1 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 00 Serial port/modem Tuple #5, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 5c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #6, code = 0x22 (Functional EXT), length = 9 000: 05 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #7, code = 0x22 (Functional EXT), length = 9 000: 06 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #8, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 01 b5 Data modem services available: Tuple #9, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 1f 00 02 00 b5 Tuple #10, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 1f 00 02 00 b5 Tuple #11, code = 0x1a (Configuration map), length = 5 000: 01 27 80 ff 67 Reg len = 2, config register addr = 0xff80, last config = 0x27 Registers: XXX--XX- Tuple #12, code = 0x1b (Configuration entry), length = 19 000: cf 41 99 79 55 3d 86 46 26 4c aa 60 f8 03 07 f0 010: bc 86 28 Config index = 0xf(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 3.5 x 10mA Max current average over 1 second: 1 x 100mA, ext = 0x46 Max current average over 10 ms: 2 x 100mA Power down supply current: 4.5 x 1mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level, Pulse, Shared IRQs: 4 5 6 7 10 11 12 13 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 17 08 aa 60 f8 02 07 Config index = 0x17 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 1f 08 aa 60 e8 03 07 Config index = 0x1f Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 27 08 aa 60 e8 02 07 Config index = 0x27 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0xff (Terminator), length = 0 Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common
Re: sound and sio problems after newbus changes
On Sun, 2 May 1999, Bruce Evans wrote: > Fast interrupts were broken in early versions of new-bus. Without > fast interrupts, sio interrupt latency is limited by the worst spl > hog in the system. Yes I know that, but I believe this was later fixed. I'm running a kernel compiled today and the sio overflows still happen. Also adding in the sound problems which seem to be caused by missing interrupts, I think we have a bug in the interrupt code after the newbus changes. Blaz Zupan, b...@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: sound and sio problems after newbus changes
>Also, has anybody problems with sio buffer overflows? My machine is a >Pentium 200MMX, which should be able to handle 115.2K on a com port just >fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before >newbus). But now I'm receiving lots of sio overflows, it is as simple as >typing "ATI4" to my Courier, some characters get lost on output. Fast interrupts were broken in early versions of new-bus. Without fast interrupts, sio interrupt latency is limited by the worst spl hog in the system. Bruce To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: sound and sio problems after newbus changes
Yes and yes (I have both the sound problems and the sio overflows) - these started around the time of the newbus commits. Kris On Sat, 1 May 1999, Blaz Zupan wrote: > I also experience the sound problems. Although sound works, it has > problems stopping. For example when I hit stop in x11amp, the sound still > loops for a couple of seconds and then I get the following message on the > console: > > timeout flushing dbuf_out, chan 1 cnt 0xfff9e46c flags 0x01c1 > > This message is being generated in snd_flush() in > /sys/i386/isa/snd/dmabuf.c. Looking at the code, it loops 10 times, each > time waiting for a tsleep() to succeed. There are only two places in > dmabuf.c that wakeup() this tsleep, one is dsp_wr_dmadone(), the second > is in dsp_rd_dmadone(). Both are called from dsp_wrintr(). > > I put in a printf() at the start of dsp_wrintr(). The interrupt gets > called when I start playing music in x11amp. When I stop it, no interrupt > is generated, so dsp_wr_dmadone() is never called, so it never wakes up > the tsleep() in snd_flush(). I really don't know why the interrupt does > not occur (or if it should occur at all), maybe someone more knowledgable > can take over from here Please. Pretty please with sugar on top :) > > Also, has anybody problems with sio buffer overflows? My machine is a > Pentium 200MMX, which should be able to handle 115.2K on a com port just > fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before > newbus). But now I'm receiving lots of sio overflows, it is as simple as > typing "ATI4" to my Courier, some characters get lost on output. > > If I am allowed to take a wild guess, this problem could be linked to the > sound problem. Maybe some interrupts are generally lost or not correctly > handled. > > Blaz Zupan, b...@amis.net, http://www.herbie.amis.net > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
sound and sio problems after newbus changes
I also experience the sound problems. Although sound works, it has problems stopping. For example when I hit stop in x11amp, the sound still loops for a couple of seconds and then I get the following message on the console: timeout flushing dbuf_out, chan 1 cnt 0xfff9e46c flags 0x01c1 This message is being generated in snd_flush() in /sys/i386/isa/snd/dmabuf.c. Looking at the code, it loops 10 times, each time waiting for a tsleep() to succeed. There are only two places in dmabuf.c that wakeup() this tsleep, one is dsp_wr_dmadone(), the second is in dsp_rd_dmadone(). Both are called from dsp_wrintr(). I put in a printf() at the start of dsp_wrintr(). The interrupt gets called when I start playing music in x11amp. When I stop it, no interrupt is generated, so dsp_wr_dmadone() is never called, so it never wakes up the tsleep() in snd_flush(). I really don't know why the interrupt does not occur (or if it should occur at all), maybe someone more knowledgable can take over from here Please. Pretty please with sugar on top :) Also, has anybody problems with sio buffer overflows? My machine is a Pentium 200MMX, which should be able to handle 115.2K on a com port just fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before newbus). But now I'm receiving lots of sio overflows, it is as simple as typing "ATI4" to my Courier, some characters get lost on output. If I am allowed to take a wild guess, this problem could be linked to the sound problem. Maybe some interrupts are generally lost or not correctly handled. Blaz Zupan, b...@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
