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  linux-hardening  linux-cve-announce  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]
Message-ID: <20131014224333.GG13538@localhost.localdomain>
Date:	Tue, 15 Oct 2013 00:43:36 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Knut Petersen <Knut_Petersen@...nline.de>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>, Greg KH <greg@...ah.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG 3.12.rc4] Oops: unable to handle kernel paging request
 during shutdown

On Tue, Oct 15, 2013 at 12:31:34AM +0200, Knut Petersen wrote:
> On 14.10.2013 23:51, Frederic Weisbecker wrote:
> >Also knut, do you have a serial line?
> Yes, if really necesarry .... I´d prefer network

Hmm, you can try but it might not be working correcty after the fault.

> 
> >
> >If so may be looking at the timer events may help. Could you try to enable the following
> >timer events?
> >
> >       echo 1 > /sys/kernel/debug/tracing/events/timer/timer_cancel
> >       echo 1 > /sys/kernel/debug/tracing/events/timer/timer_expire_entry
> >       echo 1 > /sys/kernel/debug/tracing/events/timer/timer_expire_exit
> >       echo 1 > /sys/kernel/debug/tracing/events/timer/timer_init
> >       echo 1 > /sys/kernel/debug/tracing/events/timer/timer_start
> >
> >And also enable ftrace_dump_on_oops:
> >
> >       sysctl kernel.ftrace_dump_on_oops=1
> I assume you forgot .../enable several times ?!

Oops, sorry yep.

> 
> echo 1 > /sys/kernel/debug/tracing/events/timer/timer_cancel/enable
> echo 1 > /sys/kernel/debug/tracing/events/timer/timer_expire_entry/enable
> echo 1 > /sys/kernel/debug/tracing/events/timer/timer_expire_exit/enable
> echo 1 > /sys/kernel/debug/tracing/events/timer/timer_init/enable
> echo 1 > /sys/kernel/debug/tracing/events/timer/timer_start/enable
> sysctl kernel.ftrace_dump_on_oops=1
> 
> I added that to /etc/init.d/boot.local

Thanks! Now lets cross the fingers :)

> 
> 
> >
> >We may have some interesting clues about who manipulated the timer list last before
> >the oops happened.
> >
> >Thanks!
> >
> 
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ