public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: 2.6.0-test5 usbserial oops
Date: Thu, 11 Sep 2003 10:57:56 -0700	[thread overview]
Message-ID: <20030911175755.GA13334@kroah.com> (raw)
In-Reply-To: <3F60B4AB.7060109@kmlinux.fjfi.cvut.cz>

On Thu, Sep 11, 2003 at 07:45:15PM +0200, Jindrich Makovicka wrote:
> Hello,
> 
> I have a similar problem, here is the syslog with debug=1 set for visor 
> and usbserial. This occured after using a ppp connection. I am running 
> 2.4.0test5 with v4l2 patch from http://bytesex.org/v4l/.

Hm, can you try the following patch and let me know if it fixes the
problem for you?

thanks,

greg k-h

--- a/drivers/usb/serial/usb-serial.c	Wed Sep  3 08:47:22 2003
+++ b/drivers/usb/serial/usb-serial.c	Thu Sep 11 11:01:55 2003
@@ -871,8 +871,10 @@
 
 	/* the ports are cleaned up and released in port_release() */
 	for (i = 0; i < serial->num_ports; ++i)
-		if (serial->port[i]->dev.parent != NULL)
+		if (serial->port[i]->dev.parent != NULL) {
 			device_unregister(&serial->port[i]->dev);
+			serial->port[i] = NULL;
+		}
 
 	/* If this is a "fake" port, we have to clean it up here, as it will
 	 * not get cleaned up in port_release() as it was never registered with

       reply	other threads:[~2003-09-11 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F60B4AB.7060109@kmlinux.fjfi.cvut.cz>
2003-09-11 17:57 ` Greg KH [this message]
2003-09-11 22:32   ` Re: 2.6.0-test5 usbserial oops Greg Norris
2003-09-18  4:09     ` Greg KH
2003-09-19  1:39       ` Greg Norris
2003-09-11  3:30 Greg Norris
2003-09-11  4:46 ` Greg KH
2003-09-12 21:20   ` Cliff White
2003-10-11 19:35 ` 2.6.0-test7 " Greg Norris
2003-10-23  2:43   ` Greg Norris

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=20030911175755.GA13334@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=makovick@kmlinux.fjfi.cvut.cz \
    /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