old-www/HOWTO/Cable-Modem/troubleshooting.html

226 lines
4.8 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="The Cable Modem HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Notes on Specific Hardware"
HREF="hardware.html"><LINK
REL="NEXT"
TITLE="Gnu Free Documentation License"
HREF="appendix.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Cable Modem HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="hardware.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="appendix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="TROUBLESHOOTING"
></A
>5. Troubleshooting</H1
><P
> Q: I get kicked
offline about once every 4 days, for no apparent reason, and get the following error,
or something similar, in the kernel log:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> Feb 20 10:05:12 K7 kernel: CDCEther.c: rx status -110 Feb 20 10:05:12 K7 kernel:
CDCEther.c: no repsonse in BULK IN Feb 20 10:05:12 K7 kernel: CDCEther.c: rx status -110
Feb 20 10:05:12 K7 kernel: CDCEther.c: no repsonse in BULK IN Feb 20 10:05:12 K7 kernel:
CDCEther.c: rx status -110 Feb 20 10:05:12 K7 kernel: CDCEther.c: no repsonse in BULK
IN Feb 20 10:05:12 K7 kernel: CDCEther.c: rx status -110 </PRE
></FONT
></TD
></TR
></TABLE
> </P
><P
> A:
There are a number of reasons this may be happening, and future updates to the CDCEther
driver may solve some of them. At least one user on the Linux-USB-user mailing list
noticed that on at least one occasion data sent to the modem from upstream by the
cable provider has triggered it. Also, the modem itself is very sensitive to power
interruptions and can lose the connection if this occurs. The fix is to run <B
CLASS="COMMAND"
>ifdown ethX</B
>, where <EM
>ethX</EM
> is the Ethernet interface (eth0,
eth1 etc.) to clear out any remaining settings that are hung, then remove the module with
<B
CLASS="COMMAND"
> rmmod CDCEther</B
>, reinsert the CDCEther module and then <B
CLASS="COMMAND"
>ifup
ethX </B
>. A reboot may be necessary if this doesn't fix the problem. If none
of these work you probably have a real service interruption.</P
><P
> Q: I get
the following messages on boot-up; are they errors? </P
><P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> Can't use
SetEthernetMulticastFilters request Mar 2 11:00:52 K7 kernel: CDCEther.c: Ethernet
information found at device configuration. Trying to use it anyway. Mar 2 11:00:52
K7 kernel: CDCEther.c: Imperfect filtering support - need sw hashing </PRE
></FONT
></TD
></TR
></TABLE
> </P
><P
> A: No. The multicast message is pertaining to Multicast support in the kernel,
which is optional and not necessary for the proper functioning of this modem. The message
about 'Ethernet Information' is a design bug in the modem and can be ignored. As for the
'Imperfect filtering support, to quote Brad Hards: </P
><P
><SPAN
CLASS="QUOTE"
>"This is a bit
difficult to explain - I assume that you know what multicasting is - when you join a
multicast group, this can be handled by the networking device so that other multicast
traffic doesn't cause interrupts. That is called 'perfect filtering.' However sometimes
the number of multicast addresses exceeds the number of filters that you have. This
leads to 'imperfect filtering,' which can cut down the number of interrupts, but you
still need to do some work in the networking stack. Then you get to the typical cable
modem implementation, and there is not filtering at all. Every multicast packet goes
to the host to be filtered. This doesn't normally matter though, because the cable
modem is a point to point link."</SPAN
> </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="hardware.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="appendix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Notes on Specific Hardware</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Gnu Free Documentation License</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>