On Mon, 15 Jul 2013 10:32:17 +0800, "Li, Zhen-Hua" said:
> I have met a bug with the same error message, its cause was that the bios
> did not allocate RMRR/DRHD(can't remember which one) for the device.
I think I posted a link to that same bug report. The problem is that
if the BIOS wasn't
On Fri, 12 Jul 2013 14:14:20 +0200, Ingo Molnar said:
>
> (Cc:-ed a few DMAR people.)
Sorry for the slow reply, missed this in the lkml firehose.
For whatever reason, the damned problem seems to have evaporated:
% egrep -i 'dmar|Linux vers' /var/log/messages-20130714
Jul 11 18:54:15
On Fri, 12 Jul 2013 14:14:20 +0200, Ingo Molnar said:
(Cc:-ed a few DMAR people.)
Sorry for the slow reply, missed this in the lkml firehose.
For whatever reason, the damned problem seems to have evaporated:
% egrep -i 'dmar|Linux vers' /var/log/messages-20130714
Jul 11 18:54:15
On Mon, 15 Jul 2013 10:32:17 +0800, Li, Zhen-Hua said:
I have met a bug with the same error message, its cause was that the bios
did not allocate RMRR/DRHD(can't remember which one) for the device.
I think I posted a link to that same bug report. The problem is that
if the BIOS wasn't
I have met a bug with the same error message, its cause was that the bios
did not allocate RMRR/DRHD(can't remember which one) for the device.
Thanks
ZhenHua
On 07/12/2013 10:31 PM, Joerg Roedel wrote:
Thanks for the heads-up, Ingo.
On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
I have met a bug with the same error message, its cause was that the bios
did not allocate RMRR/DRHD(can't remember which one) for the device.
Thanks
ZhenHua
On 07/12/2013 10:31 PM, Joerg Roedel wrote:
Thanks for the heads-up, Ingo.
On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
Thanks for the heads-up, Ingo.
On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
> > Jul 10 12:20:19 turing-police kernel: [0.021583] DMAR:[fault reason 06]
> > PTE Read access is not set
> >
> > Now I have 3 extra messages talking about handling a fault status. lspci
> > says
(Cc:-ed a few DMAR people.)
* Valdis Kletnieks wrote:
> Dell Latitude E6530.
>
> Seeing a new error message crop up in next-0709 that wasn't there with 0703.
> Particularly odd, last person to touch dmar.c was on 05/20/2013, so no smoking
> guns there...
>
> egrep -i 'dmar|linux ver'
(Cc:-ed a few DMAR people.)
* Valdis Kletnieks valdis.kletni...@vt.edu wrote:
Dell Latitude E6530.
Seeing a new error message crop up in next-0709 that wasn't there with 0703.
Particularly odd, last person to touch dmar.c was on 05/20/2013, so no smoking
guns there...
egrep -i
Thanks for the heads-up, Ingo.
On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
Jul 10 12:20:19 turing-police kernel: [0.021583] DMAR:[fault reason 06]
PTE Read access is not set
Now I have 3 extra messages talking about handling a fault status. lspci
says 00:1f.2
Dell Latitude E6530.
Seeing a new error message crop up in next-0709 that wasn't there with 0703.
Particularly odd, last person to touch dmar.c was on 05/20/2013, so no smoking
guns there...
egrep -i 'dmar|linux ver' /var/log/messages gives me:
Jul 9 21:47:15 turing-police kernel: [
Dell Latitude E6530.
Seeing a new error message crop up in next-0709 that wasn't there with 0703.
Particularly odd, last person to touch dmar.c was on 05/20/2013, so no smoking
guns there...
egrep -i 'dmar|linux ver' /var/log/messages gives me:
Jul 9 21:47:15 turing-police kernel: [
12 matches
Mail list logo
