Message-ID: <495DCD18.8060900@rtr.ca>
Date: Fri, 02 Jan 2009 03:15:20 -0500
From: Mark Lord <lkml@rtr.ca>
Organization: Real-Time Remedies Inc.
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: Greg KH <gregkh@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: libusb broken on 2.6.28 x86_64 ?
References: <495DB4AC.50602@rtr.ca> <495DBBC1.7040202@rtr.ca> <20090102072436.GA3444@suse.de> <495DC771.9030103@rtr.ca> <20090102075835.GA3955@suse.de>
In-Reply-To: <20090102075835.GA3955@suse.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1765
Lines: 47

Greg KH wrote:
> On Fri, Jan 02, 2009 at 02:51:13AM -0500, Mark Lord wrote:
>> Greg KH wrote:
>>> On Fri, Jan 02, 2009 at 02:01:21AM -0500, Mark Lord wrote:
>>>> Mark Lord wrote:
>> ..
>>>> Mmm.. broken only for 64-bit userspace, it seems.
>>>>
>>>> I've recompiled the same app against 32-bit libs,
>>>> and it works just fine on that 64-bit system,
>>>> as well as on 32-bit systems.
>>>>
>>>> But not when compiled for pure 64-bit operation on a 64-bit system.
>> ..
>>> Which version of libusb, a new one was just released a few weeks ago
>>> that fixes a lot of problems reported in the older libusb versions, and
>>> made things much faster to boot.  You might want to check it out.
>> ..
>>
>> This is with libusb-0.1-4, which has been working fine with all prior 
>> kernels,
>> including the 2.6.27.xx series.
>>
>> Userspace stuff like this is not supposed to be broken from kernel to 
>> kernel.
> 
> No it shouldn't, I was thinking this was the first time you had tried
> such a thing (64bit userspace apps.)
> 
> If using 2.6.27 works, then we need to fix this.
..

Yup.  I don't really see anything likely in kernel from 2.6.27 to 2.6.28,
other than perhaps the new "poisoning" code.  I wonder if that could be it?

Kinda weird that the device works with libusb the first time it is used,
but then fails on all subsequent runs of the same app, until replugged.

But.. I can run the 32-bit compat app after a 64-bit failure,
and *that* does work.  There's gotta be a useful clue in there somewhere.

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/