Oliver Neukum wrote:
Am Freitag, 2. April 2004 23:43 schrieb Alan Stern:
On Fri, 2 Apr 2004, Brad Campbell wrote:
Ahah, that's the thing. It's not locking up on the actual data URB, it
locks up on the URB after the data was sent. So from what I gather, the
data makes it to the disk, it just can't
Hi. This is the qmail-send program at enviroserver.envirolink.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
This user does not exist.
--- Below this line is a copy of the m
I have an Epson Stylus CX3200. But the GET_DEVICE_ID ioctl is not working
(see kern.log output below).
Because of this, user software like foomatic-gui cannot identify it.
Turns out there is a bug in the GET_DEVICE_ID implementation. The patch below
(against 2.6.5-rc2) fixes the code to work accor
Am Freitag, 2. April 2004 23:43 schrieb Alan Stern:
> On Fri, 2 Apr 2004, Brad Campbell wrote:
> > Ahah, that's the thing. It's not locking up on the actual data URB, it
> > locks up on the URB after the data was sent. So from what I gather, the
> > data makes it to the disk, it just can't retrieve
Heiko Rosemann wrote:
Hi everyone,
I'm standing a little bit on the other side of the road - I am currently
developing a USB HID. Things work with Windows 98 and XP, but with Linux
(both 2.4.24 and 2.6.3) I get errors when it tries to receive the device
descriptor. 2.4.24 tells me:
usb.c: USB devi
USB doesn't really work on my ThinkPad X40. It either panics or oopses
if I unplug a device or suspend/resume using APM.
I'm running standard kernel 2.6.5-rc3-mm4, but this has never
worked on any kernel back to 2.6.3. USB works more or less OK with
2.4.25, but I cannot run 2.4 thanks to suspend/r
On Fri, 2004-04-02 at 18:40, Mike Anderson wrote:
> Greg stopped by and after talking this over I think I see why sd is
> racing in its current form. The race happens when sd_remove and do_open
> race. Even though I do not like adding a lock_kernel it would appear
> adding on to sd_remove would ser
On Fri, Apr 02, 2004 at 10:37:05AM -0800, David Brownell wrote:
> Greg KH wrote:
> >On Mon, Mar 29, 2004 at 06:47:53PM -0800, David Brownell wrote:
> >
> >>I pulled this out of my BK tree, didn't verify that it still
> >>behaves without everything else that's there ...
> >>
> >>The per-port LEDs on
On Fri, 2004-04-02 at 19:11, Mike Anderson wrote:
> It looks like cdrom_release always returns 0? Is there some other patch
> outstanding that changes this.
Yes, not that I know of.
However, while it apparently has a return code indicating success or
failure, we should respect it [unless Jens wan
James Bottomley [EMAIL PROTECTED] wrote:
> = drivers/scsi/sr.c 1.103 vs edited =
> --- 1.103/drivers/scsi/sr.c Fri Apr 2 11:30:44 2004
> +++ edited/drivers/scsi/sr.c Fri Apr 2 17:29:06 2004
> @@ -424,8 +424,19 @@
>
> static int sr_block_release(struct inode *inode, struct file *file
V I R U S A L E R T
Our viruschecker found the
'W32/Netsky-P'
virus(es) in your email to the following recipient(s):
-> <[EMAIL PROTECTED]>
Please check your system for viruses, or ask your system administrator
to do so.
For your reference, here are the hea
James Bottomley [EMAIL PROTECTED] wrote:
> On Fri, 2004-04-02 at 12:44, Mike Anderson wrote:
> > Where does the last put come from? How do you close the open race or
> > know when the final put_disk has been called? SCSI cannot do this alone
> > as we have created and registered an object in anothe
On Thu, 2004-04-01 at 18:32, James Bottomley wrote:
> Now, the questions are, whose issue is this and how do we fix it? I can
> see that a driver needs early notification of unplugs so it can deny all
> access to a gone device. On the other hand, for a user land open where
> we still have to hold
On Fri, 2 Apr 2004, Brad Campbell wrote:
> Ahah, that's the thing. It's not locking up on the actual data URB, it locks up on
> the URB after the
> data was sent. So from what I gather, the data makes it to the disk, it just can't
> retrieve the
> status of the transfer.
You're missing the po
This message conforms to all email spam restrictions for the USA and Canada. To opt out please see bottom of email and we will honor your request.
This weeks "Featured Advertiser" HaggleMe.com
The alternative to high priced auctions. Both Buyers and Sellers will find HaggleMe.com to be a us
Greg KH wrote:
On Mon, Mar 29, 2004 at 06:47:53PM -0800, David Brownell wrote:
I pulled this out of my BK tree, didn't verify that it still
behaves without everything else that's there ...
The per-port LEDs on the most USB 2.0 hubs are programmable.
And the USB spec describes some ways to use them
On Mon, Mar 29, 2004 at 06:47:53PM -0800, David Brownell wrote:
> I pulled this out of my BK tree, didn't verify that it still
> behaves without everything else that's there ...
>
> The per-port LEDs on the most USB 2.0 hubs are programmable.
> And the USB spec describes some ways to use them, bli
On Fri, 2004-04-02 at 12:44, Mike Anderson wrote:
> Where does the last put come from? How do you close the open race or
> know when the final put_disk has been called? SCSI cannot do this alone
> as we have created and registered an object in another subsystem
> (alloc_disk and add_disk) and we ha
James Bottomley [EMAIL PROTECTED] wrote:
> On Fri, 2004-04-02 at 11:45, Mike Anderson wrote:
> > Maybe some clarification here as I am unsure if we both think there
> > needs to be a notification (a put call) from outside SCSI. We have
> > release functions available on most objects in SCSI now. Th
Sergey Vlasov wrote:
This thing is seriously broken, both for 2.4.x and 2.6.x:
1) Allocating "struct hiddev_usage_ref_multi uref_multi" on the
stack in hiddev_ioctl() is not good - with HID_MAX_USAGES==1024, it
is more than 4K.
I suppose an artifical limit could be put in (32 maybe?) which forces
On Fri, 2004-04-02 at 11:45, Mike Anderson wrote:
> Maybe some clarification here as I am unsure if we both think there
> needs to be a notification (a put call) from outside SCSI. We have
> release functions available on most objects in SCSI now. The issue is
> that when we register (add_disk, dev
James Bottomley [EMAIL PROTECTED] wrote:
> > Recently I have not been spending the proper time looking at this, but
> > last look it appeared that we needed to add a release / put method call
> > to the gendisk disk_release routine. The release function or object to do
> > the put on would need to
On Fri, 2004-04-02 at 03:43, Mike Anderson wrote:
> I have looked at the sd issue off and on due to the previous open race
> reported by Alan Stern. While the window can be narrowed inside SCSI you
> need help for the calling subsystem to know when it is OK to cleanup and
> your routine will not be
Alan Stern wrote:
On Thu, 1 Apr 2004, Brad Campbell wrote:
Indeed. One thing I did find interesting though is that windows recovered whereas
linux needs an
unplug/plug to recover (or sometimes a power cycle). I include the bit of USB-Snoopy
log that shows
the urb going down, the lockup and reco
On Wed, 31 Mar 2004, Marc-Christian Petersen wrote:
> On Sunday 28 March 2004 00:51, Alan Stern wrote:
>
> Hi Grzegorz,
>
> > > When running modem_run on 2.6.4-WOLK2.3 it locks in D state on one of USB
> > > ioctls. It works at least on 2.6.2-rc2. I have no idea what causes this
> > > bug so I s
User mailbox exceeds allowed size: [EMAIL PROTECTED]
Original message follows.
Received: from tautobiotech.com [218.88.41.109] by liming.com with ESMTP
(SMTPD32-7.07) id ADD318790024; Fri, 02 Apr 2004 14:53:07 +0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Mail System ([EMAIL PRO
On Wed, Mar 17, 2004 at 04:01:52PM -0800, Greg KH wrote:
> ChangeSet 1.1290.15.4, 2004/02/02 14:36:26-08:00, [EMAIL PROTECTED]
>
> [PATCH] USB: Fixing HID support for non-explicitly specified usages
>
>
> drivers/usb/hid-core.c | 11 +-
> drivers/usb/hiddev.c | 78
Your message
To: [EMAIL PROTECTED]
Subject: account?
Sent:Fri, 2 Apr 2004 02:18:07 -0800
did not reach the following recipient(s):
[EMAIL PROTECTED] on Fri, 2 Apr 2004 02:20:07 -0800
The recipient name is not recognized
The MTS-ID of the original message is: c=us;a=
;p
Alan Stern [EMAIL PROTECTED] wrote:
> > You can search the lkml archives for the bugs that my kobject patch
> > fixed, as there was some discussion there (otherwise I would have never
> > written the patch...)
>
> I searched and found one thread that looks relevant:
>
> http://marc.theaimsgroup.c
James Bottomley [EMAIL PROTECTED] wrote:
>
> Well, I know why this happens, but I'm not entirely clear how to fix it.
>
> The problem comes because the cdrom open and close take and release
> references to the SCSI generic device (as they're supposed to).
>
> However, Upper level Drivers like sr
30 matches
Mail list logo
