On Tue, Jan 10, 2017 at 2:45 PM, François Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx> wrote: > Le 10/01/2017 05:44, Chris Murphy a écrit : >> On Mon, Jan 9, 2017 at 11:54 AM, François Patte >> <francois.patte@xxxxxxxxxxxxxxxxxxxx> wrote: >> >>> janv. 09 19:26:12 bhaskara systemd[1]: Stopped /dev/dm-5. >>> janv. 09 19:26:12 bhaskara systemd[1]: Stopped >>> /sys/devices/virtual/block/dm-5. >>> janv. 09 19:26:12 bhaskara blkdeactivate[10933]: [DM]: deactivating >>> crypt device luks-63be2188-bd3d-4552-9a8b-9481d942fb46 (dm-5)... done >>> janv. 09 19:26:12 bhaskara kernel: md122: detected capacity change from >>> 42951770112 to 0 >>> janv. 09 19:26:12 bhaskara kernel: md: md122 stopped. >>> janv. 09 19:26:12 bhaskara kernel: md: unbind<sdb2> >>> janv. 09 19:26:12 bhaskara kernel: md: export_rdev(sdb2) >>> janv. 09 19:26:12 bhaskara kernel: md: unbind<sda2> >>> janv. 09 19:26:12 bhaskara kernel: md: export_rdev(sda2) >>> janv. 09 19:26:12 bhaskara kernel: BUG: unable to handle kernel paging >>> request at ffff8f3f29ea8000 >> >> OK well it's a kernel bug, seems like to me. The simplest thing to do >> is try a different kernel. But which one? I'm not seeing immediately >> relevant patches for md in either 4.8.16 or 4.8.17. What kernel >> version are you using now? If it's 4.18.15, sure you can try either >> 4.18.16 (which is in updates-testing) or you can get 4.8.17 from koji. >> Looks like 4.9.2 is building now in koji and should be done shortly so >> you could also try that one. > > I use 4.8.15 and 4.8.16 is not yet in the update reposirory. > >> >> If it reproduces with 4.9.2, for sure you should try to get more >> information. If you can ssh into the system remotely so you can get a >> complete dmesg that'd be useful. If ssh gets killed off before the >> bug, then you might see if any of these ideas will get you more >> information on the nature of the failure. >> >> https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 > > This bug appears randomly: today, I could shutdown my machine normaly > (almost normaly: sysstemd try to write on journactl while /var is > unmounted.... for instance). > > I don't undersstand why these things are going backward: I have a fedora > 21 install which boot and shutdown without problems and systemd is > running on this machine. This class of bug is called a regression. They're extremely common. And Fedora having generally newer packages, is inevitably going to get hit with some portion of these. Par for the course. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
