On Thu, December 3, 2015 11:19 am, Jonathan Billings wrote:
> On Thu, Dec 03, 2015 at 04:46:10PM +0000, Duncan Brown wrote:
>> Here is a couple of pictures,
>>
>> http://i.imgur.com/Vqvqn1H.jpg
>> http://i.imgur.com/WQaz1j9.png
>>
>> Any use?
>
> So, both of those are just the end of the kernel call trace,
> unfortunately, it doesn't show what function actually caused the
> panic. That'd be above that text, something you could get from an
> attached console.
That is my main complaint about parallelized boot. My brain is only
capable to deal with serial sequence of events, and which next event is
deterministically predictable from previous. As with fatal things like
kernel panic, it is the previous before the fatalstep is the one that you
still can see...
It there some way to tell systemd kick in components serially?
Severs aside (you can not have everything), this (CentOS 7) is a great
system for laptops, the best I saw so far. Like machintosh. Only better.
Valeri
>
> The first one looks like its in the middle of allocating an inode for
> a file, the second in looking up some dentry during init (just
> guessing though), although both seem to be in an allocation event at
> the end of an interrupt (EOI), but that's probably just coincidence.
> --
> Jonathan Billings <billings@xxxxxxxxxx>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
