[12:35] <tjaalton> apw: do you have an estimate for the initramfs-tools update to fix nvme? should happen before 4.4 hits xenial
[12:37] <apw> tjaalton, i could do that todya i think if i back out manjo's change.  as that does not seem to work for him
[12:37] <caribou> apw: yes, on this nvme note, do you need me to re-test on my platform or cking's test is sufficient ?
[12:37] <apw> tjaalton, i think i need to pull in 0.122 from debian to fix manjo and that is a bigger job
[12:37] <tjaalton> ok..
[12:37] <apw> caribou, if cking is working i suspect you are good, though yours was a slightly differnet use case
[12:38] <apw> caribou, i applied a change for each of you and cking
[12:38]  * cking just do the NVME test
[12:38] <apw> cking,  ?
[12:38] <caribou> apw: what was cking's problem btw ? mine was a failure when using MODULES=dep
[12:38] <apw> you just tested nvme booting right ?
[12:39] <apw> caribou, i don't think he could have his as root
[12:39] <caribou> in building initrd.img
[12:39] <apw> caribou, perhaps its safest if we say, could you test :)
[12:39] <apw> then i can upload those two fixes at least
[12:39] <apw> and then merge 1.122 or whatever it is
[12:40] <apw> which has a lot of new bits so will be more frightening
[15:29] <smb> jsalisbury, Hey Joe, a random question... Did you see any bug reports from Wily or later that may happened on bare-metal servers or KVM guests and crash in run_timer_softirq()? 
[15:30] <jsalisbury> smb, I don't recall off hand, but I'll review the latest reports to see 
[15:32] <smb> jsalisbury, ok thanks. Its just a feelign or me wondering. Was looking at bug 1534345 and was not really finding anything striking out in the xen parts. There was some rework of the timer code, though. But then it should be not only Xen/AWS that gets affected...
[15:32] <jsalisbury> smb, latest one I see with that RIP is bug 1534345
[15:33] <jsalisbury> heh, good timing
[15:33] <smb> jsalisbury, heh yeah
[15:33] <smb> That was where I was coming from
[15:33] <jsalisbury> smb, I'll search through some older reports too
[15:35] <smb> jsalisbury, ok. _IF_ it had anything to do with switching from list_head to hlist in the timer code it would only start with kernel 4.2. But again its just a wild guess right now
[15:36] <jsalisbury> smb, I don't see any other recent bugs, but I'll keep an eye open for any new ones.  
[15:36] <smb> jsalisbury, ok thanks
[16:52] <TJ-> unable to reproduce so far, but today had a v4.4 boot-time kernel panic in interrupts with the CFQ in kernel/sched/fair::update_blocked_averages()