> Gulp. Let's hope that nothing in mm_init() requires that trap_init()
> has been run. What happens if something goes wrong during mm_init()
> and the architecture attempts to raise a software exception, hits a bus
> error, div-by-zero, etc, etc? Might there be hard-to-discover
> dependencies in
Hi Pavel,
FYI here is 0day's bisect result. The attached dmesg has reproduce
script at the bottom.
[27e2ce5dba4c30db031744c8140675d03d2ae7aa] mm: access to uninitialized struct
page
git://git.cmpxchg.org/linux-mmotm.git devel-catchup-201805041701
git bisect start 53eff77ad4b0adaf1ca6e1ecc6acf38
On Fri, May 4, 2018 at 7:03 PM, Pavel Tatashin
wrote:
> Thank you, I will try to figure out what is happening.
+1 is here.
The last message I have seen on the console are:
[4.690972] Non-volatile memory driver v1.3
[4.703360] Linux agpgart interface v0.103
[4.710282] loop: module lo
Thank you, I will try to figure out what is happening.
Pavel
On 05/04/2018 12:01 PM, Andrei Vagin wrote:
> On Fri, May 04, 2018 at 12:47:53PM +, Pavel Tatashin wrote:
>> Hi Andrei,
>>
>> Could you please provide me with scripts to reproduce this issue?
>
> I boot this kernel in a kvm virtual
On Fri, May 04, 2018 at 12:47:53PM +, Pavel Tatashin wrote:
> Hi Andrei,
>
> Could you please provide me with scripts to reproduce this issue?
I boot this kernel in a kvm virtual machine. The kernel is built without
modules. A config file is attahced.
Here is a qemu command line what I use t
On Fri, 04 May 2018 12:47:53 +
Pavel Tatashin wrote:
> Hi Andrei,
>
> Could you please provide me with scripts to reproduce this issue?
>
>
And the config that was used. Just saying that the commit doesn't boot
isn't very useful.
-- Steve
Hi Andrei,
Could you please provide me with scripts to reproduce this issue?
Thank you,
Pavel
On Fri, May 4, 2018 at 4:27 AM Andrei Vagin wrote:
> Hello,
> We have a robot which runs criu tests on linux-next kernels.
> All tests passed on 4.17.0-rc3-next-20180502.
> But the 4.17.0-rc3-next-2
Hello,
We have a robot which runs criu tests on linux-next kernels.
All tests passed on 4.17.0-rc3-next-20180502.
But the 4.17.0-rc3-next-20180504 kernel didn't boot.
git bisect points on this patch.
On Thu, Apr 26, 2018 at 04:26:19PM -0400, Pavel Tatashin wrote:
> The following two bugs were
On Mon, 30 Apr 2018 19:58:58 -0400 Steven Rostedt wrote:
> On Mon, 30 Apr 2018 16:26:58 -0700
> Andrew Morton wrote:
>
> > On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
> > wrote:
> >
> > > The following two bugs were reported by Fengguang Wu:
> > >
> > > kernel reboot-without-warning i
On Mon, 30 Apr 2018 16:26:58 -0700
Andrew Morton wrote:
> On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
> wrote:
>
> > The following two bugs were reported by Fengguang Wu:
> >
> > kernel reboot-without-warning in early-boot stage, last printk:
> > early console in setup code
> >
> > htt
On Thu, 26 Apr 2018 16:26:19 -0400 Pavel Tatashin
wrote:
> The following two bugs were reported by Fengguang Wu:
>
> kernel reboot-without-warning in early-boot stage, last printk:
> early console in setup code
>
> http://lkml.kernel.org/r/20180418135300.inazvpxjxowog...@wfg-t540p.sh.intel.com
The following two bugs were reported by Fengguang Wu:
kernel reboot-without-warning in early-boot stage, last printk:
early console in setup code
http://lkml.kernel.org/r/20180418135300.inazvpxjxowog...@wfg-t540p.sh.intel.com
And, also:
[per_cpu_ptr_to_phys] PANIC: early exception 0x0d
IP 10:fff
12 matches
Mail list logo
