Problems with current and sio?
I just upgraded one of my linux boxes to FreeBSD 4.0-CURRENT since I can kind of run the one application that was keeping me on linux (vmware). Well I am having one hell of a time though. I use this box as a NAT box for my local lan, and for some reason I am getting massive errors like the following. sio0: 1 more silo overflow (total 1) sio0: 1 more silo overflow (total 2) sio0: 1 more silo overflow (total 3) sio0: 1 more silo overflow (total 4) sio0: 1 more silo overflow (total 5) sio0: 1 more silo overflow (total 6) sio0: 1 more silo overflow (total 7) This brings my massive 28.8 connection down to about 1.0k second if I'm lucky (these happen pretty frequently). I was not having this problem with this serial port under linux, so I'm at a loss to as what this could be. The kernel reports sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A This is on a Dell Dimension XPS-T450 which is a P3-450 with 256 megs of ram. I have an Ati All-in-Wonder Pro video card, and a Dec 21041 Ethernet card in this box. There is also a SB16 in there as well. But I can't see how any of those could be causing the problem. Also this happens with the box sitting completely idle. I can boot the box and leave it sitting at the login prompt, and try and surf from one of my other boxes and these messages just start popping up as data moves through the modem. Just for grins to make sure my cable and modem were all right, I plugged them into my laptop which is running 3.4-STABLE and it worked great. No errors or anything. Unfortunately I can't leave my laptop as my gateway (nice $6k paper weight). Thanks. Greg -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ES1371 problems..
I have a SoundBlaster PCI128 (ES1371) in my computer, and for the life of me I have the weirdest problem. Of course I don't have the problem if I put a ISA SB16 in place of it. So it's gotta be ES1371 related. Okay, the ES1371 works great with all but one application (that I have found so far). If I try and use play (a wrapper shipped with sox), it works one time and than no more. But I am able to work fine using mpg123, xmms for example. All three of these use the OSS interface to the sound device. I have begun looking at the applications trying to determine which one does something differently, and so far have made little headway at all on this. As I said this works fine if I put a SB16 ISA card back in the computer instead of the ES1371. So it's related to something the ES1371 driver isn't doing. The weird part is that it plays the wav file once. Okay while I was writing this I have found a more interesting note. This appears to only happen when I'm trying to play a MONO file. It plays stereo files just fine (these are .wav files btw). Now what doesn't make sense about this is I have tried forcing mono on mpg123 and xmms and they both still work fine. So if anyone has any ideas, please shoot them to me. Otherwise I will continue my quest to figure out why this is broke. Greg -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
I even have a worse problem. I tried this on my system (a sony vaio PCG-XG18) which has a mini-docking station on the back of it (which allows you access to a third pcmcia slot, and a whole slew of other video goodies/serial ports/etc.). The problem is if the mini docking station isn't there, all the parts/chips/controllers are internal to the laptop, so it still sees them. The cardbus code sees the second controller (which drives the third slot) and than gracefully pukes all over it's self. So unless I have the mini docking station plugged in it doesn't work. But if it is, I can use my xircom rbem56g-100 and a linksys cardbus card just fine. I do however lose the ability to use my wavelan card and my two other pcmcia cards (non cardbus). I can't wait until all these issues are resolved (I really don't wanna run Linux again). This is just a FYI. Greg * Johny Mattsson (EPA) ([EMAIL PROTECTED]) [010323 07:25]: > >>My suggestion? Chop out the power management stuff in xl_attach() >>and see what happens. > >Okay, did that. Effect: got rid of the D0/D6 printout, and instead >got the following two once I sent something on the interface: > cstsevent occures, 0x3410 > pwrevent occures, 0x3410 > >This does not seem to have any adverse effects though. >Perhaps worth mentioning is that I get these even if I just reboot >from fbsd to fbsd, not only when I do windoze->fbsd. > >I also removed the "device pccard" config option, and as a result >lost support for the modem card, but in return this fixed the >watchdog timeouts, and the lan card works quite well now. >I guess I'll have to keep a backup kernel with the old pcic compiled >in if I want to use the modem... for now I'm very happy to have a >working lan card! > >Thanks a whole lot guys, I really appreciate it! > >/Johny > >PS. Sorry if this is still in HTML format, it shouldn't be, but I'm >stuck with outlook and it just doesn't seem to want to take a hint. -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
This is the same problem I am having with a Soundblaster 16 PCI on
4.2-STABLE. I found a work around for it. It appears that there is
something that is being un-initialized by the FreeBSD es1371 driver that
other OS's do set. I have built a linux boot floppy, boot it, modprobe
the linux es1371 driver, and than reboot into FreeBSD and the problem is
gone. And until I power off the machine, the card works fine.
I have brought this up several times on the freebsd-multimedia list, but
have gone un-noticed each time.
Anyway, I have found a lame work around, until it is fixed properly.
Greg
* The Hermit Hacker ([EMAIL PROTECTED]) [010114 21:33]:
>
> yup, just confirmed ... it does it with splay as well ...
>
>
> On Sun, 14 Jan 2001, The Hermit Hacker wrote:
>
> > On Sun, 14 Jan 2001, Cameron Grant wrote:
> >
> > > > > If this is a known problem, I'll stop for now and watch out for fixes.
> > > > > If it's not the expected behaviour from the PCM driver though, can
> > > > > anyone advise?
> > > >
> > > > Okay, just checked and it appears tha htis is the same error that I'm
> > > > seeing on mine, as reported yesterday ... not sure if its known or not,
> > > > but its not "just you" ...
> > >
> > > are either of you using esound or xmms? if so, i know the cause of this and
> > > it will be fixed shortly, once my primary development box recovers from
> > > killing its cpu.
> > >
> > > if not, i'll try to reproduce this.
> >
> > for me, I tried using splay ... but, not sure how old my compile was, so
> > am just installing a new copy and will report back ...
> >
> >
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
> Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> Systems Administrator @ hub.org
> primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Greg Rumple
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Poweroff problem with IBM ThinkPad T21 (ACPI?)
I just put 5.0-DP2 on my IBM ThinkPad T21 (which I can finaly use, 4.x was pretty bad since only one of the two pcmcia slots worked, and numerous other problems, forcing me to use windows) and have been very very happy with it. ACPI works nicely on the laptop, and everything seems to be pretty happy (I did update it to current once and had to reinstall as the stability was pretty bad, so I took it back to DP2 which is working well). I only have 1 problem that I have been completely unable to solve. If I power off the laptop (shutdown -p now, or halt -p), approximately 60-63 minutes later the laptop will power back on (I live in Los Angeles, and so it powers back on in my laptop bag during my commute home, so when I get home it's about to overheat) all by it's self. This is pretty odd. I have found no way to make it not do this. Does anyone have any ideas? I have verified in the bios that nothing is turned on that would cause this, nor did this happen under Windows XP. Thanks in advance, and great work. I'm really happy that I can finally use FreeBSD on my laptop as well as my desktops/servers. Greg -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
Here's mine. I purposely disabled the lid_switch_state and tried disabling the power_button_state thinking that might solve the problem but to no avail. hw.acpi.power_button_state: NONE hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3182 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 98 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 * Nate Lawson ([EMAIL PROTECTED]) [021205 10:40]: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? > > -Nate > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
