|
Home > Archive > alt.os.linux > October 2002 > Kernel null pointer causing USB ADSL to die..?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Kernel null pointer causing USB ADSL to die..?
|
|
| Shane 2002-10-02, 12:50 pm |
| Hi all,
I have a Dlink DSL200 USB ADSL modem running under RH7.3, stock kernel. In
the last few days I have been getting the following message in
/var/log/messages. It is causing the ADSL to die, and only a reboot seems to
correct it. "lsof /proc/bus/usb" shows nothing using it, but I still cannot
unmount it. It happens anywhere between 2 minutes and 30 minutes of getting
it up and running. I hope someone can help!
Thanks in advance,
Shane
Oct 1 16:31:41 titanium gShield.rc[1843]: Allowing all traceroutes
Oct 1 16:31:42 titanium gShield.rc[1843]: httpd publically accessible
Oct 1 16:31:42 titanium gShield.rc[1843]: SSH daemon publically accessible
Oct 1 16:35:22 titanium pppd[1824]: Modem hangup
Oct 1 16:35:23 titanium pppd[1824]: Connection terminated.
Oct 1 16:35:23 titanium pppd[1824]: Connect time 3.9 minutes.
Oct 1 16:35:23 titanium pppd[1824]: Sent 161833 bytes, received 5592934
bytes.
Oct 1 16:35:23 titanium kernel: printing eip:
Oct 1 16:35:23 titanium kernel: Oops: 0000
Oct 1 16:35:23 titanium kernel: ipt_TOS ipt_MASQUERADE ip_nat_irc
ip_conntrack_
irc ipt_state ipt_REJECT ipt_LO
Oct 1 16:35:23 titanium kernel: CPU: 0
Oct 1 16:35:23 titanium kernel: EIP: 0010:[<e489264d>] Tainted: PF
Oct 1 16:35:23 titanium /etc/hotplug/net.agent: NET unregister event not
suppor
ted
Oct 1 16:35:24 titanium kernel: EFLAGS: 00010246
Oct 1 16:35:24 titanium kernel:
Oct 1 16:35:24 titanium kernel: EIP is at usb_claim_bandwidth_R0846f21a
[usbcor
e] 0xd (2.4.18-3)
Oct 1 16:35:24 titanium kernel: eax: df20821c ebx: 00000023 ecx:
00000000
edx: 00000001
Oct 1 16:35:24 titanium pppd[1824]: Exit.
Oct 1 16:35:24 titanium kernel: esi: 00000000 edi: 00000023 ebp:
00000000
esp: df353ed4
Oct 1 16:35:24 titanium kernel: ds: 0018 es: 0018 ss: 0018
Oct 1 16:35:24 titanium kernel: Process pppoeci (pid: 1811,
stackpage=df353000)
Oct 1 16:35:24 titanium kernel: Stack: df20821c e48a75c5 00000000 df20821c
0000
0023 00000001 00000202 df757960
Oct 1 16:35:24 titanium kernel: e3f90560 0000000a df208200 00001180
e397
69c0 e4893164 df20821c e4898488
Oct 1 16:35:24 titanium kernel: df20821c e39769c0 00008800 00000000
0000
0002 0808ca20 00001180 00000000
Oct 1 16:35:24 titanium kernel: Call Trace: [<e48a75c5>] uhci_submit_urb
[usb-u
hci] 0x2f5
Oct 1 16:35:24 titanium kernel: [<e4893164>] usb_submit_urb_R51dc8d4f
[usbcore]
0x24
Oct 1 16:35:24 titanium kernel: [<e4898488>] proc_submiturb [usbcore] 0x568
Oct 1 16:35:24 titanium kernel: [<e4898e07>] usbdev_ioctl [usbcore] 0x227
Oct 1 16:35:24 titanium kernel: [<c0146314>] file_ioctl [kernel] 0x154
Oct 1 16:35:24 titanium kernel: [<c0146522>] sys_ioctl [kernel] 0x1f2
Oct 1 16:35:24 titanium kernel: [<c0109e2c>] do_IRQ [kernel] 0x9c
Oct 1 16:35:24 titanium kernel: [<c0108923>] system_call [kernel] 0x33
Oct 1 16:35:24 titanium kernel:
Oct 1 16:35:24 titanium kernel:
Oct 1 16:35:24 titanium kernel: Code: 8b 81 bc 00 00 00 01 58 2c 85 d2 74
0b 8b
81 bc 00 00 00 ff
Cheers,
Shane.
| |
| Richard Adams 2002-10-02, 12:51 pm |
| In article <3d9a2194$1@duster.adelaide.on.net>, "Shane"
<shanel@internode.on.net> wrote:
> Hi all,
> I have a Dlink DSL200 USB ADSL modem running under RH7.3, stock kernel.
> In the last few days I have been getting the following message in
> /var/log/messages. It is causing the ADSL to die, and only a reboot
> seems to correct it. "lsof /proc/bus/usb" shows nothing using it, but I
> still cannot unmount it. It happens anywhere between 2 minutes and 30
> minutes of getting it up and running. I hope someone can help! Thanks in
> advance,
> Shane
It looks like iptables is causing the problem, or too put it another way,
iptables is doing what it is told to do by you, (via iptable rules) and
your dlink dsl200 is causing the kernel to panic.
Try tuning off iptables to see if the problem goes away.
In bioth cases what you are experiancing "should not happen", considering
that is that you use a stock kernel.
>
> Oct 1 16:31:41 titanium gShield.rc[1843]: Allowing all traceroutes Oct
> 1 16:31:42 titanium gShield.rc[1843]: httpd publically accessible Oct 1
> 16:31:42 titanium gShield.rc[1843]: SSH daemon publically accessible Oct
> 1 16:35:22 titanium pppd[1824]: Modem hangup Oct 1 16:35:23 titanium
> pppd[1824]: Connection terminated. Oct 1 16:35:23 titanium pppd[1824]:
> Connect time 3.9 minutes. Oct 1 16:35:23 titanium pppd[1824]: Sent
> 161833 bytes, received 5592934 bytes.
> Oct 1 16:35:23 titanium kernel: printing eip: Oct 1 16:35:23 titanium
> kernel: Oops: 0000 Oct 1 16:35:23 titanium kernel: ipt_TOS
> ipt_MASQUERADE ip_nat_irc ip_conntrack_
> irc ipt_state ipt_REJECT ipt_LO
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^
It looks to me as if that would be a possable cause.
Read /usr/src/linux/README, the part;
IF SOMETHING GOES WRONG:
It explains what to do in these sort of situations.
> Oct 1 16:35:23 titanium kernel: CPU: 0 Oct 1 16:35:23 titanium
> kernel: EIP: 0010:[<e489264d>] Tainted: PF Oct 1 16:35:23
> titanium /etc/hotplug/net.agent: NET unregister event not suppor
> ted
> Oct 1 16:35:24 titanium kernel: EFLAGS: 00010246 Oct 1 16:35:24
> titanium kernel:
> Oct 1 16:35:24 titanium kernel: EIP is at usb_claim_bandwidth_R0846f21a
> [usbcor
> e] 0xd (2.4.18-3)
> Oct 1 16:35:24 titanium kernel: eax: df20821c ebx: 00000023 ecx:
> 00000000
> edx: 00000001
> Oct 1 16:35:24 titanium pppd[1824]: Exit. Oct 1 16:35:24 titanium
> kernel: esi: 00000000 edi: 00000023 ebp: 00000000
> esp: df353ed4
> Oct 1 16:35:24 titanium kernel: ds: 0018 es: 0018 ss: 0018 Oct 1
> 16:35:24 titanium kernel: Process pppoeci (pid: 1811,
> stackpage=df353000)
> Oct 1 16:35:24 titanium kernel: Stack: df20821c e48a75c5 00000000
> df20821c 0000
> 0023 00000001 00000202 df757960
> Oct 1 16:35:24 titanium kernel: e3f90560 0000000a df208200
> 00001180 e397
> 69c0 e4893164 df20821c e4898488
> Oct 1 16:35:24 titanium kernel: df20821c e39769c0 00008800
> 00000000 0000
> 0002 0808ca20 00001180 00000000
> Oct 1 16:35:24 titanium kernel: Call Trace: [<e48a75c5>]
> uhci_submit_urb [usb-u
> hci] 0x2f5
> Oct 1 16:35:24 titanium kernel: [<e4893164>] usb_submit_urb_R51dc8d4f
> [usbcore]
> 0x24
> Oct 1 16:35:24 titanium kernel: [<e4898488>] proc_submiturb [usbcore]
> 0x568 Oct 1 16:35:24 titanium kernel: [<e4898e07>] usbdev_ioctl
> [usbcore] 0x227 Oct 1 16:35:24 titanium kernel: [<c0146314>] file_ioctl
> [kernel] 0x154 Oct 1 16:35:24 titanium kernel: [<c0146522>] sys_ioctl
> [kernel] 0x1f2 Oct 1 16:35:24 titanium kernel: [<c0109e2c>] do_IRQ
> [kernel] 0x9c Oct 1 16:35:24 titanium kernel: [<c0108923>] system_call
> [kernel] 0x33 Oct 1 16:35:24 titanium kernel:
> Oct 1 16:35:24 titanium kernel:
> Oct 1 16:35:24 titanium kernel: Code: 8b 81 bc 00 00 00 01 58 2c 85 d2
> 74 0b 8b
> 81 bc 00 00 00 ff
>
> Cheers,
> Shane.
>
>
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
|
|
|
|
|