From owner-freebsd-bugs  Mon Jan  3 10:46:32 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP id C1C6E14D41
	for <freebsd-bugs@FreeBSD.ORG>; Mon,  3 Jan 2000 10:46:29 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway)
	id DAA04770; Tue, 4 Jan 2000 03:46:24 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master)
	id DAA07877; Tue, 4 Jan 2000 03:46:23 +0900 (JST)
Received: from localhost ([192.168.245.53]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912)
	id DAA26510; Tue, 4 Jan 2000 03:46:21 +0900 (JST)
To: joe@pavilion.net
Cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/15742: Laptop -current panics in in6_ifattach after
 suspend
In-Reply-To: <20000102201557.C60369@florence.pavilion.net>
References: <20000102124814.A24810@florence.pavilion.net>
	<20000103002949O.shin@nd.net.fujitsu.co.jp>
	<20000102201557.C60369@florence.pavilion.net>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000104034655H.shin@nd.net.fujitsu.co.jp>
Date: Tue, 04 Jan 2000 03:46:55 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 35
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > I think following additional patch should fix the problem.
> > Sorry for taking your time again, but could you please try it?
> > I confirmed that in6_control(), which called from if_detach(),
> > don't return error after this patch in my environment.
> 
> Yes, this appears to work very well.  Lots of power on/off's in random
> orders, mixed with physically plug/unplugging the card.

Thanks for your confimation.

> I got the following error messages:
> Jan  2 19:47:44 genius pccardd[46]: ioctl (PIOCSIO): Device not configured
> Jan  2 19:47:44 genius pccardd[46]: ioctl (PIOCSIO): Device not configured
> Jan  2 19:58:27 genius /kernel: ep0: eeprom failed to come ready.
> Jan  2 19:58:28 genius last message repeated 3 times
> Jan  2 19:58:28 genius /kernel: ep0: Unit failed to come ready or product ID unknown! (id 0xffff)
> Jan  2 19:58:28 genius last message repeated 3 times
> Jan  2 19:58:28 genius /kernel: ep0: Unit failed to come ready or product ID unknown! (id 0xffff)
> Jan  2 19:58:27 genius pccardd[46]: driver allocation failed for 3Com Corporation(3C589D): Device not configured
> Jan  2 19:58:27 genius pccardd[46]: driver allocation failed for 3Com Corporation(3C589D): Device not configured
> 
> None of these were unrecoverable from however.  Go ahead an commit it.

Here is my information about pccardd ep attach failures.
(Just a information and no further speculation on it. I am
novice about those things.)

I used to put my ep card into my pc's 2nd pcmcia port.
And usually there was no failure.
After I began to use it on the 1st pcmcia port, I also get several
ep0 attach failure from pccardd, sometime.
And then again I began to put it into my pc's 2nd pcmcia port,
and attach failures seem to stopped.

Yoshinobu Inoue


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message