linux-kernel - Re: [PATCH 00/12] rtc: omap: fixes and power-off feature

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: <20141022102305.GM2113@localhost>
Date:	Wed, 22 Oct 2014 12:23:05 +0200
From:	Johan Hovold <johan@...nel.org>
To:	Felipe Balbi <balbi@...com>
Cc:	Johan Hovold <johan@...nel.org>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Tony Lindgren <tony@...mide.com>,
	Benoît Cousson <bcousson@...libre.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lokesh Vutla <lokeshvutla@...com>,
	Guenter Roeck <linux@...ck-us.net>,
	Colin Foe-Parker <colin.foeparker@...icpd.com>, nsekhar@...com,
	t-kristo@...com, j-keerthy@...com, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/12] rtc: omap: fixes and power-off feature

On Wed, Oct 15, 2014 at 12:08:32PM -0500, Felipe Balbi wrote:
> On Wed, Oct 15, 2014 at 07:06:28PM +0200, Johan Hovold wrote:
> > On Wed, Oct 15, 2014 at 11:55:02AM -0500, Felipe Balbi wrote:

> > > BTW, how do you test this series ?
> > 
> > Set a 30 second wakealarm using the sysfs attribute of the rtc class
> > device and power off the BBB:
> > 
> > 	echo +30 >wakealarm; poweroff
> 
> sweet!!!! It worked just fine :-)

:)

> Too bad there's yet another DRM bug:
> 
> [  271.150158] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
> [  271.150158] 
> [  271.159725] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 3.17.0-08392-g7fe2269-dirty #326
> [  271.168567] [<c00175a4>] (unwind_backtrace) from [<c00132f0>] (show_stack+0x20/0x24)
> [  271.176668] [<c00132f0>] (show_stack) from [<c06573a4>] (dump_stack+0x8c/0xa4)
> [  271.184215] [<c06573a4>] (dump_stack) from [<c0654f10>] (panic+0xa0/0x220)
> [  271.191405] [<c0654f10>] (panic) from [<c0049e54>] (do_exit+0x974/0x9d0)
> [  271.198410] [<c0049e54>] (do_exit) from [<c0067694>] (SyS_reboot+0x14c/0x1e8)
> [  271.205870] [<c0067694>] (SyS_reboot) from [<c000f080>] (ret_fast_syscall+0x0/0x48)
> [  271.214023] drm_kms_helper: panic occurred, switching back to text console
> [  271.221312] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
> 
> In any case, board still powered up after 30 seconds(-ish). So this gets
> a:
> 
> Tested-by: Felipe Balbi <balbi@...com>

Thanks for testing. I didn't include your Tested-by in v2 due to the
invasiveness of the new device-abstraction patch. Still works fine on BBB
here though.

Johan
--
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/