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, 17 Nov 2004 15:15:20 -0800 [thread overview]
Message-ID: <20041117231520.GB20701@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411151921140.5912@amarok.dei.uc.pt>
On Mon, Nov 15, 2004 at 07:28:23PM +0000, Lu?s Pinto wrote:
>
> Hi all!
>
> I have been getting a oops in my kernel when trying to sync my
> palm tungsten E, using pilot-xfer version 0.11.8.
>
> The affected kernel versions are all since the 2.6.10-rc1,
> including mm and bk branches.
The following patch should solve this. Let me know if it doesn't.
thanks,
greg k-h
-----------
generic_startup in visor.c was not called for some hardware, resulting
in attempts to access memory that had never been allocated, which in
turn caused the problem several people reported with recent (2.6.10ish)
kernels.
Signed-off-by: Roger Luethi <rl@hellgate.ch>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
--- linux-2.6.10-rc2/drivers/usb/serial/visor.c.orig 2004-11-16 16:03:05.000000000 +0100
+++ linux-2.6.10-rc2/drivers/usb/serial/visor.c 2004-11-16 16:31:24.235249944 +0100
@@ -930,7 +930,7 @@ static int treo_attach (struct usb_seria
if (!((serial->dev->descriptor.idVendor == HANDSPRING_VENDOR_ID) ||
(serial->dev->descriptor.idVendor == KYOCERA_VENDOR_ID)) ||
(serial->num_interrupt_in == 0))
- return 0;
+ goto generic_startup;
dbg("%s", __FUNCTION__);
@@ -957,6 +957,7 @@ static int treo_attach (struct usb_seria
COPY_PORT(serial->port[1], swap_port);
kfree(swap_port);
+generic_startup:
return generic_startup(serial);
}
next prev parent reply other threads:[~2004-11-17 23:19 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 [this message]
2004-11-19 14:53 ` Luís Pinto
2004-11-24 23:37 ` Greg KH
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=20041117231520.GB20701@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox