On 01/08/2014 01:11 AM, Sarah Sharp wrote:
> Denis, what do you mean by "works for Lynx Point"? Do you mean that
> adding the quirk to switch the ports on EHCI on shutdown (e95829f474)
> for the Intense-PC2 *instead of* the commit to put the host in D3 on
> shutdown (638298dc66) works? Or do you
On 01/08/2014 01:11 AM, Sarah Sharp wrote:
Denis, what do you mean by works for Lynx Point? Do you mean that
adding the quirk to switch the ports on EHCI on shutdown (e95829f474)
for the Intense-PC2 *instead of* the commit to put the host in D3 on
shutdown (638298dc66) works? Or do you mean
On Tue, Jan 07, 2014 at 11:03:00AM +0100, Takashi Iwai wrote:
> At Mon, 06 Jan 2014 14:34:28 +0200,
> Denis Turischev wrote:
> >
> > Hi Sarah,
> >
> > On 01/03/2014 02:03 AM, Sarah Sharp wrote:
> > > Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> > > they all running a
At Mon, 06 Jan 2014 14:34:28 +0200,
Denis Turischev wrote:
>
> Hi Sarah,
>
> On 01/03/2014 02:03 AM, Sarah Sharp wrote:
> > Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> > they all running a Phoenix BIOS? Can you send me the output of `sudo
> > lspci -vvv -s` for the
At Mon, 06 Jan 2014 14:34:28 +0200,
Denis Turischev wrote:
Hi Sarah,
On 01/03/2014 02:03 AM, Sarah Sharp wrote:
Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
they all running a Phoenix BIOS? Can you send me the output of `sudo
lspci -vvv -s` for the xHCI host?
On Tue, Jan 07, 2014 at 11:03:00AM +0100, Takashi Iwai wrote:
At Mon, 06 Jan 2014 14:34:28 +0200,
Denis Turischev wrote:
Hi Sarah,
On 01/03/2014 02:03 AM, Sarah Sharp wrote:
Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
they all running a Phoenix BIOS? Can
Hi Sarah,
On 01/03/2014 02:03 AM, Sarah Sharp wrote:
> Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> they all running a Phoenix BIOS? Can you send me the output of `sudo
> lspci -vvv -s` for the xHCI host?
oem@oem-Intense-PC2 ~ $ sudo lspci -vvv -s 00:14.0
00:14.0 USB
Hi Sarah,
On 01/03/2014 02:03 AM, Sarah Sharp wrote:
Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
they all running a Phoenix BIOS? Can you send me the output of `sudo
lspci -vvv -s` for the xHCI host?
oem@oem-Intense-PC2 ~ $ sudo lspci -vvv -s 00:14.0
00:14.0 USB
On 01/03/2014 01:03 AM, Sarah Sharp wrote:
ISTR that the other folks on Cc (Meng, Niklas, Giorgos, and Art) all
had systems that broke when commit
638298dc66ea36623dbc2757a24fc2c4ab41b016 was introduced. For those
systems, what vendor was the system, and what BIOS was it running?
Information
On Thu, 2014-01-02 at 16:03 -0800, Sarah Sharp wrote:
> That means your system worked fine in 3.13-rc3 (when the quirk was
> applied broadly), but won't work for 3.13-rc6 (when the quirk was
> narrowed to HP machines). So we need the quirk to apply to your
> systems
> as well.
>
> ISTR that the
On Thu, 2014-01-02 at 16:03 -0800, Sarah Sharp wrote:
That means your system worked fine in 3.13-rc3 (when the quirk was
applied broadly), but won't work for 3.13-rc6 (when the quirk was
narrowed to HP machines). So we need the quirk to apply to your
systems
as well.
ISTR that the other
On 01/03/2014 01:03 AM, Sarah Sharp wrote:
ISTR that the other folks on Cc (Meng, Niklas, Giorgos, and Art) all
had systems that broke when commit
638298dc66ea36623dbc2757a24fc2c4ab41b016 was introduced. For those
systems, what vendor was the system, and what BIOS was it running?
Information
On Thu, 2 Jan 2014 16:03:34 -0800
Sarah Sharp wrote:
> On Sun, Dec 22, 2013 at 09:47:49AM +0200, Denis Turischev wrote:
> > On 12/21/2013 01:45 AM, Sarah Sharp wrote:
> > > On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
> > >>> Also, which kernel are you experiencing this issue
On Sun, Dec 22, 2013 at 09:47:49AM +0200, Denis Turischev wrote:
> On 12/21/2013 01:45 AM, Sarah Sharp wrote:
> > On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
> >>> Also, which kernel are you experiencing this issue on? In 3.12, I
> >>> queued a separate patch to deal with
On Sun, Dec 22, 2013 at 09:47:49AM +0200, Denis Turischev wrote:
On 12/21/2013 01:45 AM, Sarah Sharp wrote:
On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
Also, which kernel are you experiencing this issue on? In 3.12, I
queued a separate patch to deal with spurious
On Thu, 2 Jan 2014 16:03:34 -0800
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
On Sun, Dec 22, 2013 at 09:47:49AM +0200, Denis Turischev wrote:
On 12/21/2013 01:45 AM, Sarah Sharp wrote:
On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
Also, which kernel are you
On 12/21/2013 01:45 AM, Sarah Sharp wrote:
> On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
>>> Also, which kernel are you experiencing this issue on? In 3.12, I
>>> queued a separate patch to deal with spurious reboot issues on Lynx
>>> Point:
>>>
>>> commit
Sarah Sharp linux.intel.com> writes:
Good Afternoon,
> Also, do you have an HP system, or is this a different vendor?
for what its worth. I do have an Ivybridge laptop and I do see
immediate wake-ups from suspend to ram from time to time. When
this happens I do modprobe -r xhci_hcd and the
Sarah Sharp sarah.a.sharp at linux.intel.com writes:
Good Afternoon,
Also, do you have an HP system, or is this a different vendor?
for what its worth. I do have an Ivybridge laptop and I do see
immediate wake-ups from suspend to ram from time to time. When
this happens I do modprobe -r
On 12/21/2013 01:45 AM, Sarah Sharp wrote:
On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
Also, which kernel are you experiencing this issue on? In 3.12, I
queued a separate patch to deal with spurious reboot issues on Lynx
Point:
commit
On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
> > Also, which kernel are you experiencing this issue on? In 3.12, I
> > queued a separate patch to deal with spurious reboot issues on Lynx
> > Point:
> >
> > commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
> Sorry, I indeed
> Also, which kernel are you experiencing this issue on? In 3.12, I
> queued a separate patch to deal with spurious reboot issues on Lynx
> Point:
>
> commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
> Author: Takashi Iwai
> Date: Thu Sep 12 08:11:06 2013 +0200
>
> xhci: Fix spurious
Also, which kernel are you experiencing this issue on? In 3.12, I
queued a separate patch to deal with spurious reboot issues on Lynx
Point:
commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
Author: Takashi Iwai ti...@suse.de
Date: Thu Sep 12 08:11:06 2013 +0200
xhci: Fix spurious
On Fri, Dec 20, 2013 at 12:41:11PM +0200, Denis Turischev wrote:
Also, which kernel are you experiencing this issue on? In 3.12, I
queued a separate patch to deal with spurious reboot issues on Lynx
Point:
commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
Sorry, I indeed tested not on
This is actually v2.
On Thu, Dec 19, 2013 at 07:07:33PM +0200, Denis Turischev wrote:
> The same issue like with Panther Point chipsets. If the USB ports are
> switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
> which will wake the system. Some BIOS have work around for
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
The bug can be avoided if the USB ports are switched back to EHCI on
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
The bug can be avoided if the USB ports are switched back to EHCI on
This is actually v2.
On Thu, Dec 19, 2013 at 07:07:33PM +0200, Denis Turischev wrote:
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for
28 matches
Mail list logo
