lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 1 Dec 2010 20:35:08 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Tobias Karnat <tobias.karnat@...glemail.com>
Cc:	linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: edac_core: crashes on shutdown

On Wed, Dec 01, 2010 at 06:46:54PM +0100, Tobias Karnat wrote:
> Am Mittwoch, den 01.12.2010, 15:33 +0100 schrieb Borislav Petkov:
> > Unfortunately, this is still incomplete because it is missing the Code: tag and
> > the end trace tag which looks like this
> > 
> > ---[ end trace ... ]---
> > 
> > and this is most probably so because we're halting and cannot print out
> > all the oops. Two things you can do:
> > 
> > 1. Connect the machine to another machine over serial- or netconsole.
> > Google for instructions how.
> > 
> > 2. If you can't do 1. you can try enabling CONFIG_BOOT_PRINTK_DELAY and
> > boot the kernel with 'boot_delay=10', for example, so that a 10ms delay
> > is inserted after each printk line. This might let us see more on the
> > console before halt and catch the whole oops.
> > 
> > Thanks.
> 
> Yes, boot_delay=10 has helped and I also removed the nvidia driver:
> 
> http://oi56.tinypic.com/eas0pg.jpg

Hmm, I see two backtraces now. I'm still not sure whether the first
one is actually the first one that happens since it is cut off at the
beginning.

If it is the first one, it should contain something like

[ ... ] Pid: ... , comm: ... Not tainted <kernel version> <DMI system name>

the important part being the "Not tainted" string. Can you check that
please?

Also, can you disable the EDAC subsystem in Kconfig and retry?
I'm trying to rule out some other issue since the backtraces are
inconclusive wrt EDAC.

Thanks.

-- 
Regards/Gruss,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists