From: Greg KH <greg@kroah.com>
To: Lu?s Pinto <lmpinto@student.dei.uc.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in visor, since 2.6.10-rc1
Date: Wed, 24 Nov 2004 15:37:59 -0800 [thread overview]
Message-ID: <20041124233756.GC4649@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411182254310.6221@amarok.dei.uc.pt>
On Fri, Nov 19, 2004 at 02:53:42PM +0000, Lu?s Pinto wrote:
>
> This sort of solves part of it. It doesn't oops anymore,
> however, for a 'pilot-xfer -l' (list all databases on palm) or
> a 'pilot-xfer -i xyz.pdb' (install a database on palm) it
> freezes at the middle, and the palm eventually times out. Here
> goes the corresponding dmesg: the first time it didn't do
> nothing (pilot-xfer didn't even start), the second and third
> it freezed.
Please try this patch. It should solve the problem for you. Sorry for
all of the problems with these recent changes.
thanks,
greg k-h
[PATCH] USB visor: Don't count outstanding URBs twice
Incrementing the outstanding_urbs counter twice for the same URB can't
be good. No wonder Simon didn't get far syncing his Palm.
Signed-off-by: Roger Luethi <rl@hellgate.ch>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
diff -Nru a/drivers/usb/serial/visor.c b/drivers/usb/serial/visor.c
--- a/drivers/usb/serial/visor.c 2004-11-24 15:36:25 -08:00
+++ b/drivers/usb/serial/visor.c 2004-11-24 15:36:25 -08:00
@@ -497,7 +497,6 @@
dev_dbg(&port->dev, "write limit hit\n");
return 0;
}
- ++priv->outstanding_urbs;
spin_unlock_irqrestore(&priv->lock, flags);
buffer = kmalloc (count, GFP_ATOMIC);
next prev parent reply other threads:[~2004-11-24 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:28 Oops in visor, since 2.6.10-rc1 Luís Pinto
2004-11-17 23:15 ` Greg KH
2004-11-19 14:53 ` Luís Pinto
2004-11-24 23:37 ` Greg KH [this message]
2004-11-25 19:27 ` Luís Pinto
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=20041124233756.GC4649@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmpinto@student.dei.uc.pt \
/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 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.