Hi Alan,
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote:
[...]
>
> That looks fine. Below is that actual patch I propose for 2.6.20. Can
> you please try it out and make sure that it really does fix the problem?
> Be sure to remove the test patch first, since this wants to go on top of
> plain
On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> >
> > > I had some problems with the 2.6.20 kernel on my distribution and so I
> > > wasn't able to test the patch for some time. Fortunately, every
On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Sun, 25 Feb 2007, Guilherme Salgado wrote:
>
> > I had some problems with the 2.6.20 kernel on my distribution and so I
> > wasn't able to test the patch for some time. Fortunately, everything
> > is working now and I'm running 2.6.20 with the
On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> I had some problems with the 2.6.20 kernel on my distribution and so I
> wasn't able to test the patch for some time. Fortunately, everything
> is working now and I'm running 2.6.20 with the patch you provided, and
> the "can't resume" problem is gon
Hi,
On 2/14/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Feb 2007, Guilherme Salgado wrote:
[...]
> > so I did the
> > changes manually and used upper case characters on the message passed
> > to dev_info(), to make sure the new module was loaded correctly, and I
> > seem to have got th
On Tue, 13 Feb 2007, Guilherme Salgado wrote:
> Hi Alan,
> > Below is a revised version of the diagnostic patch. Try using it instead
> > of the earlier one and let's see what happens.
> >
>
> This revised version didn't apply cleanly into my tree,
Maybe because you didn't remove the original
Hi Alan,
On 2/13/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 12 Feb 2007, Guilherme Salgado wrote:
>
> > > On Thu, 11 Jan 2007, Jon Smirl wrote:
> > >
> > [...]
> > >
> > > Here we see a resume that failed. The key indicator is the 0x1000 bit in
> > > the portsc value; it means the port i
On Mon, 12 Feb 2007, Guilherme Salgado wrote:
> > On Thu, 11 Jan 2007, Jon Smirl wrote:
> >
> [...]
> >
> > Here we see a resume that failed. The key indicator is the 0x1000 bit in
> > the portsc value; it means the port is still suspended even after it was
> > supposed to have resumed. This is
> On Thu, 11 Jan 2007, Jon Smirl wrote:
>
[...]
>
> Here we see a resume that failed. The key indicator is the 0x1000 bit in
> the portsc value; it means the port is still suspended even after it was
> supposed to have resumed. This is the Intel hardware-resume bug I
> described earlier. I have
I tried the device with USBCV. Under WinXP the device behavior is
flaky and I can't get USBCV to work on it at all. On the other hand,
the device functions without problem on Win2K.
I'd say there is something wrong with the resume implementation on the
device. The device does not have updatable fi
On Fri, 12 Jan 2007, Jon Smirl wrote:
> On 1/12/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Fri, 12 Jan 2007, Jon Smirl wrote:
> >
> > > Attachment is too big for the list.
> > > It seems to be stuck in a resume loop with your debug patch installed.
> > >
> > > Device is plugged into a USB 1.
On Thursday 11 January 2007 9:21 pm, Jon Smirl wrote:
> So why does the device work when plugged into a powered hub? Do the
> ports on the powered hub not do suspend/resume?
All USB hubs (root and otherwise) are supposed to support suspend/resume,
and you'd probably observe they're using it during
On 1/12/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Jan 2007, Jon Smirl wrote:
>
> > Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
> > the device did on the ICH5. This is starting to point to a broken
> > resume capability in the device. I have more systems around b
On Fri, 12 Jan 2007, Jon Smirl wrote:
> Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
> the device did on the ICH5. This is starting to point to a broken
> resume capability in the device. I have more systems around but they
> are all ICH4/5.
>
> So why does the device work
On Thu, 11 Jan 2007, Jon Smirl wrote:
> On 1/11/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> > The default Ubuntu kernel, 2.6.17-10-generic has CONFIG_USB_SUSPEND=y.
> > I plugged the device into the laptop and it powered on fine at boot.
> > When the build finishes I'll try with 2.6.20-rc4 and verb
Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
the device did on the ICH5. This is starting to point to a broken
resume capability in the device. I have more systems around but they
are all ICH4/5.
So why does the device work when plugged into a powered hub? Do the
ports on th
On 1/11/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> The default Ubuntu kernel, 2.6.17-10-generic has CONFIG_USB_SUSPEND=y.
> I plugged the device into the laptop and it powered on fine at boot.
> When the build finishes I'll try with 2.6.20-rc4 and verbose USB
> debug.
Ubuntu 2.6.17 kernels with CO
On 1/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> Have you got a different computer to try this on?
I just kicked off a kernel build with the right config for my laptop
which has an ICH4.
I have a few other computers I can try if we need to.
The default Ubuntu kernel, 2.6.17-10-generic has CONF
On Thu, 11 Jan 2007, Jon Smirl wrote:
> In this log I booted with it plugged in and let the usbhid drivers load.
> I then successively modprobe/rmmod them.
>
> There were only two ways I could get the device working once it went
> into suspend:
> rmmod/modprobe uhci_hcd;modprobe usbhid
> usbreset
On 1/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
Probably the new driver wasn't loaded. On my system (FC6) uhci-hcd is
loaded as part of the initrd image, not through the usual sort of
on-demand loading. You may need to rmmod uhci-hcd and then load the
modified driver.
I see now it is on ini
On Thu, 11 Jan 2007, Jon Smirl wrote:
> It doesn't appear to have hit your debug code but I am sure I built it
> into the driver.
The debug code did not run, but it should have.
Probably the new driver wasn't loaded. On my system (FC6) uhci-hcd is
loaded as part of the initrd image, not through
It doesn't appear to have hit your debug code but I am sure I built it
into the driver.
--
Jon Smirl
[EMAIL PROTECTED]
dmesg1
Description: Binary data
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.n
On Thu, 11 Jan 2007, Jon Smirl wrote:
> Attached dmesg may explain what is happening.
I don't think so.
> I renamed all my sound and usb input modules so that they wouldn't
> load at boot. I then manually modprobe'd usbhid in.
>
> The device implements two profiles, sound and hid. How is error
Attached dmesg may explain what is happening.
I renamed all my sound and usb input modules so that they wouldn't
load at boot. I then manually modprobe'd usbhid in.
The device implements two profiles, sound and hid. How is error
processing going to work if both of these modules attach to the dev
On Wed, 10 Jan 2007, Jon Smirl wrote:
> > What happened to the HID interface before the reset?
>
> How can I check it? The controls cause events, is there some way to see them?
Well, earlier you wrote:
> This doesn't help but it is complicated because the PSC805 also
> includes a USBHID compo
On 1/10/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 10 Jan 2007, Jon Smirl wrote:
>
> > I just rebooted and all of the drivers loaded automatically but the
> > device didn't work.
> > Doing a usbreset of the device fixed everything.
> >
> > My best guess is that the "usb 2-1: usb auto-resum
On Wed, 10 Jan 2007, Jon Smirl wrote:
> I just rebooted and all of the drivers loaded automatically but the
> device didn't work.
> Doing a usbreset of the device fixed everything.
>
> My best guess is that the "usb 2-1: usb auto-resume" failed to enable
> power to the device.
The dmesg log for
I just rebooted and all of the drivers loaded automatically but the
device didn't work.
Doing a usbreset of the device fixed everything.
My best guess is that the "usb 2-1: usb auto-resume" failed to enable
power to the device.
Note that the failure only happens when the device is plugged into a
On 1/10/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> There is no way to prevent a USB device without a driver from being
> suspended. Perhaps we need one. On the other hand, USB devices _are_
> supposed to be able to suspend and resume with no ill effects -- it's part
> of the spec.
>
> I still wo
Brief summary: After being suspended and resumed, Jon's USB sound device
remains in a useless powered-off state (the LEDs don't turn back on).
Clemens, if you have any ideas that might be relevant, please let us know.
On Tue, 9 Jan 2007, Jon Smirl wrote:
> Something has a refcount set into snd
On Tue, 9 Jan 2007, Jon Smirl wrote:
> I tried to unbind/bind with the device in the not working state:
> snd-usb-audio 2-1:1.0: usb_probe_interface
> snd-usb-audio 2-1:1.0: usb_probe_interface - got id
> USB device is in the shutdown state, cannot create a card instance
> snd-usb-audio: probe of
I turned off CONFIG_USB_SUSPEND and everything is working.
--
Jon Smirl
[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opi
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > I tried to unbind/bind with the device in the not working state:
> > snd-usb-audio 2-1:1.0: usb_probe_interface
> > snd-usb-audio 2-1:1.0: usb_probe_interface - got id
> > USB device is in the shutdown sta
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > > On Tue, 9 Jan 2007, Jon Smirl wrote:
> > >
> > > > Is there some tool or sys variable that can toggle power to the
> > > > device? That will let me se
On Tue, 9 Jan 2007, Jon Smirl wrote:
> On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Tue, 9 Jan 2007, Jon Smirl wrote:
> >
> > > Is there some tool or sys variable that can toggle power to the
> > > device? That will let me see if it is in sleep mode when it shouldn't
> > > be.
> >
> > I
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > Is there some tool or sys variable that can toggle power to the
> > device? That will let me see if it is in sleep mode when it shouldn't
> > be.
>
> If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > Is there some tool or sys variable that can toggle power to the
> > device? That will let me see if it is in sleep mode when it shouldn't
> > be.
>
> If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can
On Tue, 9 Jan 2007, Jon Smirl wrote:
> Is there some tool or sys variable that can toggle power to the
> device? That will let me see if it is in sleep mode when it shouldn't
> be.
If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can suspend your device
by doing:
echo -n 2 >/sys/bus/u
On Mon, 8 Jan 2007, Jon Smirl wrote:
> On 1/8/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > What shows up in dmesg?
> dmesg is the same when it works and when it doesn't
I bet if you compare a working and a non-working dmesg log now that you
have CONFIG_USB_DEBUG turned on, you'll find a differen
On 1/8/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> >What happens if you unplug the device and then plug it directly into
> the computer?
Is there some tool or sys variable that can toggle power to the
device? That will let me see if it is in sleep mode when it shouldn't
be.
--
Jon Smirl
[EMAIL PR
On 1/8/07, Alan Stern <[EMAIL PROTECTED]> wrote:
What shows up in dmesg?
dmesg is the same when it works and when it doesn't
What happens if you unplug the device and then plug it directly into
the computer?
it works. As far as I can tell the problem only occurs on boot
What do you get if
On Mon, 8 Jan 2007, Jon Smirl wrote:
> I have a Philips PSC805 external audio device. It is powered via USB.
> This device used to work plugged directly into my desktop. Now it is
> coming up, initializing, and then shutting down once user space
> starts. This happens about 90% of the time but not
I have a Philips PSC805 external audio device. It is powered via USB.
This device used to work plugged directly into my desktop. Now it is
coming up, initializing, and then shutting down once user space
starts. This happens about 90% of the time but not always.
If I move the device to a powered h
43 matches
Mail list logo
