Shutdown is supposed to terminate all processes/threads so it's probably not about the watchdog daemon. It sounds more like the classic distro was disabling the hardware watchdog during shutdown and your new distro doesn't do that. Try comparing the kernel watchdog drivers in the two distros because that's the most likely culprit.
=== ALAN LEVY, Lead Consultant, Embedded Systems Plextek Consulting, The Plextek Building, London Road, Great Chesterford, Saffron Walden, CB10 1NY, UK T: +44 (0) 1799 533200 E: alan.l...@plextek.com W: www.plextek.com -----Original Message----- >Date: Mon, 15 Jan 2018 16:39:40 +0100 >From: Ryan Meulenkamp <ryan.meulenk...@nedap.com> >To: yocto@yoctoproject.org >Subject: [yocto] Halt problem >Message-ID: <f635d9dd-76fb-fc81-5dc0-fda98d50f...@nedap.com> >Content-Type: text/plain; charset=utf-8; format=flowed > >Hi y'all, > >I ran into a problem using shutdown -h (or halt) on an openembedded-core > (yocto) distro running on the Atmel at91sam9g45. > >We used to run an openembedded-classic (angstr?m) based OS with kernel version >2.6.35.14+. Here, halting the system would cause it to shutdown without >resetting, or >turning the power off, to await a manual reset. > >Now we are building a new distro based on openembedded-core and yocto. >Halting the system now causes a watchdog intervention. I tried all different >arguments for both the shutdown and the halt command. It looks if though the >classic based >distro left the watchdog daemon running during a halt. > >What could be the cause of this problem? In what direction should I look (e.g. >kernel config, sysvinit config, openembedded config, processor specific code >etc.)? > >I'm not sure if this is the right mailing list to ask this question, but I >guess one of you could point me in the right direction. > >Thanks in advance and kind regards, > >Ryan Meulenkamp -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
