/srv/irclogs.ubuntu.com/2013/11/04/#ubuntu-kernel.txt

ppisatimoin08:43
smbppisati, morning08:44
smbppisati, Still in one piece? :)08:45
* apw yawns08:48
apw(himself)08:48
* smb already had08:51
ppisatismb: yep :)09:01
=== fmasi_afk is now known as fmasi
apwsmb, i thought the dm-raid45 driver was effectivly a meta-data reader, and setup md underneath once so read ?09:44
apwsmb, and ... what do we think about just leaving it off for T, to figure out if anyone is actually affected by it09:48
smbapw, The dm-raid45 module is the kernel-side implementation (as I wrote in my reply)09:49
smbRight now the dmraid user-space uses it to set up the dm driver09:49
smbBut as I wrote too, one could change it maybe to use dm-raid -> md  09:50
apwso dmraid userspace is still using raid4509:51
smbOr leave it off but change the installer to make mdadm at least support two formats09:51
smbapw, It seems to be as abandoned as the kernel module, yes09:51
apwhmmm09:51
apwwell that is poop.  what do we use to setup raid normally, dmsetup instead now ?09:51
smbNot sure whether RH silently came up with something differently named to replace it or just did not care for those09:52
smbapw, fakeraid not the normal raid09:52
smbapw, for softraid the tools should use mdadm already and that is md09:53
smbapw, dmraid is fakeraid which is those bios'es claiming to have raid but only do some meta-data and the rest is software09:53
apwsmb, ok ... so from your email it sounded like some of the formats supported by fakeraid now were supported by mdadm ?09:58
smbapw, Mostly the IMSM. I can not say whether or if which of those might be DDF09:59
smbapw, Though I would doubt that a lot of those cared about any standard10:00
apwwell presumably fakeraid support formats A B and C, do we know that list10:02
smbapw, Not from memory. We could use the source...10:05
apwsmb, ok i am comparing now ... and will reply10:05
smbapw, I guess the problem might be that the utils say support this and that controller or board but not what kind of format that was10:07
apwsmb, right ... am i right in thinking you have something which used this ?10:19
smbapw, Well I have one, maybe two kinds... not really very much10:22
smbapw, And one of those is my work-desktop... which is a lot of pain to try things on (while preventing to end up with a lot of pieces)10:23
apwsmb, is either of those actually using it?  or did you use something else10:26
apwsmb, and if they are can you get me a dmsetup table off one10:26
smbapw, Neither is using it right now10:26
apwok10:27
smbapw, And the work machine uses md raid10:27
smbapw, You would see nothing with dmsetup10:27
apwsmb, i thought dmraid45 was a real dm personality when loaded10:28
apwit is used that way in the dmraid userspace10:28
smbapw, The problem is that "it" is quite ambiguous... 10:29
apwthe dmraid userspace uses the dmraid45 kernel module via making dm tables, which seems to doo it that way10:30
smbapw, Right, just when you asked whether I currently use "it" I was not sure you asked about dmraid or any softraid.10:31
apwi am being oblique indeed10:44
apwxnox, hey ... know anything about dmraid userspace ... 10:44
apwit is so clear this has not changed like forever10:45
smbWonder whether this would be worth a session on vUDS10:54
apwyeah we might want to touch on it in our 'misc' session at least10:56
xnoxapw: smb: i want a vUDS session on fakeraid. IMSM works "best" with mdadm, which means we need to pull mdadm into initramfs (done) and actually start mdmon to monitor / make those "special" raid devices work (IMSM and DDF)11:37
xnoxafter 3.3 is merged, since that actually makes DDF work.11:37
xnoxmy motherboard has support for both DDF and IMSM raid devices.11:37
xnoxbut that means to organise switchout from dmraid, which helpfully will also try to activate "all" raid devices it can regornise.11:38
xnoxI haven't tried yet on my machine to see what happens if both dmraid and mdadm are racing to activate same raid device, or if it's ok for both of them to activate it (as long as only one of them mounted I guess)11:38
smbxnox, I am not completely sure what I got. nvidia and something else. But we would also tend to rather want to drop the dm-raid45 special kernel module dmraid uses right now11:39
smbxnox, In the past (when I tried last) mdadm won but only worked read-only11:39
xnoxsmb: but mdadm does not support _all_ raids that dmraid does.11:39
smb(for intel msm)11:39
smbxnox, right11:39
xnoxsmb: for intel msm, mdadm is best. I was thinking to patch out IMSM out of dmraid & upload dmraid with "Depends: mdadm" to transition people to mdadm who use Intel MSM.11:40
smbxnox, The question would be whether (or how difficult) it would be to make dmraid use the dm-raid target instead (which then uses md in the background)11:40
xnoxnot sure how sane that approach is though.11:40
smbAt least imsm is a known subset, so that does sound sane at least11:41
xnoxsmb: just using md in the background is not enough. For intel msm raid with mdadm, one needs to have mdmon daemon running - which actually does the talking to the firmware/raid-chip-on-board to write/read/update raid metadata, as far as I can tell.11:41
xnoxDDF doesn't have 1-to-1 mapping into dmraid set of supported devices =/ and i'm happy to mostly ignore DDF for now, until some vendors come and say we really want this and that supported via mdadm.11:43
xnox(intel expressed such interest before)11:43
smbYeah, I can see no easy way to figure out which is which. Hm, somewhat I'd be surprised that mdmon talks to firmware (that firmware seemed pretty dumb to me) But I would have to look into that. But yeah, probably that is doing the loggin via something else11:45
apwxnox, will you own getting a dmraid session on the core- track ... and put smb and myself on it ... as clearly this needs some work and we should have a BP for it :)11:50
apwxnox, that first bit really is a question btw :)11:50
xnoxapw: yes. let me put it in.11:54
apwxnox, great, a plan then12:07
xnoxapw: smb: summit is aweful, please "attend" http://summit.ubuntu.com/uds-1311/meeting/22017/transitioning-to-use-mdadm-by-default-for-some-of-the-fakeraid-devices/ as well =)12:09
* xnox couldn't be bothered to scroll though non-searchable list of people who signed up to vUDS =)12:09
xnoxyou are subscribed to the blueprint already... maybe summit will import that, maybe not.12:10
apwxnox, thanks ... 12:29
=== gfrog_ is now known as gfrog
* ppisati disappears for a bit...16:48
=== fmasi is now known as fmasi_afk
apwhenrix, i've applied that patch and tried to sort out the bug, it is missing the SRU bits17:51
henrixapw: thanks17:52
henrixapw: that bug has been fixed in Q before, and i thought the fix was applied from 3.2 stable. i was wrong17:54
apwhenrix, ok, just needs the SRU templaste copying over from the last one i suspect17:55
henrixapw: yep, i'll take care of that17:55
henrixapw: thanks17:55
apwotherwise it looks fine to me, and well smb and sconklin have staked their reputations on it :) so i don't need to read it17:55
henrixheh 17:55
apwclap4ham18:29
apwi am do going to remove unity from this machine18:29
apwthat'd be the fourth time it has done htat in as many months18:30
* apw is jetlagged to hell and back ...19:38
bjfmarrusl, around?23:44
bjfkamal, is bug 1163720 something you can verify or get someone to verify?23:45
ubot2Launchpad bug 1163720 in linux (Ubuntu Raring) "Brightness control broken on XPS13 and 3.8.0-16, 3.8.0-22 and 3.11.0-12" [Medium,In progress] https://launchpad.net/bugs/116372023:45
bjfkamal, i seem to have a commit that has that as the buglink in quantal23:46
marruslbjf, hey23:51
bjfmarrusl, is bug 1208740 something you can verify23:54
ubot2Launchpad bug 1208740 in linux (Ubuntu Raring) "Large pastes into readline enabled programs causes breakage from kernels v2.6.31 onwards" [Medium,Fix committed] https://launchpad.net/bugs/120874023:54
bjf?23:54
bjfmarrusl, or will arges be back this week and he can do it?23:54
marruslbjf, arges is back I believe.  one of us will get to it.  making a note.23:55
bjfmarrusl, thanks23:59

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