Bug#596468: linux-image-2.6.32-5-openvz-amd64: Keyspan USA-49WG USB-Serial 4th Port Doesn't Work
- To: Moritz Mühlenhoff <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Bug#596468: linux-image-2.6.32-5-openvz-amd64: Keyspan USA-49WG USB-Serial 4th Port Doesn't Work
- From: Steaphan Greene <email@example.com>
- Date: Sat, 30 Apr 2011 21:49:31 -0400
- Message-id: <[🔎] 4DBCBC2B.firstname.lastname@example.org>
- Reply-to: Steaphan Greene <email@example.com>, firstname.lastname@example.org
- In-reply-to: <20110423194123.GA5687@pisco.westfalen.local>
- References: <email@example.com> <20101226114626.GA5463@galadriel.inutil.org> <4D1AF799.firstname.lastname@example.org> <1293631853.2928.116.camel@localhost> <4D1B8678.email@example.com> <1293658530.3028.9.camel@localhost> <20110423194123.GA5687@pisco.westfalen.local>
On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote:
> On Wed, Dec 29, 2010 at 09:35:30PM +0000, Ben Hutchings wrote:
>> On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote:
>>> On 12/29/2010 09:10 AM, Ben Hutchings wrote:
>>>> On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote:
>>>>> On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote:
>>>>>> Could you try to reproduce this with a current 2.6.37-rcX
>>>>>> kernel from experimental?
>>>>>> The kernel is available from packages.debian.org. If the error can
>>>>>> still be reproduced, we should report it upstream.
>>>>> Unfortunately, 2.6.37-rc7-amd64 has an even greater problem, which
>>>>> prevents me from testing it. The error I am now encountering seems to
>>>>> be the one discussed here:
>>>> That was fixed in 2.6.37-rc5.
>>> ...then it has been re-introduced, or a new bug which causes the same
>>> behavior for at least my keyspan device has cropped up in -rc7. All
>>> access attempts to all of the 4 ports of my device with 2.6.37-rc7
>>> failed with a "Resource Temporarily Unavailable" error.
>> Please add that information on bugzilla.kernel.org.
> it seems you didn't followup in the kernel.org bugzilla. Is this fixed
> in current kernels from sid or testing?
Testing on a different computer, just plugging it in with a clean boot
on the same kernel version as before (that this bug was filed against)
immediately crashed the kernel (OOPS, followed shortly by a constant
terminal bell and no response to any input, not even numlock or SysRq).
Testing this device using linux-image2.6.38-2-amd64 from current sid
(v2.6.38-4) resulted in all 4 ports working perfectly. However, I only
could test them individually on that machine, so I can not confirm they
will work simultaneously as they are used on the real system. But, it
certainly seems better to me.
I will follow up once I get a chance to test this on the live system
with this new kernel version, but that may be a while. I suspect this
bug is now resolved, but I can't confirm this until then.
Steaphan Greene <firstname.lastname@example.org>
Lecturer, Computer Science, Binghamton University
GPG public key: http://www.cs.binghamton.edu/~sgreene/gpg.key.txt