* 2.5.74 X.25+LAPB still kills the kernel
@ 2003-07-11 17:27 Krzysztof Halasa
2003-07-12 5:44 ` David S. Miller
0 siblings, 1 reply; 5+ messages in thread
From: Krzysztof Halasa @ 2003-07-11 17:27 UTC (permalink / raw)
To: netdev
Hi,
No need to actually use X.25+LAPB, it's enough to just compile it in.
Linux version 2.5.74 (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-4))
You do not need Ethernet either, it will oops with just loopback as well.
Serial console dump follows (details available on request in case someone
need them).
gw:/# ip link
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
gw:/# ifconfig
lo Link eUnable to handle kernel paging requestncap:Local Loopb at virtual address 6b6b6b6b
ack
printing eip:
inet addr:127.0c01a0f22
.0.1 Mask:255.0*pde = 00000000
.0.0
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01a0f22>] Not tainted
EFLAGS: 00010202
EIP is at __release_sock+0x22/0x60
eax: 6b6b6b6b ebx: 00000000 ecx: 00000000 edx: c3cd2c44
esi: c3cd2c44 edi: c3cd2c44 ebp: c10b7f00 esp: c10b7ef8
ds: 007b es: 007b ss: 0068
Process ifconfig (pid: 37, threadinfo=c10b6000 task=c10ce060)
Stack: 00000000 c3cd2c88 c10b7f18 c01ee728 c3cd2c44 c3cd2c44 c3ed1d2c c3cdb494
c10b7f40 c01eebf8 c3cd2c44 c3cd2c44 00000000 00000000 00000000 c3cdb494
00000000 c3cdb4b8 c10b7f54 c019e1d6 c3cdb494 c3cdb4b8 c3ced41c c10b7f64
Call Trace:
[<c01ee728>] x25_destroy_socket+0x188/0x1a0
[<c01eebf8>] x25_release+0x38/0xa0
[<c019e1d6>] sock_release+0x56/0x80
[<c019e9a3>] sock_close+0x23/0x40
[<c01432b6>] __fput+0xd6/0xe0
[<c0141cdb>] filp_close+0x3b/0x60
[<c0141d47>] sys_close+0x47/0x60
[<c010ac17>] syscall_call+0x7/0xb
Code: 8b 18 c7 00 00 00 00 00 50 56 ff 96 1c 01 00 00 85 db 5a 89
UP LOOPBACK RUNN<0>Kernel panic: Fatal exception in interrupt
ING MTU:16436 In interrupt handler - not syncing
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
--
Krzysztof Halasa
Network Administrator
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.5.74 X.25+LAPB still kills the kernel
2003-07-11 17:27 2.5.74 X.25+LAPB still kills the kernel Krzysztof Halasa
@ 2003-07-12 5:44 ` David S. Miller
0 siblings, 0 replies; 5+ messages in thread
From: David S. Miller @ 2003-07-12 5:44 UTC (permalink / raw)
To: Krzysztof Halasa; +Cc: netdev
On 11 Jul 2003 19:27:28 +0200
Krzysztof Halasa <khc@pm.waw.pl> wrote:
> No need to actually use X.25+LAPB, it's enough to just compile it in.
Hmmm, if nobody is listening on linux-x25 and neither is
the listed "MAINTAINER" eis@baty.hanse.de we should update
the linux/MAINTAINERS file to be in sync with reality.
Anyways, I'll try to look into this if nobody else does.
Thanks for reporting this to the right place finally, as
a reward your bug will be looked at and hopefully fixed.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.5.74 X.25+LAPB still kills the kernel
2003-07-11 2:08 ` David S. Miller
@ 2003-07-11 12:55 ` Mr. James W. Laferriere
0 siblings, 0 replies; 5+ messages in thread
From: Mr. James W. Laferriere @ 2003-07-11 12:55 UTC (permalink / raw)
To: David S. Miller; +Cc: Krzysztof Halasa, linux-kernel
Hello All , It appears no one is listening there either !-(
JimL
On Thu, 10 Jul 2003, David S. Miller wrote:
> On 11 Jul 2003 00:28:44 +0200
> Krzysztof Halasa <khc@pm.waw.pl> wrote:
> > No need to actually use X.25+LAPB, it's enough to just compile it in.
> If you post this to linux-net@vger.kernel.org or
> netdev@oss.sgi.com, someone might actually read
> your bug report.
> No network developers listen on linux-kernel.
--
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.5.74 X.25+LAPB still kills the kernel
2003-07-10 22:28 Krzysztof Halasa
@ 2003-07-11 2:08 ` David S. Miller
2003-07-11 12:55 ` Mr. James W. Laferriere
0 siblings, 1 reply; 5+ messages in thread
From: David S. Miller @ 2003-07-11 2:08 UTC (permalink / raw)
To: Krzysztof Halasa; +Cc: linux-kernel
On 11 Jul 2003 00:28:44 +0200
Krzysztof Halasa <khc@pm.waw.pl> wrote:
> No need to actually use X.25+LAPB, it's enough to just compile it in.
If you post this to linux-net@vger.kernel.org or
netdev@oss.sgi.com, someone might actually read
your bug report.
No network developers listen on linux-kernel.
^ permalink raw reply [flat|nested] 5+ messages in thread
* 2.5.74 X.25+LAPB still kills the kernel
@ 2003-07-10 22:28 Krzysztof Halasa
2003-07-11 2:08 ` David S. Miller
0 siblings, 1 reply; 5+ messages in thread
From: Krzysztof Halasa @ 2003-07-10 22:28 UTC (permalink / raw)
To: linux-kernel
Hi,
No need to actually use X.25+LAPB, it's enough to just compile it in.
Linux version 2.5.74 (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-4))
You do not need Ethernet either, it will oops with just loopback as well.
Serial console dump follows (details available on request in case someone
need them).
gw:/# ip link
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
gw:/# ifconfig
lo Link eUnable to handle kernel paging requestncap:Local Loopb at virtual address 6b6b6b6b
ack
printing eip:
inet addr:127.0c01a0f22
.0.1 Mask:255.0*pde = 00000000
.0.0
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01a0f22>] Not tainted
EFLAGS: 00010202
EIP is at __release_sock+0x22/0x60
eax: 6b6b6b6b ebx: 00000000 ecx: 00000000 edx: c3cd2c44
esi: c3cd2c44 edi: c3cd2c44 ebp: c10b7f00 esp: c10b7ef8
ds: 007b es: 007b ss: 0068
Process ifconfig (pid: 37, threadinfo=c10b6000 task=c10ce060)
Stack: 00000000 c3cd2c88 c10b7f18 c01ee728 c3cd2c44 c3cd2c44 c3ed1d2c c3cdb494
c10b7f40 c01eebf8 c3cd2c44 c3cd2c44 00000000 00000000 00000000 c3cdb494
00000000 c3cdb4b8 c10b7f54 c019e1d6 c3cdb494 c3cdb4b8 c3ced41c c10b7f64
Call Trace:
[<c01ee728>] x25_destroy_socket+0x188/0x1a0
[<c01eebf8>] x25_release+0x38/0xa0
[<c019e1d6>] sock_release+0x56/0x80
[<c019e9a3>] sock_close+0x23/0x40
[<c01432b6>] __fput+0xd6/0xe0
[<c0141cdb>] filp_close+0x3b/0x60
[<c0141d47>] sys_close+0x47/0x60
[<c010ac17>] syscall_call+0x7/0xb
Code: 8b 18 c7 00 00 00 00 00 50 56 ff 96 1c 01 00 00 85 db 5a 89
UP LOOPBACK RUNN<0>Kernel panic: Fatal exception in interrupt
ING MTU:16436 In interrupt handler - not syncing
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
--
Krzysztof Halasa
Network Administrator
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-07-12 5:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-11 17:27 2.5.74 X.25+LAPB still kills the kernel Krzysztof Halasa
2003-07-12 5:44 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 22:28 Krzysztof Halasa
2003-07-11 2:08 ` David S. Miller
2003-07-11 12:55 ` Mr. James W. Laferriere
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.