[10:00] <TJ-> Would we expect a system hang when iwl4965 (iwlegacy/4965-mac.c) reports 'BUG_ON idx doesn't match seq control'. I couldn't fully track the IL_ERR macro (dev_err) back to its final expansion
[10:02] <TJ-> This is with 15.10 amd64 low-latency kernel. May have happened a couple of times in the last 24 hours but this is the first time the log has shown anything
[10:16] <apw> TJ-, any bug_on can be fatal or not depending on circumstances, but i' dmore commonly expect you to lose wireless 
[10:17] <apw> TJ-, anyhow you hsould file a bug with the backtrace
[10:18] <TJ-> apw: Not possible. System hung. If that is the cause of all the hangs I've seen - this is the only logged clue currently. Always happens when the system has been left idle with no-one using it
[10:18] <apw> then that might be power management perhaps ?
[10:18] <apw> might be worth seeing if there is a way to turn that off as a test
[10:18] <apw> TJ-, and which kernel are you running
[10:19] <TJ-> I somehow think it is unrelated, I've been using a build of 4.1 with PCI IOMEM fixes in for a long time on 14.04, and not been hit. I think this is something unique to the Ubuntu 4.1 build.
[10:19] <TJ-> apw: amd64 4.1.0-3-lowlatency
[10:20] <TJ-> There's no ASPM enabled
[10:20] <apw> TJ-, so wily, has the 4.2 migrated yet ?
[10:26] <TJ-> I've not see it yet. Not been able to use the mainline 4.2 without manually fixing the workqueue GPL symbol, due to requiring nvidia
[10:27] <TJ-> I've been having to carry fixes for PCI IOMEM since 3.15 which *should* finally reach mainline in 4.3, so it gets quite involved trying to chase down these issues :)
[10:28] <apw> TJ-, its in -proposed
[10:28] <TJ-> OK, I'll enable it and see how it goes. I hate it when there are 0 clues
[13:37] <rtg> arges, what ever happened with bug #1370352 in trusty ?
[13:45] <arges> rtg: looking
[13:48] <arges> rtg: the bug in the last comment should have been bug 1398975
[13:49] <rtg> arges, yeah, it was circular
[14:24] <cmagina> I am porting an upstream driver to arm64 and it requires a kernel config update so i ran the updateconfigs target. It made changes to the common config but the new driver is only needed for a specific arch. should i move these changes to that arch's config or leave it how updateconfigs left it?
[14:24] <cmagina> back porting an upstream arm64 driver
[14:25]  * cmagina needs stronger coffee
[14:29] <rtg> cmagina, if the config option is unique to arm64 then it will appear in common since it is the only instance 
[14:30] <cmagina> rtg: ah, ok, so just leave it since updateconfigs did the right thing
[14:30] <rtg> yup
[14:30] <cmagina> thanks
[15:10] <MikeCamel> Hi, folks - anyone having any joy with 4.2?  No problems compiling, but it hangs at initramfs boot.  Using config files pretty much unchanged from 4.1...
[15:13] <apw> MikeCamel, boots ok for me here
[15:14] <apw> cat /proc/version_signature 
[15:14] <apw> Ubuntu 4.2.0-5.5~masternext201508181139-generic 4.2.0-rc7
[15:14] <apw> running a slightly older one than the -7.7 in -proposed, but it boots for sure
[15:14] <rtg> apw, tsk, tsk. you should be booting -7.7
[15:15] <apw> rtg, i am supprised to find i am not
[15:15] <rtg> apt-add-repository ?
[15:16] <MikeCamel> I've just been taking the .xz from kernel.org, and compiling my own.  Old style, but it's what I'm used to.
[15:17] <MikeCamel> I'm taking debs from ~kernel-ppa: I'll see if those boot.  If they do, I'll try the .config from /boot there, and use that as the starting point.
[15:19] <apw> rtg, oh how it gets on isn't the issue, lack of care is
[15:19] <apw> MikeCamel, sound plan
[15:20] <MikeCamel> been compiling kernels since ~'96.  Recently got back into it.  :-)
[15:21] <MikeCamel> These days it's just for fun.  In those days, you _had_ to, if you wanted your new h/w to work.
[15:22] <MikeCamel> right.  biab.  reboot time.
[15:25] <MikeCamel> well, that booted, at least.  no wifi, but it booted.
[15:25] <MikeCamel> wonder what the diff was.  Time to do some playing...