On Wed 2018-07-04 14:41:08, Meelis Roos wrote:
> I tried 4.18.0-rc1-00023-g9ffc59d57228 and now 
> 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other 
> 32-bit machines, and got half-failed bootup - kernel and userspace come 
> up but some services fail to start, including network and 
> systemd-journald:
> 
> systemd-journald[85]: Assertion 'clock_gettime(map_clock_id(clock_id), &ts) 
> == 0' failed at ../src/basic/time-util.c:53, function now(). Aborting.
> 
> I then tried multiple other machines. All x86-64 machines seem 
> unaffected, some x86-32 machines are affected (Athlon with AMD750 
> chipset, Fujitsu RX100-S2 with P4-3.4, and P4 with Intel 865 chipset), 
> some very similar x86-32 machines are unaffected. I have different 
> customized kernel configuration on them, so far I have not pinpointed 
> any configuration option to be at fault.
> 
> All machines run Debian unstable.
> 
> 4.17.0 was working fine.
> 
> Will continue with bisecting between 4.17.0 and 
> 4.18.0-rc1-00023-g9ffc59d57228.

I don't think if it helps you, but 4.18-rc4 seems to work okay for me
(and previous versions did, too) on thinkpad X60.

But I'm using older debian version.

                                                                        Pavel
                                                                        
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachment: signature.asc
Description: Digital signature

Reply via email to