From: Wakko Warner <wakko@animx.eu.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Date: Wed, 15 Jun 2005 07:31:59 -0400 [thread overview]
Message-ID: <20050615113159.GA10188@animx.eu.org> (raw)
In-Reply-To: <200506150829.52765.oliver@neukum.org>
Oliver Neukum wrote:
> Very well.
>
> > Results (after ifconfig up, ethernet cable was plugged in at the time):
> > Jun 14 20:50:25 gonzales kernel: [80756.691742] kaweth: begin callback
> > Jun 14 20:50:25 gonzales kernel: [80756.691754] kaweth: u->status: 0
> > Jun 14 20:50:25 gonzales kernel: [80756.691759] kaweth: Link state change. kaweth->linkstate: 0 act_state: 2
> > Jun 14 20:50:25 gonzales kernel: [80756.691764] kaweth: netif_carrier_off
>
> OK, that should not happen.
>
> Could you remove the "!" at 'if (!act_state) {' and retest?
> The documentation I got says that it should be there, but who knows
> how accurate it is for all devices.
Ok, I removed the ! and it now says "netif_carrier_on" and still blasting
the messages. I'm unable to ping the other end when configured.
> > Jun 14 20:50:25 gonzales kernel: [80756.691769] kaweth: new link state: 2
> > Jun 14 20:50:25 gonzales kernel: [80756.691776] kaweth: end callback
> >
> > the next thing was:
> > Jun 14 20:50:25 gonzales kernel: [80756.819793] kaweth: begin callback
> > Jun 14 20:50:25 gonzales kernel: [80756.819800] kaweth: u->status: 0
> > Jun 14 20:50:25 gonzales kernel: [80756.819807] kaweth: end callback
> > many times, last occurence:
> > Jun 14 20:50:36 gonzales kernel: [80767.576134] kaweth: begin callback
> > Jun 14 20:50:36 gonzales kernel: [80767.576143] kaweth: u->status: 0
> > Jun 14 20:50:36 gonzales kernel: [80767.576157] kaweth: end callback
> >
> > then I ifconfig down since it was spewing that information:
> > Jun 14 20:50:36 gonzales kernel: [80767.618157] kaweth: begin callback
> > Jun 14 20:50:36 gonzales kernel: [80767.618172] kaweth: u->status: -2
> >
> > I assume it didn't print the end since the status was -2 (not sure what -2 is)
>
> Killing the URB due to ifconfig.
I meant I didn't know the name to number translation.
For the next tests, I think it would be best to remove the 3 printks I added
to show beginning, u->status, and ending. Spews too much stuff =)
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-06-15 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 0:41 Wakko Warner
2005-06-12 1:16 ` Wakko Warner
2005-06-12 7:57 ` Oliver Neukum
2005-06-12 13:05 ` Wakko Warner
2005-06-12 15:22 ` Oliver Neukum
2005-06-15 1:02 ` Wakko Warner
2005-06-15 6:29 ` Oliver Neukum
2005-06-15 11:31 ` Wakko Warner [this message]
2005-06-15 11:30 ` Oliver Neukum
2005-06-15 16:53 ` Wakko Warner
2005-06-15 16:52 ` Oliver Neukum
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=20050615113159.GA10188@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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®