* Borislav Petkov wrote:
> On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
> > I've got limited extra capacity right now - but if Peter rebases
> > tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
> > it into -tip testing and yell if it goes wrong.
> >
>
> Ok,
On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
> I've got limited extra capacity right now - but if Peter rebases
> tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
> it into -tip testing and yell if it goes wrong.
>
Ok, I'll do that in a second.
Btw, another
* Borislav Petkov wrote:
> On Mon, Apr 15, 2013 at 05:54:15PM +0200, Borislav Petkov wrote:
> > On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
> > > It was tip:master with x86/cpu merged in freshly.
> >
> > Ok, some more observations. I can trigger some oops similar yours (I
> >
* Borislav Petkov b...@alien8.de wrote:
On Mon, Apr 15, 2013 at 05:54:15PM +0200, Borislav Petkov wrote:
On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
It was tip:master with x86/cpu merged in freshly.
Ok, some more observations. I can trigger some oops similar yours (I
On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
I've got limited extra capacity right now - but if Peter rebases
tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
it into -tip testing and yell if it goes wrong.
Ok, I'll do that in a second.
Btw, another
* Borislav Petkov b...@alien8.de wrote:
On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
I've got limited extra capacity right now - but if Peter rebases
tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
it into -tip testing and yell if it goes wrong.
On Mon, Apr 15, 2013 at 05:54:15PM +0200, Borislav Petkov wrote:
> On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
> > It was tip:master with x86/cpu merged in freshly.
>
> Ok, some more observations. I can trigger some oops similar yours (I
> haven't caught mine yet over serial or
On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
> It was tip:master with x86/cpu merged in freshly.
Ok, some more observations. I can trigger some oops similar yours (I
haven't caught mine yet over serial or such) with latest tip/master +
tip:x86/cpu.
When I remove tip:x86/cpu, the
* Borislav Petkov wrote:
> On Mon, Apr 15, 2013 at 12:08:58PM +0200, Ingo Molnar wrote:
> > It gave me the impression of memory corruption - but impressions can
> > deceive ;-)
> >
> > Anyway, not sure I can test/bisect it this week - merge window
> > preparations and all that.
>
> Ok, and
On Mon, Apr 15, 2013 at 12:08:58PM +0200, Ingo Molnar wrote:
> It gave me the impression of memory corruption - but impressions can
> deceive ;-)
>
> Anyway, not sure I can test/bisect it this week - merge window
> preparations and all that.
Ok, and also, in your oops, it said 3.9.0-rc6+ but
* Borislav Petkov wrote:
> And 0x3f76 + 0x104 gives exactly 0x407a which is the address at
> which we #PF:
>
> [ 15.921486] BUG: unable to handle kernel paging request at 407a
> [ 15.921486] IP: [<41071ab0>] __lock_acquire.isra.19+0x3e0/0xb00
>
> More hmmm...
It gave me the
* Borislav Petkov b...@alien8.de wrote:
And 0x3f76 + 0x104 gives exactly 0x407a which is the address at
which we #PF:
[ 15.921486] BUG: unable to handle kernel paging request at 407a
[ 15.921486] IP: [41071ab0] __lock_acquire.isra.19+0x3e0/0xb00
More hmmm...
It gave me
On Mon, Apr 15, 2013 at 12:08:58PM +0200, Ingo Molnar wrote:
It gave me the impression of memory corruption - but impressions can
deceive ;-)
Anyway, not sure I can test/bisect it this week - merge window
preparations and all that.
Ok, and also, in your oops, it said 3.9.0-rc6+ but
* Borislav Petkov b...@alien8.de wrote:
On Mon, Apr 15, 2013 at 12:08:58PM +0200, Ingo Molnar wrote:
It gave me the impression of memory corruption - but impressions can
deceive ;-)
Anyway, not sure I can test/bisect it this week - merge window
preparations and all that.
Ok, and
On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
It was tip:master with x86/cpu merged in freshly.
Ok, some more observations. I can trigger some oops similar yours (I
haven't caught mine yet over serial or such) with latest tip/master +
tip:x86/cpu.
When I remove tip:x86/cpu, the
On Mon, Apr 15, 2013 at 05:54:15PM +0200, Borislav Petkov wrote:
On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
It was tip:master with x86/cpu merged in freshly.
Ok, some more observations. I can trigger some oops similar yours (I
haven't caught mine yet over serial or such)
On Fri, Apr 12, 2013 at 11:47:24AM +0200, Borislav Petkov wrote:
> On Thu, Apr 11, 2013 at 10:34:48PM -0700, H. Peter Anvin wrote:
> > >The lockup went away after excluding x86/cpu. I'll try more testing
> > >as time permits.
>
> Right,
>
> so tip:x86/cpu has all in all 11 patches. Maybe a quick
On Thu, Apr 11, 2013 at 10:34:48PM -0700, H. Peter Anvin wrote:
> >The lockup went away after excluding x86/cpu. I'll try more testing
> >as time permits.
Right,
so tip:x86/cpu has all in all 11 patches. Maybe a quick bisect?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under
On Thu, Apr 11, 2013 at 10:34:48PM -0700, H. Peter Anvin wrote:
The lockup went away after excluding x86/cpu. I'll try more testing
as time permits.
Right,
so tip:x86/cpu has all in all 11 patches. Maybe a quick bisect?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my
On Fri, Apr 12, 2013 at 11:47:24AM +0200, Borislav Petkov wrote:
On Thu, Apr 11, 2013 at 10:34:48PM -0700, H. Peter Anvin wrote:
The lockup went away after excluding x86/cpu. I'll try more testing
as time permits.
Right,
so tip:x86/cpu has all in all 11 patches. Maybe a quick bisect?
I used to have one of these but have it away when cleaning out my study... no
space.
Ingo Molnar wrote:
>
>* Borislav Petkov wrote:
>
>> On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
>> > What host is this?
>>
>> Judging by the DMI string in the oops:
>>
>> > [
* Borislav Petkov wrote:
> On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
> > What host is this?
>
> Judging by the DMI string in the oops:
>
> > [ 15.921486] Pid: 73, comm: hwclock Tainted: GW3.9.0-rc6+
> > #222032 System manufacturer System Product Name/A8N-E
On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
> What host is this?
Judging by the DMI string in the oops:
> [ 15.921486] Pid: 73, comm: hwclock Tainted: GW3.9.0-rc6+
> #222032 System manufacturer System Product Name/A8N-E
it is an ASUS board with a K8 on it -
On 04/11/2013 05:09 AM, Ingo Molnar wrote:
>
> Even with this applied, the attached config is still unhappy and
> crashes/locks up
> during user-space init, see the crashlog attached below.
>
> The config has MATH_EMULATION=y, so I suspect it's the same problem category.
>
What host is
On Thu, Apr 11, 2013 at 02:09:52PM +0200, Ingo Molnar wrote:
> Even with this applied, the attached config is still unhappy and
> crashes/locks up during user-space init, see the crashlog attached
> below.
>
> The config has MATH_EMULATION=y, so I suspect it's the same problem
> category.
>
>
On Thu, Apr 11, 2013 at 02:09:52PM +0200, Ingo Molnar wrote:
Even with this applied, the attached config is still unhappy and
crashes/locks up during user-space init, see the crashlog attached
below.
The config has MATH_EMULATION=y, so I suspect it's the same problem
category.
(I'll keep
On 04/11/2013 05:09 AM, Ingo Molnar wrote:
Even with this applied, the attached config is still unhappy and
crashes/locks up
during user-space init, see the crashlog attached below.
The config has MATH_EMULATION=y, so I suspect it's the same problem category.
What host is this?
On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
What host is this?
Judging by the DMI string in the oops:
[ 15.921486] Pid: 73, comm: hwclock Tainted: GW3.9.0-rc6+
#222032 System manufacturer System Product Name/A8N-E
it is an ASUS board with a K8 on it -
* Borislav Petkov b...@alien8.de wrote:
On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
What host is this?
Judging by the DMI string in the oops:
[ 15.921486] Pid: 73, comm: hwclock Tainted: GW3.9.0-rc6+
#222032 System manufacturer System Product
I used to have one of these but have it away when cleaning out my study... no
space.
Ingo Molnar mi...@kernel.org wrote:
* Borislav Petkov b...@alien8.de wrote:
On Thu, Apr 11, 2013 at 12:26:09PM -0700, H. Peter Anvin wrote:
What host is this?
Judging by the DMI string in the oops:
t's start (oops below for
> info).
Ok, here's a fix which boots fine here in qemu. Ingo, it would be cool
if you gave it a run to verify.
Thanks.
--
>From 2263430417dd8de1a5fef4b2c40127e681fdc1ab Mon Sep 17 00:00:00 2001
From: Borislav Petkov
Date: Wed, 10 Apr 2013 21:37:03 +0200
Subject
).
Ok, here's a fix which boots fine here in qemu. Ingo, it would be cool
if you gave it a run to verify.
Thanks.
--
From 2263430417dd8de1a5fef4b2c40127e681fdc1ab Mon Sep 17 00:00:00 2001
From: Borislav Petkov b...@suse.de
Date: Wed, 10 Apr 2013 21:37:03 +0200
Subject: [PATCH] x86, FPU: Fix FPU
32 matches
Mail list logo
