Date: Tue, 21 Jul 1998 14:16:50 -0700 From: Mike Smith <mike@smith.net.au> To: Brian Somers <brian@Awfulhak.org> Cc: Bruce Evans <bde@zeta.org.au>, freebsd-current@FreeBSD.ORG, jak@cetlink.net, freebsd-mobile@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <199807212116.OAA01981@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 21 Jul 1998 21:10:45 BST." <199807212010.VAA20743@awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >The laptop: > > > > > >: FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 > > >: brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF > > >: Timecounter "i8254" frequency 1193182 Hz cost 1296 ns > > >: CPU: Cyrix GXm (17.09-MHz 586-class CPU) This isn't actually a Cyrix "MediaGX" processor, is it? If so *all* bets on its behaviour are off. The MediaGX emulates some of the system hardware using SMI traps, and the quality and accuracy of this emulation seems to vary widely with BIOS implementor. > Additionally, the apm controller is misbehaving - so all this may be > a result of that. It's one of those nasty pci-come-isa jobs (VLSI > 82C146, 5 mem & 2 i/o windows), and no matter what I do, I can't get > it to notice the pccard's irq. Don't confuse APM (which is a software interface to the BIOS) and the PCCARD controller (which is hardware). Completely different things. What do you mean by "notice the pccard's IRQ"? Have you verified that the controller in question is actually an 82C146, or just something that behaves something like it? The PCCARD controller is polled as well as handled by an interrupt, but that doesn't sound like your problem. > I've tried manually assigning irq 12 (rather than 3) to the > controller by tweaking pccard.c but it makes no difference. The card > is functional in my old laptop and has a hard-coded irq 10 in > pccard.conf - and I know irq 12 is free for the controller (I'm not > sure about irq 3 'cos there's a built-in modem that I haven't been > able to find i/o address-wise yet) :-/ > > I know it's an irq problem because if I ``ping -c2'', I get > everything back in one go at the end. Any other ping results in > nothing. arps work and dns (udp?) works very slowly. This isn't related to the controller IRQ, but rather the card IRQ. It sounds like either the controller is not correctly generating the requested IRQ, or the IRQ that you're assigning to the card is in use by something else in the system. Try moving your card IRQ's around. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807212116.OAA01981>