Re: [X86] Looking for x86-related fires

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 06, 2018 at 07:51:18PM -0400, Jeff Backus wrote:
> On Fri, Jul 6, 2018 at 6:32 PM, Jeff Backus <jeff.backus@xxxxxxxxx> wrote:
> 
> > On Thu, Jul 5, 2018 at 5:47 PM, Jeff Backus <jeff.backus@xxxxxxxxx> wrote:
> >
> >>
> >> On Thu, Jul 5, 2018 at 5:07 PM, Zbigniew Jędrzejewski-Szmek <
> >> zbyszek@xxxxxxxxx> wrote:
> >>
> >>>
> >>> Might be a problem in systemd code to select clock type
> >>> (monotonic/realtime/etc.).
> >>> You can try taking an older image, and compiling systemd, and running
> >>> the tests.
> >>> Even something as simple as
> >>>   sudo dnf build-dep systemd
> >>>   git clone https://github.com/systemd/systemd
> >>>   cd systemd
> >>>   meson -Dman=false build && ninja -C build && ninja -C build test
> >>>
> >>> If that passes, then the next step would be to take that older image,
> >>> install just the newer kernel, and repeat the tests.
> >>>
> >>> Zbyszek
> >>>
> >>
> >>
> > Here's a quick update, since I may not be able to get back to this until
> > early next week. I was able to build the version of systemd that is in the
> > master branch of the GH repo, SHA: 8255430. All tests that were executed
> > pass under kernel 4.16.16-300. About 10 tests were skipped. The following
> > skipped tests seem to be of particular interest:
> > * test-udev
> > * test-boot-timestamps
> >
> > I was able to insert an "assert_se(1==0)" after the line that triggered
> > the assertion when booting from the installer, and numerous tests fail. So
> > that code is at least getting exercised.
> >
> > Installed the latest version of the kernel available for F28, 4.17.3-200,
> > and test results were the same. I am now trying to build 4.18.0-0.rc3,
> > since that appears to be the latest version in rawhide.
> >
> 
> I updated to 4.18.0-0.rc3 and the problem showed up. I didn't have long to
> glance at the logs, but I am seeing the systemd segfault related to udev.
> This is with whatever version my F28 system had installed, not the version
> I compiled from GH. So, looks like an issue in the kernel. I'll try to
> extract more info from the journal when I get a chance. Are there any boot
> options, etc. that would produce additional helpful info?

See https://www.freedesktop.org/wiki/Software/systemd/Debugging/.

Zbyszek
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx/message/OCLEH53BOB7Y23CTQJHHWAOA2QBLMOX4/




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux