lamontjsalisbury: fail00:30
lamontandbug updated, afk for a while00:32
who_mehello. is there a known issue with kernel 4.4 that it automounts volumes without them being mentioned in fstab? The system also shows ntfs volumes as mounted but they are not09:18
who_meI've seen this using both the Xenial ISOs and by compiling the kernel using the patches in the mainline ppa09:19
apwwho_me, that would not be expected i don't think, mount decisions are almost exclusivly driven by userspace09:28
apwwho_me, where do they get mounted on?09:29
apwthe kernel would know about the volumes as it discovers them, but it has no idea where they are meant09:29
apwto be mounted, so its not clear to me how it could be responsible09:29
who_meah heck, I never checked where the mount points were. will be right to report on that. brb. reboot. will also get a dmesg to pastebin it.09:30
who_mealright, I'm on 4.4 now09:33
who_meapw, they get mounted in /media/my_user_name/random_directory_name09:34
apwwho_me, that is gvfs that decides to do that, which is a part of the login session09:35
apwthats the thing which mounts usb sticks and the like09:35
who_meyes but this does not happen with anything earlier than 4.409:35
apwthough i have not noticed it doing that spectacularly more than it did before09:35
apwso i guess we need to find out what type of volumes it is finding now it did not before09:36
who_mewith the 4.3 series and earlier it mounts volumes when I click on them in the file manager09:36
apwso, could you file a bug aginst the kernel "ubuntu-bug linux" 09:37
apwand record that info, with some clear examples of the volumes it is now mounting it did not before09:37
apwand perhaps include the output of blkid for those in 4.3 and 4.409:37
apwwho_me, what sort of physical volumes are they ?09:38
apwit is probabally something like the volumes are reporting themselves removable now09:38
apwso gnome thing thinks they are sticks you rammed in, and mounts them without checking09:38
who_meummm they are on internal SATA SSD and HDDs09:38
who_meapw, this is blkid shows: http://pastebin.com/bHTUwgpf09:41
who_mein Disks they do indeed appear as removable drives...09:42
who_meso weird09:42
apwtry this but sub in one of the drives that got mounted that you didn't expect: cat /sys/class/block/sda/removable09:43
who_mereturns "1"09:43
who_mefor some reason the kernelthinks they're removable?09:44
who_meeven my main drive shows up as removable09:45
who_meso sda, sdb, sdc, sdd, sde and sdf show up as removable09:46
who_meso yea, ubuntu bug respectfully invites me to report this upstream... oh well... will do09:49
apwwho_me, they may well be removable ... what are they connected to09:52
who_meto internal SATA connectors on the mainboard09:53
apwwho_me, which kernel version is this09:53
who_me4.4.2 but also had this happen with 4.4.009:53
smbmight be that ahci with hotswap support09:53
apwright, it may be "true" in a literal sense09:53
apwon 4.4.0-2.16 my sata drive is not removable09:54
who_meat least it did not disable the read/write caches... as far as I can tell09:55
smbapw, well don't nail me on this but at least on some boxes I think one could twiddle something in BIOS/UEFI to say a port is hotswap enabled or not09:56
who_me[sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA09:56
who_mesmb, the UEFI on this mobo has such a setting, yes09:57
who_megoing to see whether it's on or off and flip it to off if that's the case then09:58
who_mebut I think gvfs should still not automount this stuff09:58
smbwho_me, so in theory if you say yes there the disk is potentially removable 09:58
who_meanyway, brbr09:58
who_meright, that solved it for most of my drives10:07
who_methe one connected to the Marvell controlled port still shows up as removable10:07
who_mebut it's still weird, why would it do this now. No previous kernel caused this in the past :/10:17
smbmight be a "fix" even (to support now to read what the controller thinks it can handle)10:20
who_methe problem is that I can only enable or disable the Marvell controller and set its mode like AHCI, IDE or RAID. And I also would not turn off the hotswap on that because I have an eSATA disk drive which I use on and off to store things long term10:23
apwwho_me, it sounds like it needs some thought, 1) to know why the kernel now is saying they are removable, and 2) to think about if this has a knock on effect for gvfs10:27
apwwho_me, did you file a bug in the end ?  if so what was the $10:27
who_meI did, kernel bug #112681 on the kernel bugzilla10:29
ubot5bug 112681 in kdelibs (Ubuntu) "[apport] kdeinit crashed with SIGSEGV" [Undecided,Invalid] https://launchpad.net/bugs/11268110:29
ubot5bugzilla.kernel.org bug 112681 in Other "kernel marks internal drives as being removable" [Normal,New]10:29
who_meudev rule took care of the drive connected to Marvell controller...11:13
zkandaHello, anyone here can help me debug my sound card issue? I hear static noise for Ubuntu while this is not present in windows.11:34
Madkissapw: Are you there? We're getting back to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948 once again13:10
ubot5Launchpad bug 1505948 in linux (Ubuntu Wily) "Memory arena corruption with FUSE (was Memory allocation failure crashes kernel hard, presumably related to FUSE)" [High,Confirmed]13:10
bjfhallyn, can you verify LP: #1539349 for wily15:28
ubot5Launchpad bug 1539349 in linux (Ubuntu Wily) "sleep from invalid context in aa_move_mount" [Undecided,Fix committed] https://launchpad.net/bugs/153934915:28
hallynbjf: ok16:12
lamontjsalisbury: ready for another kernel, though I expect it;ll be 5 or 6 hours before I can test it16:28
jsalisburylamont, good timing, I'm building it now.  I'll post it to the bug when it's ready16:28
lamontjsalisbury: the lxc where I do 99% of my testing for the actual core-work is on the machine that I have to reboot each time to test this, so it's frequently blocked by EBUSY_PRIMARY_WORKSURFACE16:30
jsalisburylamont, gotcha16:30
rtg_kamal, this bug fix might be suitable for stable for all our kernels: https://bugs.launchpad.net/bugs/154720720:58
ubot5Error: Could not gather data from Launchpad for bug #1547207 (https://launchpad.net/bugs/1547207). The error has been logged20:58
rtg_bug #154720720:59
kamalrtg_, already applied to all of our stable kernels :-)21:02
kamalrtg_, ... and pending in all of the Ubuntu master-next branches21:04
rtg_kamal, cool21:04
rtg_kamal, I don't see it pending in precise master-next21:06
kamalrtg_, you're right -- I'll see if it applies21:44
rtg_kamal, it does, I was just about to email out the patch21:45
kamalrtg_, in that case, I'll ack it21:45
kamalrtg_, you marked the bug "Fix Released" for T, V, W, and X, but its actually only "Fix Committed" for all of those (except X? i dunno)21:48
rtg_kamal, I guess they'll be fix released soon enough21:49
* kamal looks the other way ;-)21:49
rtg_kamal, good move21:49
rtg_kamal, what about utopic ?21:50
kamalrtg_, yeah, just looking at that21:50
kamalrtg_, its "Fix Committed" in trusty/lts-backport-utopic-next21:50
argeskamal: did a cat jump on your laptop?22:30
lamontjsalisbury: fail, updating the bug22:32
kamalbut now everyone knows my password!  ;-)22:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!