Date: Sun, 20 Nov 2005 19:52:51 +0100 From: spil oss <spil.oss@googlemail.com> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-current@freebsd.org, Thierry DELHAISE <befree_fr@mac.com>, "M. Warner Losh" <imp@bsdimp.com>, freebsd@psam.se Subject: Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT Message-ID: <5fbf03c20511201052n566858f7m3498db435b4814ca@mail.gmail.com> In-Reply-To: <200511201051.42444.dfr@nlsystems.com> References: <4352E841.6000601@psam.se> <4353F3D5.6060309@psam.se> <20051017.130631.73017921.imp@bsdimp.com> <200511201051.42444.dfr@nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug, Thanks a lot for the reply. This indeed resolved the watchdog timeouts on my 3c575B. Still would be great if this were fixed for non-polling. Now acpi seems to be misbehaving, a fan that used to stop when the CPU < 62C now continuously runs. Spil. On 11/20/05, Doug Rabson <dfr@nlsystems.com> wrote: > On Monday 17 October 2005 20:06, M. Warner Losh wrote: > > : When I start it outside and then connect the card it will detect > > : and configure it correctly. > > > > OK. This is a HUGE clue. One that shouldn't be overlooked :-). > > What it is telling me is that FUNCTION interrupts aren't getting > > through, but STATUS interrupts ARE getting through. I'll have to go > > re-read my two TOPIC data sheets to make sure, but I think that the > > TOPIC chips, especially the older ones, have a number of knobs for > > function interrupts that are not in the standard bridge chipset. > > > > Please refresh my recollection: Did this used to work with 5.4? > > IIRC, I did some work to fix o2 micro hangs that disabled the > > function interrupts during card insertion by routing them via IRQ 1 > > (which the o2micro actually doesn't route, so they just disappear). > > Maybe that work around had bad effects for the TOPIC95B that you > > have? > > I get this (xl0 watchdog etc) with my little Sony picturebook, trying to > run current. I'm getting around it using polling for now. I've attached > a verbose dmesg from 7.0 here. This combination works great with 5.4 > but getting a dmesg for that configuration would be a bit trickier. > > As far as I can see from vmstat, some interrupts are getting through to > irq9 but not the ones that were intended for xl0. > > $ vmstat -i > interrupt total rate > irq0: clk 1145039 999 > irq1: atkbd0 2 0 > irq8: rtc 146591 127 > irq9: cbb0 fwohci* 194 0 > irq13: npx0 1 0 > irq14: ata0 3980 3 > Total 1295807 1130 > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5fbf03c20511201052n566858f7m3498db435b4814ca>