On Tue, Apr 01, 2003 at 09:05:16AM -0800, Greg KH wrote:
On Tue, Apr 01, 2003 at 05:24:11PM +0100, Nick Craig-Wood wrote:
I tried 2.5.66 and yes it no longer Oopses on close! I tried it 100
times on USA-49W and USA-49WLC just to be sure.
Good :)
Is it easy to break out a patch
I first noticed this problem in the 2.4.20 kernel. I checked out the
latest bk kernel from bk://linuxusb.bkbits.net/usb-2.4 to test if the
problem was still there.
In a nutshell the problem seems to be that a panic happens if the
keyspan driver is receiving data when the port is closed. I use a
On Thu, Jun 20, 2002 at 12:27:32PM -0700, Greg KH wrote:
On Thu, Jun 20, 2002 at 01:41:25PM +0100, Nick Craig-Wood wrote:
So now the devices are numbered in a completely illogical fashion. It
*seems* to be consistent the numbering scheme from boot to boot but if
you move one thing about
On Mon, Mar 25, 2002 at 01:46:57PM +0100, Georg Acher wrote:
On Mon, Mar 25, 2002 at 12:21:48PM +, Nick Craig-Wood wrote:
The data stream gets corrupted in a very specific way - there are no
bytes added or removed to the serial output but there is one byte
overwritten with null (0x00
;
if (todo 63)
todo = 63;
+ else if (todo 31) /* workaround fix for bad region */
+ todo = 31;
flip = p_priv-out_flip;
--
Nick Craig-Wood
[EMAIL PROTECTED]
___
[EMAIL PROTECTED
On Sun, Dec 30, 2001 at 10:55:19AM +0100, [EMAIL PROTECTED] wrote:
On Sun, 30 Dec 2001, Nick Craig-Wood wrote:
I'm sure this is a known problem - does anyone know how to go about
fixing it?
Please go to the syslog and check whether usb-storage computes identical
UUIDs for both devices
