[09:37] <denlud> Hey Guys
[09:37] <denlud> Can somebody tell me why the Option CONFIG_MMC_UNSAFE_RESUME cant be set in new kernels? (4.0+)
[09:39] <denlud> I want to bind my sd card as /home, but then my laptop cant use suspend. The solution for people with an older kernel was this Option. Now it doesnt exist anymore.
[09:40] <apw> denlud, well from the name UNSAFE does not sound that positive
[09:40] <apw> denlud, did you have some kind of kernel command line override to enable that mode ?
[09:40] <denlud> It declares a SD Card as unremoveable.
[09:41] <denlud> Its only unsafe, if you change your sd cards.
[09:41] <ogra_> i think yoiu can enforce that from userspace somehow
[09:41] <amitk> denlud: that behaviour became the default IIRC from chatting to the MMC maintainer and so the option went away
[09:41] <apw> as being allowed to be, but ... does the option have an override to opt-in, otherwise that is a risky proposition
[09:42] <denlud> It becomes default?
[09:42] <denlud> But my /home isnt working after suspend....
[09:42] <apw>    - CONFIG_MMC_UNSAFE_RESUME=y is now default behavior
[09:42] <apw> cirtianly the changelogs imply the option became the default which fits amitk's memory
[09:42] <amitk> yes
[09:43] <amitk> denlud: and here is a line from his his weekly report to me:
[09:43] <amitk> * Submitted a new version of the patchset that makes MMC_UNSAFE_RESUME
[09:43] <amitk> default behaviour.
[09:43] <denlud> Ok, but it isnt working....
[09:44] <denlud> What should i try anymore....i already tried alot :(
[09:44] <amitk> denlud: try talk to ulfh on #linaro-kernel
[09:44] <ogra_> https://www.kernel.org/doc/menuconfig/drivers-mmc-core-Kconfig.html
[09:44] <ogra_> This option sets a default which can be overridden by the
[09:44] <ogra_> module parameter "removable=0" or "removable=1".
[09:45] <apw> i think that may no longer exist
[09:45] <ogra_> (now dont ask me how to set it if there is no module :P )
[09:45] <denlud> But that was my Question.....:D
[09:45] <ogra_> did you dig in sysfs ?
[09:46] <denlud> dig in sysfs? Sorry i am a Linux Beginner...
[09:47] <ogra_> find /sys -name '*removable*'
[09:47] <ogra_> check if there is anything mmc related
[09:48] <ogra_> aha ... so it seems there is a cmdline option:
[09:48] <ogra_> mmc_core.removable=0
[09:48] <ogra_> add that to youir kernel commandline 
[09:49] <ogra_> and see if that fixes it
[09:49] <denlud> yes that could be the solution!!
[09:50] <denlud> If that fixes my Problem, i love you ogra_ :D You dont know what i already make to get my /home work...
[09:50] <apw> denlud, that option no longer exists in later kernels
[09:50] <apw> it was removed when the option was set to =y and removed
[09:50] <denlud> really?
[09:51] <apw> yes
[09:51] <ogra_> how mean
[09:51] <apw> not really, i think your sysfs thing is worth persuing
[09:51] <apw> as the kernel behaves different depending how the card is marked removable/not
[09:51] <apw> but the unsafe toggle for all cards is gone
[09:52] <apw> as many machines using it have two slots one inside which is not-removable and one outside which is
[09:52] <apw> so they need both semantics, different per card
[09:52] <apw> whether you can lie to the kernle and say your external card is "not-removable" less easy to tell
[09:52] <apw> on quick inspection
[09:52] <apw> it's you arm types who have made this this way :)
[09:53] <denlud> I dont get why my SD Card isnt working, and my internal space is working. They are both MMC's.
[09:53] <denlud> Oh ok, apw...
[09:53] <ogra_> ubuntu@localhost:~$ find /sys -name '*removable*'|grep mmcblk1
[09:53] <ogra_> find: ‘/sys/kernel/debug’/sys/devices/platform/soc/7864900.sdhci/mmc_host/mmc1/mmc1:1234/block/mmcblk1/removable
[09:53] <ogra_> so seems on systems with mmc i have such a sysfs node
[09:54] <denlud> dennis@Yoda:~/kernel/linux-source-4.4.0$  find /sys -name '*removable*'|grep mmcblk1
[09:54] <denlud> find: "/sys/kernel/debug"/sys/devices/pci0000:00/0000:00:12.0/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1/removable
[09:54] <denlud> : Keine Berechtigung
[09:54] <ogra_> find the equivalent on your system and make sure the content is "0"
[09:55] <ogra_> well, if mmcblk1 is your mmc device ... else your command needs to filter "mmcblk0"
[09:56] <denlud> my working mmc device is mmcblk0 (the internal space)
[09:56] <ogra_> so:  find /sys -name '*removable*'|grep mmcblk0
[09:56] <apw> shoving a card in mine it is marked non-removable ... so i'd kinda expect that work be ok
[09:56] <apw> would
[09:56] <apw> but perhaps that is a lie from my bios or something, hmmmm
[09:58] <denlud> find: "/sys/kernel/debug"/sys/devices/pci0000:00/0000:00:12.0/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1/removable
[09:58] <denlud> how can i lie to my kernel now, and say its non removeable?
[09:58] <denlud> I dont get it sorry...
[10:01] <ogra_> why do you look at mmcblk1 ?
[10:02] <ogra_> (you said above it is mmcblk0)
[10:03] <denlud> No, the already working mmc is mmcblk0
[10:03] <denlud> home "is" mmcblk1
[10:04] <apw> denlud, what sort of machine is this ...
[10:04] <denlud> Its a Lenovo 100s
[10:04] <denlud> and it only has 32Gb internal space. 14" version
[10:04] <apw> denlud, and is the mmcblk0 "inside" and mmcblk1 a removable slot ?
[10:04] <denlud> Yes.
[10:07] <apw> and when you s/r what happens to your card goes into error or something ?
[10:08] <denlud> https://forum.ubuntuusers.de/topic/sd-karte-home-wird-falsch-behandelt/
[10:08] <denlud> Here I posted all outputs.
[10:08] <denlud> Dont want to post It here, its very much...
[10:09] <apw> yep
[10:09] <apw> well on a cursory examination i cannot actually see a way to override the behaviour, it seems to be defined
[10:10] <apw> by the machine definition telling the slot whether it is removable, and if it is, it gets zapped on s/r
[10:10] <denlud> My second output I posted there was after suspend, when my /home isnt working anylonger. And the programs are already crashed
[10:11] <denlud> So I must try a flipping of the bios removeable bit?
[10:13] <apw> denlud, i am not sure you would even have such a setting, you might, but ...
[10:13] <apw> though the description implies the card should be handled as if the old UNSAFE is set, so i am not sure
[10:14] <apw> why this is not working as one would expect, i guess some later change
[10:14] <denlud> http://apple.stackexchange.com/questions/113202/can-i-mark-a-sd-card-as-permanent-storage
[10:15] <denlud> Oh, that is for apple. I thought if it would be for windows. I can install Windows. flipping the bit in the BIOS, install Linux and be happy.
[10:19] <denlud> Seems like I have to give my Laptop back...
[10:20] <denlud> Or should i try flipping the BIOS non removeable bit? pci0000:00/0000:00:12.0/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1/removable
[10:23] <apw> denlud, i have no idea if that is even the right kind of bit as that is marked non-removable already ... right, it is 0
[10:25] <denlud> dennis@Yoda:~/kernel/linux-source-4.4.0$ cat /sys/devices/pci0000:00/0000:00:12.0/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1/removable
[10:25] <denlud> 0
[10:26] <apw> this descrption still says that the kernel should be behaving as it was with unsafe set, which should work
[10:26] <apw> ie the card should just be being s/r as well
[10:27] <denlud> You think the problem must be somewhere else?
[10:28] <apw> it feels like the card is not handling s/r well
[10:28] <apw> i wonder if i can confirm that here somehow ...
[10:30] <denlud> Can i send you a pastebin link, i make some orders after suspend. And there some I/O Errors I think.
[10:30] <denlud> *?
[10:31] <denlud> http://pastebin.com/FwzhraHt
[10:32] <denlud> This output is after suspend. Maybe you can take a look at it.
[10:33] <denlud> (At the moment when /home isnt working)
[10:36] <ogra_> because it becake readonly obviously
[10:36] <ogra_> *became
[10:38] <denlud> ...can I do something against that bevior?
[10:39] <apw> denlud, ok i just added an sd card in my external sd slot, which i believe is marked removable
[10:39] <apw> denlud, and after a s/r it is still there and working, no errors
[10:39] <apw> denlud, what kernel version are you using 
[10:39] <denlud> I tried 4.2, 4.4.0-12 and 4.4.0-18 and 4.4.6
[10:40] <apw> so i am using 4.4.0-20 and it worked there for me, but i would expect -18 to be the same for mmc things
[10:40] <apw> so that for me suggests it is machine specific in some way, but i am not really sure what to suggest as mine works
[10:40] <apw> or at least not affecting everyeone
[10:42] <denlud> Maybe I try another SD Card
[10:42] <denlud> What datasystem are you using FAT?
[10:46] <apw> denlud, ext4, so something which cares if the media is ripped out
[10:48] <denlud> Ok, so i try another SD Card now and thats all i can try or?
[10:48] <apw> i am out of obvious ideas at this point
[10:49] <denlud> Ok, but thank you and ogra_ for your help.
[10:49] <denlud> And sorry for my english, I dont write in english very often.
[10:49] <apw> np
[10:49] <apw> your english is perfectly understandable
[13:04] <fg__> cking: any news about pkg-zfs/pkg-spl packaging repositories? the one at git://kernel.ubuntu.com/cking/pkg-zfs.git is still very much out of date, and the zfs user space source packages don't reference anything..
[13:05] <fg__> also are there any plans to include ZFS support in the ubuntu installer? couldn't find anything in the beta 2 iso that would allow me to setup zfs as root fs
[13:06] <cking> fg__, i will get onto that, just I'm buried in some other higher priority tasks at the moment
[13:06] <cking> fg__, no, it's not going to be supported in the 16.04 installer
[13:10] <fg__> I figured you would have other stuff on your plate with the nearing release, but figured asking would not hurt ;) thanks!
[13:16] <smb> apw, So fwiw I dug out an old aspire one that got mmc card reader and I neither can see any attempt (4.4.0-18) to eject the card and can suspend/resume even with an ext3 mounted and cd'ed into the path on a terminal window to keep it occupied
[13:28] <cpaelzer> Hi, I've analyzed bug 1570195 down to an issue in DPDK (not clear what it is exactly yet) and the kernel (can drive virtio into an infinite loop)
[13:28] <ubot5`> bug 1570195 in linux (Ubuntu) "Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices" [Medium,Confirmed] https://launchpad.net/bugs/1570195
[13:29] <cpaelzer> smb: arges: ^^ the bug holds a lot of debug info, but I'll give you the tl;dr and ask you a few important questions for confirmation before I go out to the dpdk and kernel community
[13:30] <cpaelzer> the most important open question to me would be - "what would need to happen" in the virtio protocol/host/guest-implementation so that the loop at the end of virtnet_send_command becomes an infinite loop
[13:30] <cpaelzer> it seems the buffers never change/refill again - but that is my assumption
[13:30] <cpaelzer> look at this for the loop http://lxr.free-electrons.com/source/drivers/net/virtio_net.c#L1011
[13:31] <smb> cpaelzer, maybe you allow me/us a bit to read into the bug
[13:31] <cpaelzer> oh absolutely - I'm happy about a few more eyes trying to reinterpret
[13:31] <arges> yea what smb said : ) lots of data
[13:31] <cpaelzer> I might have diverged from the right way several times
[13:32] <smb> cpaelzer, There is rarely "the" right way anyway
[13:34] <arges> cpaelzer: without reading the entire bug, have you been able to eliminate any variables causing this bug? dpdk/ovs/virtio/multiqueue ; does it work with newer kernel version, etc
[13:35] <cpaelzer> yes
[13:35] <cpaelzer> ovs is out of the scope
[13:35] <cpaelzer> also dpdk doesn't need to run traffic, just initializing the devices is enough
[13:35] <cpaelzer> anything that goes through virtnet_send_command seems to block
[13:36] <arges> and upstream dpdk also fails with the same issue?
[13:36] <cpaelzer> I didn't check an upstream kernel yet, but can do that along you are reading this
[13:36] <smb> cpaelzer, with initializing you mean let the app grab the devices not bound to a linux driver
[13:36] <cpaelzer> smb: this is virtio - dpdk grabs the device even while bound with a linux driver
[13:36] <cpaelzer> that is part of the problem as it leaves it behind in a broken state
[13:37] <cpaelzer> arges: I can test upstream versions of both over the next hour and let you and the bug know - a good test for sure
[13:37] <cpaelzer> not that I would have seen anything in the dpdk commits, but one can never be sure
[13:38] <arges> cpaelzer: yup
[13:42] <smb> cpaelzer, Hm, imo that should not be possible and probably is the problem. While the virtio network driver is bound to the device dpdk should not be able to directly access it. But thats right now a high level opinion (without much research)
[13:42] <cpaelzer> smb: it does work and it is how the people use it
[13:42] <cpaelzer> smb: which doesn't counter your opinion at all - I wondered myself at first
[13:49] <cpaelzer> smb: I asked on the DPDK channel what the opinion of the DPDK Maintainers to that is
[13:49] <cpaelzer> e.g. do they epxect people to reinitialize devices ?
[13:50] <cpaelzer> or even not to use them while bound to virtio-pci in general (but what would the PMD driver be for then)
[13:56] <smb> cpaelzer, I could imagine that being bound there, though there is also the virtio bus involved and there the virtio-net driver. But with the whole stack set up I can imagine that virtio-net could make certain assumptions which may be messed up by something else touching the lower level protocol
[14:01] <cpaelzer> smb: thanks, that is like a +1 to my theory
[14:01] <cpaelzer> still in general we would like to protect the kernel by e.g. detect too much retries in that loop and bail out right?
[14:04] <cpaelzer> I'll later on once confirmed on latest upstream of kernel and dpdk send mails to their mailing lists
[14:04] <smb> cpaelzer, heh... well the question is a bit whether virtio protocol should ever be in the situation to have a loop. The answer from that side might be that should never happen so one needs to fix the loophole of getting there.
[14:04] <cpaelzer> IMHO the kernel should get a protection to return an error instead of hanging
[14:04] <cpaelzer> and DPDK should more clearly state to either not do it this way OR add something like "after you touched it it is broken, you need to reinit"
[14:05] <cpaelzer> smb: yeah, but so far I con only point at the end of the loophole and can't clearly say which part breaks it :-)
[14:06] <smb> If the virtio nic would behave like a physical one you would get an error when trying to access it without rebinding to some userspace io driver, wouldn't you
[14:06] <cpaelzer> smb: yes
[14:07] <cpaelzer> smb: also a lot of people ran into trouble by dpdk (by default) grabbing all virtio-pci devices (usually shutting your ssh connection down)
[14:07] <cpaelzer> unfortunately so far no one responded on the DPDK IRC chan
[14:07] <smb> cpaelzer, Oh I know... 
[14:08] <cpaelzer> but if nothing gets back the mail will do
[14:08] <cpaelzer> you have to blacklist/whitelist things to go on with virto-pci
[14:08] <cpaelzer> ah you mean you ran into that smb?
[14:08] <smb> Yeah... not sure that was even with real hw and accidentally forgetting the blacklist ...
[14:09] <smb> back in 2.0
[14:10] <smb> at least some state of kiss your network connectivity good bye after trying what happens when I run testpmd...
[14:19] <cpaelzer> smb: ha - the dpdk maintainer responded
[14:19] <cpaelzer> smb: the admin is supposed to reinitialize
[14:19] <cpaelzer> known deficiency
[14:20] <cpaelzer> I'll submit patches for the docs of dpdk and our readme in packaging and our serverguid doc about it
[14:20] <cpaelzer> yet I think the kernel should protect itself in some way and will start the discussion on that later as well
[14:23] <smb> cpaelzer, yeah somehow it should be similar to real hw. I just cannot really say how this all should interact together...
[14:28] <cpaelzer> smb: there is a patch that it no more initializes when bound to virtio-pci
[14:29] <cpaelzer> smb: just discussing with the DPDK maintainer - I'll try to backport that
[14:29] <cpaelzer> that would mean a user would have to unbind it from virtio-pci before using it in dpdk
[14:29] <cpaelzer> and to use it in the normal linux world would have to rebind it
[14:29] <cpaelzer> that would reinitialize and all is good
[14:30] <smb> cpaelzer, I think that would make it behave "normal" so much better 
[14:30] <cpaelzer> ack
[19:47] <jsalisbury> lamont, I pinged upstream regarding you bug again.  I cc'd you on the mail, so you can stay in the loop.
[19:48] <lamont> woot
[23:53] <denlud> Heey whats up?
[23:56] <denlud> I have a Problem with my diskspace, would be great if someone can i help me. I have downloaded to much porns, now my home memory is full. How can i expand it with an external drive?