Re: 3.13.0: crash on boot

2014-02-07 Thread Borislav Petkov
On Fri, Feb 07, 2014 at 09:26:18PM +0400, Alexandra N. Kossovsky wrote: > On Feb 07 15:44, Borislav Petkov wrote: > > On Fri, Feb 07, 2014 at 01:00:45PM +0400, Alexandra N. Kossovsky wrote: > > > > Btw, did this box boot any kernels successfully in EFI mode at all? > > > > > > Yes. It booted, for

Re: 3.13.0: crash on boot

2014-02-07 Thread Borislav Petkov
On Fri, Feb 07, 2014 at 01:00:45PM +0400, Alexandra N. Kossovsky wrote: > I asked. He installed an update. No difference. Ok. > > Btw, did this box boot any kernels successfully in EFI mode at all? > > Yes. It booted, for example, the same 3.13 kernel from Debian - without > debug options. H

Re: 3.13.0: crash on boot

2014-02-04 Thread Borislav Petkov
On Tue, Feb 04, 2014 at 05:30:50PM +0400, Alexandra N. Kossovsky wrote: > On Feb 03 14:41, Matt Fleming wrote: > > Alexandra, any chance you could try out a v3.14-rc1 kernel? Basically > > all of the EFI memory mapping code was rewritten for v3.14. > > v3.14-rc1: kmemleak complains about acpi code

Re: 3.13.0: crash on boot

2014-02-03 Thread Borislav Petkov
On Mon, Feb 03, 2014 at 02:41:20PM +, Matt Fleming wrote: > On Fri, 31 Jan, at 11:29:39AM, Bjorn Helgaas wrote: > > [+cc Matt and Matthew; maybe EFI related?] > > (Pulling in Borislav too) > > Yeah, looks EFI related. > > > On Fri, Jan 31, 2014 at 1:37 AM, Alexandra N. Kossovsky > > wrote:

Re: 3.13.0: crash on boot

2014-02-03 Thread Matt Fleming
On Fri, 31 Jan, at 11:29:39AM, Bjorn Helgaas wrote: > [+cc Matt and Matthew; maybe EFI related?] (Pulling in Borislav too) Yeah, looks EFI related. > On Fri, Jan 31, 2014 at 1:37 AM, Alexandra N. Kossovsky > wrote: > > Hello. > > > > I've got 3.13.0 kernel creshed on boot. A lot of debug opti

Re: 3.13.0: crash on boot

2014-01-31 Thread Bjorn Helgaas
[+cc Matt and Matthew; maybe EFI related?] On Fri, Jan 31, 2014 at 1:37 AM, Alexandra N. Kossovsky wrote: > Hello. > > I've got 3.13.0 kernel creshed on boot. A lot of debug options are on. > Crash: > BUG: unable to handle kernel paging request at 00012a53f020 > IP: [] 0xcf