Date: Thu, 5 Jul 2001 19:38:00 -0400 (EDT) From: "H. Wade Minter" <minter@lunenburg.org> To: Kevin Oberman <oberman@es.net> Cc: Scott Mitchell <scott.mitchell@mail.com>, <freebsd-mobile@FreeBSD.ORG> Subject: Re: 4.3-R lockup with Xircom RealPort REM56 (non-cardbus) Message-ID: <20010705193744.C9215-100000@ashburn.skiltech.com> In-Reply-To: <200107052335.f65NZ5c03551@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
What can I do to check and find a good iomem value? --Wade On Thu, 5 Jul 2001, Kevin Oberman wrote: > > Date: Thu, 5 Jul 2001 19:24:26 -0400 (EDT) > > From: "H. Wade Minter" <minter@lunenburg.org> > > Sender: owner-freebsd-mobile@FreeBSD.ORG > > > > Ok, I've assigned IRQ 10 to the PCMCIA controller. "dmesg | grep -i irq" > > and "vmstat -i" show 10 as free. > > > > So the system boots up fine with or without the card in it. When I insert > > the card or it gets detected on bootup, the system beeps and prints out > > "pccard: card inserted, slot 0" to the console. > > > > It then prints out some pccardd messages that it has matched CEM56, which > > looks right. > > > > It then prints out: > > xe0 at port 0x2e8-0x2ef iomem 0xd0000-0xd0fff irq 3 slot 0 on pccard0 > > > > and hangs the system. If I go to eject the card, the system comes back > > with: > > > > kernel trap 19 with interrupts disabled. > > > > Then prints out a fatal trap and tries to reboot. > > > > Ideas? > > Yes. You have assigned a free IRQ to the pcic and it's now working > fine. > > The next step is the interrupt of the Xircom card, itself. > > Under the current pccard software the IRQs are assigned from a list in > the pccard.conf file. You need to look for another free IRQ to assign > to the xe device. > > The best thing to do is to scan the outputs of dmesg and vmstat -i and > see what IRQs are in use. IRQ 2 and 13 are always unavailable. > > Then edit/create /etc/pccard.conf with a line reading > irq 5 9 (replace the numbers with the free IRQs you have found.) > > This should do the trick, although it is possible that your laptop > will need the iomem range adjusted, too. > > This is all a real pain, but once you get it, you won't have to worry > about it until V5.0 comes out which will replace the whole mess with > something that works far better (I hope). > > Good luck! > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010705193744.C9215-100000>