From: cagri coltekin <cagri@ripe.net>
To: Herbert Xu <herbert.xu@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pekkas@netcore.fi
Subject: Re: PROBLEM: kernel BUG at net/ipv6/ip6_output.c:718
Date: Thu, 28 Sep 2006 10:40:18 +0200 [thread overview]
Message-ID: <20060928084018.GA15141@ripe.net> (raw)
In-Reply-To: <20060928003829.GA8952@gondor.apana.org.au>
On Thu, Sep 28, 2006 at 10:38:29AM +1000, Herbert Xu wrote:
> On Tue, Sep 26, 2006 at 01:21:22PM +0200, cagri coltekin wrote:
> >
> > ------------------------------------------------------------------------------
> > [ 1395.890897] ------------[ cut here ]------------
> > [ 1395.946093] kernel BUG at net/ipv6/ip6_output.c:940!
>
> Could you go further back in the logs to see if there was a
> warning message? Either that or turn the WARN_ON into a BUG.
No. Bug is the first after boot:
[ 34.042841] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 44.110469] eth0: no IPv6 routers present
[ 80.968012] process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
[ 81.452248] process `named' is using obsolete setsockopt SO_BSDCOMPAT
[ 110.559560] process `lwresd' is using obsolete setsockopt SO_BSDCOMPAT
[ 140.568831] process `named' is using obsolete setsockopt SO_BSDCOMPAT
[ 1395.890897] ------------[ cut here ]------------
[ 1395.946093] kernel BUG at net/ipv6/ip6_output.c:940!
[ 1396.005441] invalid opcode: 0000 [#1]
Cheers,
--
cagri
next prev parent reply other threads:[~2006-09-28 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 14:23 PROBLEM: kernel BUG at net/ipv6/ip6_output.c:718 cagri coltekin
2006-08-28 0:16 ` Herbert Xu
2006-08-28 0:49 ` cagri coltekin
2006-08-29 8:28 ` Herbert Xu
2006-08-31 15:12 ` cagri coltekin
2006-09-01 7:05 ` Herbert Xu
2006-09-01 16:22 ` cagri coltekin
2006-09-25 12:15 ` Herbert Xu
2006-09-26 11:21 ` cagri coltekin
2006-09-28 0:38 ` Herbert Xu
2006-09-28 8:40 ` cagri coltekin [this message]
2006-10-03 5:49 ` Herbert Xu
2006-10-03 6:28 ` Herbert Xu
2006-10-03 14:57 ` cagri coltekin
2006-10-03 13:56 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060928084018.GA15141@ripe.net \
--to=cagri@ripe.net \
--cc=davem@davemloft.net \
--cc=herbert.xu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.