Please verify if APIC mode can help this case?
Thanks
Luming
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Blueman
>Sent: 2004年10月25日 4:20
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: [2.6.9] unhandled OHCI IRQs...
>
>When plugging in
On Tue, Oct 19, Alan Stern wrote:
> Can you run the tests with a different USB disk drive? Were the tests on
> the Intel and PPC machines done using the same drive?
I have tried it on OSX today, copied 8 iso images on the drive,
rebooted, and copied it back to the internal disk.
3 images were c
Hi all,
I've found the explanation about the change of this bit.
It's written in the UHCI specification ( read it better next time! ) and is
the result of the HCRESET command sent in uhci.c: start_hc().
Patrick Agrain
---
This SF.net email is s
On Tue, 26 Oct 2004, Olaf Hering wrote:
> On Tue, Oct 19, Alan Stern wrote:
>
> > Can you run the tests with a different USB disk drive? Were the tests on
> > the Intel and PPC machines done using the same drive?
>
> I have tried it on OSX today, copied 8 iso images on the drive,
> rebooted, a
On Tue, 26 Oct 2004 [EMAIL PROTECTED] wrote:
> Well, I think I must admit I was wrong.
>
> I have done some tests and there was no ooops after succesful writing or after
> unmounting device. The oops is when I unplug USB-DVD-Recorder when there is
> already mounted device on it.
>
> Then there i
On Tuesday 26 October 2004 05:16, Olaf Hering wrote:
> On Tue, Oct 19, Alan Stern wrote:
>
> > Can you run the tests with a different USB disk drive? Were the tests on
> > the Intel and PPC machines done using the same drive?
>
> I have tried it on OSX today, copied 8 iso images on the drive,
>
On Tue, Oct 26, David Brownell wrote:
> On Tuesday 26 October 2004 05:16, Olaf Hering wrote:
> > On Tue, Oct 19, Alan Stern wrote:
> >
> > > Can you run the tests with a different USB disk drive? Were the tests on
> > > the Intel and PPC machines done using the same drive?
> >
> > I have trie
Hi,
2.6.10-rc1 gives the following error messages on my iBook G4, which uses
the ohci-hcd driver:
usb usb2: usbfs: USBDEVFS_CONTROL failed cmd usbmodules rqt 128 rq 6 len 18 ret -113
usb usb2: usbfs: USBDEVFS_CONTROL failed cmd usbmodules rqt 128 rq 6 len 18 ret -113
usb usb2: usbfs: USBDEVFS_CON
On Tue, 26 Oct 2004, Olaf Hering wrote:
> Hmm, 'assuming drive cache: write through', can that make a difference
> if I force some other cache mode? Maybe both Linux and OSX get confused
> because the drive reports something wrong?
I think that the cache mode only affects the behavior when you fl
On Tuesday 26 October 2004 08:28, Colin Leroy wrote:
> Hi,
>
> 2.6.10-rc1 gives the following error messages on my iBook G4, which uses
> the ohci-hcd driver:
>
> usb usb2: usbfs: USBDEVFS_CONTROL failed cmd usbmodules rqt 128 rq 6 len 18
ret -113
> usb usb2: usbfs: USBDEVFS_CONTROL failed cmd u
On Mon, 25 Oct 2004 12:19:10 -0400 (EDT), Alan Stern
<[EMAIL PROTECTED]> wrote:
> > This is a followup to the thread regarding my USB keyboard problem.
[snipped]
> Please try applying the patch below, and then post the dmesg output you
> get when plugging the keyboard in after bootup.
Hi,
I was p
On Wed, 27 Oct 2004, Gideon N. Guillen wrote:
> Hi,
>
> I was partially wrong about may last message. It seems that the
> keyboard is working already in 2.6.9. I successfully pass the
> "Mounting USB file system" part. It still "freezes". Well not really,
> more like it stays there for 30 to 45 s
[EMAIL PROTECTED] wrote:
On Thu, 21 Oct 2004, Alan Stern wrote:
On Thu, 21 Oct 2004 [EMAIL PROTECTED] wrote:
After successful write on USB DVD-R writer (HP-200j), system oops's when unpluging USB
device.
Same thing with 2.6.9-rc2mm1.
Try applying this patch:
http://marc.theaimsgroup.com/?l=linux
Mike Christie wrote:
[EMAIL PROTECTED] wrote:
On Thu, 21 Oct 2004, Alan Stern wrote:
On Thu, 21 Oct 2004 [EMAIL PROTECTED] wrote:
After successful write on USB DVD-R writer (HP-200j), system
oops's when unpluging USB device.
Same thing with 2.6.9-rc2mm1.
Try applying this patch:
http://marc.the
This patch resolves several problems that prevent system sleep transitions,
mostly by updating the PCI and USB bus-specific code to understand cases
where the PM core is deluded. Please merge.
- Dave
This patch makes usbcore behave better with system sleep states, fixing
some PM/PCI integration p
These mostly make the root hub autosuspend logic use the
usbcore logic more directly. Please merge; this relies on some
symbols exported from usbcore by a previous patch.
- Dave
This makes OHCI use more of the standard usbcore suspend/resume logic
when it's available (exported by a different pat
This makes some diagnostics more useful, and adds one to report when
khubd starts to scan a hub. Please merge.
- Dave
Minor updates for better diagnostics from usbcore:
- Only print ep0 maxpacket when it's not what we first tried
- have khubd say when it's looking at a hub
- When warning ab
This gets the EHCI driver in much the same state as OHCI with respect to
ACPI S1 or swsusp style suspend: the driver behaves OK, "rmmod" not
needed (in conjunction with usbcore updates). Please merge.
- Dave
This patch much improves suspend/resume behavior of EHCI, as tested with
"echo suspend >
Here's a small patch with a few tiny fixups for the EHCI Kconfig help
text. Please consider applying.
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
diff -u linux-2.6.10-rc1-bk5-orig/drivers/usb/host/Kconfig
linux-2.6.10-rc1-bk5/drivers/usb/host/Kconfig
--- linux-2.6.10-rc1-bk5-orig/drivers/us
Hey Alan,
Unfortunately I haven't had any luck fixing this timing issue, so I've
returned to seek wisdom and guidance. I've tried:
-capping the average transfer speed in my driver
-looking for similar behaviour in the Windows driver
Everything I've observed* suggests (to me) a l
Begin forwarded message:
Date: Wed, 27 Oct 2004 01:10:57 +0200
From: Ernst Herzberg <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: OOPS: 2.6.9 (not reproducable)
Thinkpad R50p:
Oct 26 23:26:25 halso Linux version 2.6.9 ([EMAIL PROTECTED]) (gcc version 3.3.4
20040623 (Gentoo Linux 3.3.4-
On Tue, 2004-10-26 at 14:08, Mike Christie wrote:
> > The null state and and oops are becuase of this
> > http://marc.theaimsgroup.com/?l=linux-scsi&m=109733573729283&w=2
>
> Oh yeah. that patch is not correct, but if you correctly modify it to
> use device_for_each_child per Christoph's suggestio
James Bottomley wrote:
On Tue, 2004-10-26 at 14:08, Mike Christie wrote:
The null state and and oops are becuase of this
http://marc.theaimsgroup.com/?l=linux-scsi&m=109733573729283&w=2
Oh yeah. that patch is not correct, but if you correctly modify it to
use device_for_each_child per Christoph's s
James Bottomley wrote:
On Tue, 2004-10-26 at 14:08, Mike Christie wrote:
The null state and and oops are becuase of this
http://marc.theaimsgroup.com/?l=linux-scsi&m=109733573729283&w=2
Oh yeah. that patch is not correct, but if you correctly modify it to
use device_for_each_child per Christoph's s
24 matches
Mail list logo