From: Florian Lohoff <flo@rfc822.org>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at fs/sysfs/symlink.c:87
Date: Mon, 24 Jan 2005 16:51:00 +0100 [thread overview]
Message-ID: <20050124155100.GA2583@paradigm.rfc822.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
Hi,
while using the bridging code between a tap0 and a real eth1 i got this:
Linux zmgr1.wstk.mediaways.net 2.6.10-zmgr-p3cel #1 Mon Jan 24 16:15:39 CET 2005 i686 GNU/Linux
UP, P3 Celeron, Non-Preempt, Vanilla Kernel
kernel BUG at fs/sysfs/symlink.c:87!
invalid operand: 0000 [#1]
Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc 3c59x bridge tun autofs eepro100 e100 mii i2c_i801 i2c_core uhci_hcd usbcore
CPU: 0
EIP: 0060:[<c017cac6>] Not tainted VLI
EFLAGS: 00010246 (2.6.10-zmgr-p3cel)
EIP is at sysfs_create_link+0x56/0x60
eax: c45ef738 ebx: 00000000 ecx: c709f000 edx: c39b3ec0
esi: c8880878 edi: c7915728 ebp: c79156a0 esp: c4d91e94
ds: 007b es: 007b ss: 0068
Process brctl (pid: 3500, threadinfo=c4d90000 task=c52b25e0)
Stack: c017b8cf c68ba7e4 c8880824 00000000 c887aa57 c45ef738 c7915728 c709f000
c45ef220 c709f000 c79156a0 c45ef220 00000000 c887762d c79156a0 c79156a0
c709f090 00000001 c709f000 c45ef220 ffffffed c4d91f34 c8877c34 c45ef220
Call Trace:
[<c017b8cf>] sysfs_create_file+0x2f/0x50
[<c887aa57>] br_sysfs_addif+0xe7/0x140 [bridge]
[<c887762d>] br_add_if+0xbd/0x160 [bridge]
[<c8877c34>] add_del_if+0x64/0x80 [bridge]
[<c022d564>] dev_ifsioc+0x384/0x3f0
[<c022d7b7>] dev_ioctl+0x1e7/0x260
[<c0269d2c>] inet_ioctl+0x9c/0xb0
[<c02231c9>] sock_ioctl+0xc9/0x240
[<c015bc79>] sys_ioctl+0xc9/0x240
[<c01024a3>] syscall_call+0x7/0xb
Code: 4c 24 04 8b 44 24 18 89 1c 24 89 44 24 08 e8 f2 fe ff ff 89 c1 8b 53 08 ff 42 68 0f 8e 0b 02 00 00 8b 5c 24 0c 89 c8 83 c4 10 c3 <0f> 0b 57 00 f5 59 2c c0 eb be 8b 44 24 04 8b 40 30 89 44 24 04
<7>tap0: no IPv6 routers present
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-24 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 15:51 Florian Lohoff [this message]
2005-01-24 16:08 ` Jörn Engel
2005-01-24 16:28 ` Florian Lohoff
2005-01-24 17:04 ` Florian Lohoff
2005-01-25 11:31 ` Jörn Engel
2005-01-25 20:32 ` Stephen Hemminger
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=20050124155100.GA2583@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®