From owner-freebsd-mobile Wed Nov 12 01:56:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19252 for mobile-outgoing; Wed, 12 Nov 1997 01:56:28 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19246 for ; Wed, 12 Nov 1997 01:56:24 -0800 (PST) (envelope-from guido@gvr.org) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id KAA03052; Wed, 12 Nov 1997 10:26:16 +0100 (MET) From: Guido van Rooij Message-Id: <199711120926.KAA03052@gvr.gvr.org> Subject: Re: sio: probe test 3 failed In-Reply-To: <199711112028.NAA17750@rocky.mt.sri.com> from Nate Williams at "Nov 11, 97 01:28:21 pm" To: nate@mt.sri.com (Nate Williams) Date: Wed, 12 Nov 1997 10:26:15 +0100 (MET) Cc: nate@mt.sri.com, freebsd-mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > Both slots are 'resumed' correctly. > > > Nov 11 20:40:21 mouse /kernel: sio1: probe test 3 failed > > Nov 11 20:40:21 mouse pccardd[41]: driver allocation failed for Nokia Mobile Phones > > Still not sure why this happened, but let's go on. It's not obvious > what 'resource' it can't find when trying to use the card, but I > *suspect* it's the interrupt. test 3 tests to see if an interrupt is present (it should be). > > Nov 11 20:42:02 mouse /kernel: Card inserted, slot 1 > > Nov 11 20:42:08 mouse pccardd[41]: No free configuration for card Intelligent > > Hmm, at this point it *appears* that the driver was allocated, but never > de-allocated after failure. Let me look into that..... > > Looks good to me. > > > > > This needs to be done at boot time (or at least before the first > suspend) for it to have any effect. > Are you sure? Then why is it settable? Furthermore: I got the impresson that setting this to 1 caused the network card to be `ignored' > > > > Nov 11 20:45:34 mouse /kernel: Card removed, slot 1 > > Nov 11 20:45:45 mouse /kernel: Card inserted, slot 1 > > Nov 11 20:45:48 mouse /kernel: ep0: unload > > Nov 11 20:45:48 mouse /kernel: Return IRQ=10 > > Nov 11 20:45:48 mouse /kernel: stray irq 10 > > Nov 11 20:45:48 mouse /kernel: Card disabled, slot 0 > > Nov 11 20:45:48 mouse /kernel: Card disabled, slot 1 > > Fine, no cards to disable at slot 0 since the 'inserted' message never > got around to the pccardd daemon long enough for it to have allocated a > driver for the slot. > > > > > Nov 11 20:45:53 mouse /kernel: resumed from suspended mode (slept 00:00:07) > > Nov 11 20:45:54 mouse /kernel: Card inserted, slot 1 > > Nov 11 20:45:54 mouse /kernel: Card inserted, slot 0 > > Nov 11 20:46:01 mouse /kernel: sio1: probe test 3 failed > > Nov 11 20:46:01 mouse pccardd[41]: driver allocation failed for Nokia Mobile Pho > > nes > > > > I know why this happens. Basically, I need to *FORCE* the system to > think the card was removed at suspend time, and *FORCE* it to think the > card was inserted at resume time. Right now I 'fake' it. Basically, > this is a 'known' bug that I haven't gotten time to fix. It shouldn't > happen very often in any case. > > > Nov 11 20:46:36 mouse /kernel: Card removed, slot 0 > > Nov 11 20:46:38 mouse /kernel: Card inserted, slot 0 > > > > Nov 11 20:46:49 mouse /kernel: ep0: utp/bnc[*UTP*] address 00:60:97:8e:e3:ff > > Yep, that's not a good solution, but it no longer locks up your machine > like suspend/resume used to do. :) :) :) > > [ > Well, in your particular case we still have sio lockups, but that's > another story. > ] Only if the pcic's irq is higher then the drivers it may allocate. -Guido