I'm not sure why you were getting those errors, but definitely stop the
udisks service. Your blktrace shows it being accessed by the "pool"
task. For some silly reason, the glib thread pool library that udisks
uses decides to rename its threads to "pool" instead of the application
name.
With udi
If you want to get more information about what's happening at the USB
level, you should use usbmon (see Documentation/usb/usbmon.txt in the
kernel source for instructions). It will tell you what commands are
being sent to the drive, but not which program is responsible for
sending them. Still, yo
so far the feeling is that
-) 3.14 seems to support this drive better, as it appears to be able to
retrieve its power status and to, more importantly, set it, unlike the previous
kernel (4.4-)
-) 3.14 seems to be also more invasive. Previously, hdparm -C would return some
error, but never wake
Seems that with the new kernel the disk stays awake and never even tries
to go standby:
http://codepad.org/lIRqEBOW
Edit:
i did stop this script for a while, and the disk went to sleep (not standby,
but i think suspend or more. The drive was not only spun down, but the light
was blinking, so s
It wouldn't be surprising to find that udisks2 is the program waking up
your drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage noti
Spoke too early, drive just woke up out of the blue, after having been
manually unmounted in nautilus, and forced to standby with hdparm -y
(now that it works), without me re-mounting it or anything.
dmesg does not report anything relevant:
[ 641.041831] EXT4-fs (sde1): mounted filesystem with or
Trying 4.14.4 ((from mainline debs).
So far it looks promising: Hdparm seems now able to also query/set the status
(before it was returning an error with this drive), and it's about one H since
i forced it to standby and the drive is staying in standby.
--
You received this bug notification bec
working on it, but i was also thinking: The same value is returned in 14.04.
Can it be that 16.04 kernel does not honor that value and keeps polling at a
10minute interval?
these driver sense error always come up at a 600secs interval, and they
are definitely generated by the same process that al
first finding:
cat /sys/block/sdb/events_poll_msecs
-1
will now proceed testing a newer kernel to check if the problem has been
fixed in the meanwhile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Thank you Alan, for providing these valuable info.
Actually i noticed the polling by looking at dmesg. I suspected that the errors
in my distribution's kernel (4.4.0 in 16.04) were somehow related to a kernel
polling process with a default of 10 minutes.
I will try to do both things you suggest:
I have no idea which kernel versions Ubuntu uses in its releases, but
the recurring Hardware Error bug should be fixed in the 4.14 kernel. At
least I think it should -- nobody has reported on whether the fix
actually works, so I have no way of knowing.
As for the drive spontaneously waking up...
Ok, i think i gathered some relevant evidence.
I had the drive plugged on a 16.04, and at some point i noticed it went standby
(led blinking intermittently).
Last dmesg lines were [ 6217.720607] perf interrupt took too long (5053 >
5000), lowering kernel.perf_event_max_sample_rate to 25000
[ 663
also, on 16.04, in addition to the above messages, the drive not only
does not go to standby (with the led blinking regularly), but it also
does not spin down. Tested with 3 different 16.04 (2 ubuntus and one kde
neon) on 2 different systems
--
You received this bug notification because you are a
and, by the way, this is the kind of messages that flood dmesg:
[ 118.189091] sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
[ 118.189101] sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
[ 118.189106] sd 7:0:0:0: [sdc] tag#0 Add. S
Updated the description: I tested with 14.04 and as expected everything
goes to sleep when it should and stays sleeping.
I have the serious fear this is a regression in the kernel SATA subsystem.
HOWEVER, i'm willing to test it more on 16.04.
Could someone point me at a super stripped-down versio
can it be related to
https://bugzilla.redhat.com/show_bug.cgi?id=1351305#c36 ?
** Bug watch added: Red Hat Bugzilla #1351305
https://bugzilla.redhat.com/show_bug.cgi?id=1351305
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Ok, so i managed to start btrace when i saw the disk sleeping and stopped after
it woke up:
http://paste.ubuntu.com/26128577/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted
oh, and 14.04 disks stay mounted (just not accessed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage notifications about this bug go to:
to compare, this is what i got on the 14.04 where unmounted HDs stay
standby
http://paste.ubuntu.com/26128324/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wak
Thank you for the suggestion!
So i tried it out, on the unmounted usb drive, and this is what i got:
http://paste.ubuntu.com/26128246/
the fear is that it might not (only) be some userspace daemon to keep the drive
alive..
But it doesn't seem to me that it is easy to understand what's going on,
You can use blktrace to see who is accessing the drive. My first
suspect would be udisksd so you might try killing that process and see
if that makes it go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Brian, that doesn't seem a nautilus issue
** Package changed: nautilus (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To mana
Nobody that is able to even reproduce this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage notifications about this bug go to:
https://
** Tags added: xenial
** Package changed: ubuntu => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage notifications abo
yes, of course there's no source package to blame. Or, at least, i donno
which one it would be..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
T
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
26 matches
Mail list logo
