On Wed, May 09, 2007 at 01:14:59AM +0100, Ken Moffat wrote:
> On Wed, May 09, 2007 at 01:01:34AM +0200, Andi Kleen wrote:
> >
> > Already known, although it is still unclear what the bug actually is.
> > Can you run with the appended patch please (from Eric Biederman)
> > and post any backtraces
On Wed, May 09, 2007 at 01:14:59AM +0100, Ken Moffat wrote:
On Wed, May 09, 2007 at 01:01:34AM +0200, Andi Kleen wrote:
Already known, although it is still unclear what the bug actually is.
Can you run with the appended patch please (from Eric Biederman)
and post any backtraces the
Hi,
Seems I have the same problem. Sometimes whole system is locked,
sometimes keyboard is still active but others dead.
It does not happen till now since I run a silly script on background
to log the kernel messages:
-
#!/bin/sh
while true; do
sleep 3
dmesg >/tmp/dmesg.txt
sync
On Wed, May 09, 2007 at 01:01:34AM +0200, Andi Kleen wrote:
>
> Already known, although it is still unclear what the bug actually is.
> Can you run with the appended patch please (from Eric Biederman)
> and post any backtraces the WARN_ON in there spews out?
>
> Also do you use swiotlb?
>
>
On Wed, 09 May 2007 01:01:34 +0200, Andi Kleen said:
> Already known, although it is still unclear what the bug actually is.
> Can you run with the appended patch please (from Eric Biederman)
> and post any backtraces the WARN_ON in there spews out?
> diff --git a/include/asm-x86_64/page.h
On Wed, May 09, 2007 at 12:47:02AM +0200, Michal Piotrowski wrote:
>
> Please check the latest -git.
>
> 31 hours ago Linus Torvalds Revert "[PATCH] x86: __pa and
> __pa_symbol address space ...
>
>
On Tue, May 08, 2007 at 08:51:42PM +0100, Ken Moffat wrote:
> This is a resend, with a better title and slightly more
> clarification. Originally sent yesterday evening, but I can see no
> evidence that it got beyond my isp's mailserver. Apologies to the
> Cc's if you did get the original.
>
>
Hi Ken,
On 08/05/07, Ken Moffat <[EMAIL PROTECTED]> wrote:
This is a resend, with a better title and slightly more
clarification. Originally sent yesterday evening, but I can see no
evidence that it got beyond my isp's mailserver. Apologies to the
Cc's if you did get the original.
Using
On Tue, May 08, 2007 at 04:21:51PM -0400, [EMAIL PROTECTED] wrote:
> On Tue, 08 May 2007 20:51:42 BST, Ken Moffat said:
>
> > After trying git-bisect, it tells me:
> > 0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
> > commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
> > Author:
On Tue, 08 May 2007 20:51:42 BST, Ken Moffat said:
> After trying git-bisect, it tells me:
> 0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
> commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
> Author: Vivek Goyal <[EMAIL PROTECTED]>
> Date: Wed May 2 19:27:07 2007 +0200
>
>
This is a resend, with a better title and slightly more
clarification. Originally sent yesterday evening, but I can see no
evidence that it got beyond my isp's mailserver. Apologies to the
Cc's if you did get the original.
Using Linus' tree pulled on Sunday afternoon UK time. Running an
This is a resend, with a better title and slightly more
clarification. Originally sent yesterday evening, but I can see no
evidence that it got beyond my isp's mailserver. Apologies to the
Cc's if you did get the original.
Using Linus' tree pulled on Sunday afternoon UK time. Running an
On Tue, 08 May 2007 20:51:42 BST, Ken Moffat said:
After trying git-bisect, it tells me:
0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
Author: Vivek Goyal [EMAIL PROTECTED]
Date: Wed May 2 19:27:07 2007 +0200
[PATCH]
On Tue, May 08, 2007 at 04:21:51PM -0400, [EMAIL PROTECTED] wrote:
On Tue, 08 May 2007 20:51:42 BST, Ken Moffat said:
After trying git-bisect, it tells me:
0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
Author: Vivek Goyal
Hi Ken,
On 08/05/07, Ken Moffat [EMAIL PROTECTED] wrote:
This is a resend, with a better title and slightly more
clarification. Originally sent yesterday evening, but I can see no
evidence that it got beyond my isp's mailserver. Apologies to the
Cc's if you did get the original.
Using
On Tue, May 08, 2007 at 08:51:42PM +0100, Ken Moffat wrote:
This is a resend, with a better title and slightly more
clarification. Originally sent yesterday evening, but I can see no
evidence that it got beyond my isp's mailserver. Apologies to the
Cc's if you did get the original.
On Wed, May 09, 2007 at 12:47:02AM +0200, Michal Piotrowski wrote:
Please check the latest -git.
31 hours ago Linus Torvalds Revert [PATCH] x86: __pa and
__pa_symbol address space ...
On Wed, 09 May 2007 01:01:34 +0200, Andi Kleen said:
Already known, although it is still unclear what the bug actually is.
Can you run with the appended patch please (from Eric Biederman)
and post any backtraces the WARN_ON in there spews out?
diff --git a/include/asm-x86_64/page.h
On Wed, May 09, 2007 at 01:01:34AM +0200, Andi Kleen wrote:
Already known, although it is still unclear what the bug actually is.
Can you run with the appended patch please (from Eric Biederman)
and post any backtraces the WARN_ON in there spews out?
Also do you use swiotlb?
Thanks
Hi,
Seems I have the same problem. Sometimes whole system is locked,
sometimes keyboard is still active but others dead.
It does not happen till now since I run a silly script on background
to log the kernel messages:
-
#!/bin/sh
while true; do
sleep 3
dmesg /tmp/dmesg.txt
sync
20 matches
Mail list logo
