Prev: Make Intel 8-way Xeons boot again
Next: [tip:x86/uv] x86, uv: uv_global_gru_mmr_address() macro fix
From: Dimitrios Apostolou on 18 Feb 2010 15:30
On Thu, 11 Feb 2010, Arjan van de Ven wrote:
> On Thu, 11 Feb 2010 22:58:21 +0100
> Wojciech Ploskonka <wploskonka(a)gmail.com> wrote:
>
>> 08:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394
>> Controller (rev 05) (prog-if 10 [OHCI])
>
> 08:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
> (rev 05) (prog-if 10 [OHCI])
>
> is the one having PME+ set.
>
> Len: how do we handle PME's again?

So is this something fixable? Did I lose some email?


Dimitris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dimitrios Apostolou on 22 Feb 2010 11:50
Hi Arjan, Len,

It seems that another user of archlinux (mie.iscrizioni CC'd) is having
the same problem, and this time I can't see any PME+ flag in lspci output.
The bug report is at [1] but since it's getting too big perhaps you want
to take a look at attachment [2], which includes "powertop -d",
"dmidecode" and "lspci -vvv" output.

BTW, the common denominator for all these cases is the message "Marking
TSC unstable due to TSC halts in idle". So I was thinking perhaps the code
that detects the bug is already there! What do you think?


Thanks,
Dimitris


[1] http://bugs.archlinux.org/task/17771
[2] http://bugs.archlinux.org/task/17771?getfile=4899
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Arjan van de Ven on 22 Feb 2010 21:00
On Mon, 22 Feb 2010 18:43:50 +0200 (EET)
Dimitrios Apostolou <jimis(a)gmx.net> wrote:

> Hi Arjan, Len,
>
> It seems that another user of archlinux (mie.iscrizioni CC'd) is
> having the same problem, and this time I can't see any PME+ flag in
> lspci output. The bug report is at [1] but since it's getting too big
> perhaps you want to take a look at attachment [2], which includes
> "powertop -d", "dmidecode" and "lspci -vvv" output.
>
> BTW, the common denominator for all these cases is the message
> "Marking TSC unstable due to TSC halts in idle". So I was thinking
> perhaps the code that detects the bug is already there! What do you
> think?

every single Intel and AMD cpu prior to the latest generation will spew
that message....
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Make Intel 8-way Xeons boot again
Next: [tip:x86/uv] x86, uv: uv_global_gru_mmr_address() macro fix