Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 Jan 2000 02:30:50 +0900
From:      Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
To:        joe@FreeBSD.ORG
Cc:        joe@pavilion.net, freebsd-bugs@FreeBSD.ORG
Subject:   Re: kern/15742: Laptop -current panics in in6_ifattach after suspend
Message-ID:  <20000102023050X.shin@nd.net.fujitsu.co.jp>
In-Reply-To: <20000101163112Y.shin@nd.net.fujitsu.co.jp>
References:  <200001010339.TAA16831@freefall.freebsd.org> <20000101163112Y.shin@nd.net.fujitsu.co.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
> > I don't believe that this has fixed the problem.  I've just got 
> > a panic with exactly the same backtrace on a kernel that I've confirmed
> > has this patch in.                             
> 
> Please let me know the name of the LAN card driver, you are
> using.

Sorry for my stupid question. It was already written in your
previous bug report.

I also have 3Com Etherlink III 3C589D, and I tried several
tests on my FreeBSD current PC.

Unfortunately my PC (panasonic Let's Note AL-N4) can not do
software suspend(apm -Z or zzz) in FreeBSD current
environment, so I tried

 pccardc power 0 0
 (my ep0 power down)

Then my ep0 disappeared,
and then

 pccardc power 0 1

Then my ep0 appeared again.
And there was no problem.

I think essentialy same thing will happen on ep when
suspend/resume is done.  (By the way, at least in my
environment, dynamic ep0 plugging/unplugging is not seems to
be supported.)

I also reviewed several code part, and it seems to me that
panicing at in6_ifattach()(line 384 of in6_ifattach.c) after
suspend/resume is very not likely to happen for any interface
which calls if_detach() at suspend.
(If sys/net/if.c version is 1.82)

And if some interface don't call if_detach at suspend, then it
will panic at any ifconfig related operation. (e.g. some
problem should also happen on a kernel where INET6 is not
defined.)

Is your current problem exactly same as before?, and happens
only on INET6 defined kernel?
I am afraid if it is some other new problem.

Yoshinobu Inoue


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000102023050X.shin>