Bug 26959

Summary:	All disks remounted at random times.
Product:	Mageia	Reporter:	Doug Laidlaw <laidlaws>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, fri, marja11
Version:	7	Keywords:	UPSTREAM
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	systemd-241-8.5.mga7.src.rpm	CVE:
Status comment:

Description Doug Laidlaw 2020-07-16 14:54:25 CEST

Description of problem:
This does not happen often.  I doubt ythat it would be a release blocker.  At random times during a session, all disks mounted at startup but not active, are remounted, and I am prompted for my sudo password to mount them.  Looking around the forums, others are seeing this bug.  It seems to be a problem with udev, and won't be fixed until udev is updated.  I can't find an example at present, and I couldn't identify it with an existing Mageia bug, and thought that it should be documented somewhere.

Version-Release number of selected component (if applicable):
(See above)

How reproducible:
A random effect - not under user control.

Steps to Reproduce:
1.
2.
3.

Comment 1 Morgan Leijström 2020-07-17 10:49:44 CEST

(In reply to Doug Laidlaw from comment #0)
> I doubt ythat it would be a release blocker. 

So this is Cauldron?  If so please correct Version field.

CC: (none) => fri

Comment 2 Doug Laidlaw 2020-07-17 11:27:37 CEST

No, sorry, this is 7.1.  I can test Cauldron.

Comment 3 Lewis Smith 2020-07-21 12:54:56 CEST

(In reply to Doug Laidlaw from comment #2)
> No, sorry, this is 7.1.  I can test Cauldron.
Please do.

> others are seeing this bug
> It seems to be a problem with udev, and won't be fixed until udev is updated
This is important confirmation. But how will we know if & when the udev bug is fixed?

udev is part of the systemd SRPM, for which no fixed maintainer. So assigning this globally.

Assignee: bugsquad => pkg-bugs
Source RPM: libudev1-241-8.5.mga7 (and friends.) => systemd-241-8.5.mga7.src.rpm
Keywords: (none) => UPSTREAM

Comment 4 Doug Laidlaw 2020-07-21 13:40:29 CEST

Yes, I can test with Cauldron (I am running 8-alpha as Cauldron,) but since the bug is intermittent, I can do a "soak test" only.  Where I saw it elsewhere was with an earlier kernel.

Comment 5 Aurelien Oudelet 2021-07-06 13:15:42 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 6 Doug Laidlaw 2021-07-06 13:32:35 CEST

I have not seen this happen under Mageia 8.

Comment 7 Marja Van Waes 2021-07-06 17:12:02 CEST

(In reply to Doug Laidlaw from comment #6)
> I have not seen this happen under Mageia 8.

Thanks. Closing then

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 8 Dave Hodgins 2021-07-06 20:00:01 CEST

Just fyi, (first time I noticed this bug report). The issue is caused by
pci power management.

For systems using a battery, having the power management on is a good thing
despite the remounting it causes.

For systems on AC it can be reduced by booting with the kernel parameters
pcie_port_pm=off pcie_aspm=off

In most cases having it on doesn't cause any problems except lots of syslog
messages, but on systems with devices that are slow to respond it may cause
noticeable delays.

It's a tradeoff between power saving and performance with the defaults chosen
by the kernel authors.

CC: (none) => davidwhodgins

Comment 9 Doug Laidlaw 2021-07-28 13:49:13 CEST

Thanks for the explanation, David.  My computer must be slow. An online Web form kept putting up an error message. Research said it was due to speed (or lack of it) in propagation through my browser.  In Windows 10 with Edge, I had no difficulty.  (For the lurkers, this says nothing about Windows being better.  It was simply a case of using the system the page was designed for.)