mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Tue, 14 Jun 2005 21:02:39 -0400	[thread overview]
Message-ID: <20050615010238.GA9215@animx.eu.org> (raw)
In-Reply-To: <200506121722.09813.oliver@neukum.org>

Here's my modified int_callback:
static void int_callback(struct urb *u, struct pt_regs *regs)
{
        struct kaweth_device *kaweth = u->context;
        int act_state;

printk(KERN_INFO "kaweth: begin callback\n");
printk(KERN_INFO "kaweth: u->status: %d\n", u->status);
        switch (u->status) {
        case 0:                 /* success */
                break;
        case -ECONNRESET:       /* unlink */
        case -ENOENT:   
        case -ESHUTDOWN:
                return;
        /* -EPIPE:  should clear the halt */
        default:                /* error */
                goto resubmit;
        }

        /* we check the link state to report changes */
        if (kaweth->linkstate != (act_state = ( kaweth->intbuffer[STATE_OFFSET]
printk(KERN_INFO "kaweth: Link state change.  kaweth->linkstate: %d act_state:
        kaweth->linkstate, act_state);
                if (!act_state) {
printk(KERN_INFO "kaweth: netif_carrier_on\n");
                        netif_carrier_on(kaweth->net);
                } else {
printk(KERN_INFO "kaweth: netif_carrier_off\n");
                        netif_carrier_off(kaweth->net);
                }

                kaweth->linkstate = act_state;
printk(KERN_INFO "kaweth: new link state: %d\n", act_state);
        }
resubmit:
        kaweth_resubmit_int_urb(kaweth, GFP_ATOMIC);
printk(KERN_INFO "kaweth: end callback\n");
}

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
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)

I'm working off a different ethernet card to stay on line while I debug.
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-06-15  0:46 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 [this message]
2005-06-15  6:29         ` Oliver Neukum
2005-06-15 11:31           ` Wakko Warner
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=20050615010238.GA9215@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®