From owner-freebsd-mobile Fri Jan 30 13:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22874 for freebsd-mobile-outgoing; Fri, 30 Jan 1998 13:21:43 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from keywest.ird.rl.af.mil (KEYWEST.IRD.RL.AF.MIL [128.132.193.224]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA22776 for ; Fri, 30 Jan 1998 13:21:33 -0800 (PST) (envelope-from goeringerm@keywest.ird.rl.af.mil) Received: by keywest.ird.rl.af.mil with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BD2D9C.1B79B0F0@keywest.ird.rl.af.mil>; Fri, 30 Jan 1998 16:28:33 -0500 Message-ID: From: "Goeringer, Michael" To: "'Sean J. Schluntz'" Cc: "'freebsd-mobile@freebsd.org'" Subject: RE: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop) Date: Fri, 30 Jan 1998 16:28:31 -0500 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-mobile" For what it's worth, ep1 and ep0 have nothing to do with slot 0 and 1... I guess you could have two network cards in and then each would require thier own entry. In my example I make the printers poll and was using IRQ 7 for the card...is this what you did? Michael G. >---------- >From: Sean J. Schluntz[SMTP:schluntz@clicknet.com] >Sent: Friday, January 30, 1998 4:05 PM >To: freebsd-questions@FreeBSD.ORG >Cc: freebsd-mobile@FreeBSD.ORG >Subject: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop) > >Ok, I'm in for it now. I'm still trying to get my 3Com 3C589D PCCard >running and I rebuild the kernel with ep1 insted of ep0 and moved the >pccard.conf to ep1 and when I incert the card I get Slot 1, unfielded >interrupt 0 repeated in an unbreakable look (hard shutdown is only >option.) I rebuild the kernel and put everything back and I'm still >getting it! > >What can I do? > >-Sean >