[05:25] <lucent> bug 657081 needs some love from anyone who knows how to get changes applied to Maverick
[05:25] <ubot2> Launchpad bug 657081 in linux (Ubuntu) "New firewire stack unreliable with Texas Instruments TSB82AA2 IEEE-1394b (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/657081
[05:25] <lucent> (from stable)
[05:31] <crimsun> lucent: please reference the upstream linux-2.6 git changeset hash in a comment
[05:32] <crimsun> lucent: depending on the invasiveness of the changesets, you might want to submit it for inclusion in 2.6.35.x (send an e-mail to stable@kernel.org)
[05:32] <lucent> oh. okay.
[05:33] <lucent> crimsun: it's a revert, "Revert commit 54672386ccf36ffa21d1de8e75624af83f9b0eeb"
[05:34] <lucent> does that make sense?  or does the revert have its own hash for the action of reverting
[05:35] <crimsun> it does make sense, and yes, a revert has its own git changeset hash.
[05:35] <crimsun> you're of course speaking of commit aa0170ff
[05:35] <lucent> oh okay, so there's some point where my brain stopped working :)
[05:36] <lucent> now I am looking and making sense of http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.36
[05:36] <lucent> two minutes before, I was too confused to notice
[05:36] <lucent> commit 7f81c56cf29c0af66a1d0cdbce48441cdaf9fa16
[05:36] <crimsun> err, not precisely
[05:37] <crimsun> 7f81c56c is the merge changeset
[05:37] <crimsun> the actual commit to cherry-pick is aa0170ff
[05:37] <lucent> add to the bug, thanks for the guidance
[05:37] <crimsun> yw
[05:38] <lucent> seperately I have affected some USB serial code, which is up for review to be included in 2.6.37-rc1
[05:38] <lucent> is it helpful for me to file a launchpad bug about that?
[05:39] <lucent> the cause is determined, upstream knows, just that I'm confused how will Ubuntu kernel get these changes
[05:42] <crimsun> it depends on the Ubuntu release(s) to which you're referring.
[05:42] <crimsun> if it's the current development one (2.6.37), then the changes are rebased nominally in natty.
[05:43] <lucent> okay, you're right... I did not say.  I'm thinking of Maverick
[05:43] <lucent> Maverick is the only release that is affected by my findings of the usb serial and firewire regressions, here, because the regressions are since 2.6.35
[05:43] <crimsun> the easiest approach in that regard is to request that the relevant changeset(s) from linux-2.6.git be merged into 2.6.35 stable via gregkh
[05:44] <lucent> ah okay
[12:35] <PascalFR> bug #660302
[12:35] <ubot2> Launchpad bug 660302 in module-init-tools (Ubuntu) "e1000e ethernet link down (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/660302
[12:35] <PascalFR> anyone has eth which uses e1000e on maverick ?
[13:10] <lucent> not I
[17:12] <ai2097> I'm trying to build/install a custom kernel following <https://wiki.ubuntu.com/KernelTeam/GitKernelBuild>, but step 8 (make-kpkg) fails. Tail-end of output (with the command issued at the very end) at: <http://pastebin.com/67rhtEVh>