[00:10] <psusi> does anyone know of a decent software design spec/overview for libata?
[01:20] <Sebboh> Hi.  I'm using the guide at https://help.ubuntu.com/community/Kernel/Compile .  I'm building on a PowerPC, I've got the Maverick kernel source via git, and I've modified a source file to get around a won't-fix bug for powerpc.  I haven't done this in a while, and last time I did was on Debian.  I'd use make menuconfig to build a .config.. About halfway through that guide, it says to execute "AUTOBUILD=1 fakeroot debian/rules binary-debs". 
[01:25] <Sebboh> Also, this guide refers to a few things that don't exist in this source tree, like "To build one of the custom flavours (found in debian/binary-custom.d/), use: ..."  There is no such directory.  Did that stuff move somewhere else?
[01:28] <Sebboh> Oh, a better example: "If you just want to update one architecture, run: debian/scripts/misc/oldconfig ARCH"...  No such file.  But I really want to do that.  How?
[01:36] <Sebboh> debian/rules editconfigs didn't prompt me for powerpc.  I'm just trying random things here.. :P
[03:40] <Sebboh> ok, forget my previous question..
[03:40] <Sebboh> How can I use my own .config for a kernel build?  I'm following this guide: https://help.ubuntu.com/community/Kernel/Compile .. Whenever I put a .config in the kernel source root, the build process complains that I should run make mrproper. I've read that this means there are extra files, great.  How do I shove my .config into this new debian.master/config flavour system?
[10:08] <jussi> right, Im trying to find someone I met at UDS - I left a bottle of salmiakki with him...
[10:15] <amitk> jussi: riku?
[10:15] <jussi> amitk: no, I think his name was Lee - was the saturday night :=)
[10:15] <amitk> lag: ^
[14:36] <lag> Hi jussi 
[14:37] <lag> What can I do for you?
[15:13] <smoser> smb, around ?
[15:13] <smb> smoser, masybe 25% (currently sitting in talks at LPC)
[15:14] <smoser> i'm wondering if you woudl think that bug 667656 is a dupe of bug 567334 and/or bug 666211
[15:14] <ubot2> Launchpad bug 667656 in linux (Ubuntu) "soft-crash: task flush blocked for more than 120 seconds (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/667656
[15:14] <ubot2> Launchpad bug 567334 in linux (Ubuntu) (and 1 other project) "blocked tasks delay cloud-init for 240 seconds (affects: 2) (heat: 33)" [Medium,Triaged] https://launchpad.net/bugs/567334
[15:14] <ubot2> Launchpad bug 666211 in linux (Ubuntu) "maverick on ec2 64bit ext4 deadlock (affects: 3) (heat: 26)" [High,Confirmed] https://launchpad.net/bugs/666211
[15:14] <smoser> or if its just symtoms (the blocked tasks that are the same)
[15:15] <smb> smoser, blocked tasks would at least be different to the boot crash I guess
[15:15] <smb> Depends on whether there is a crash visible
[15:15] <smb> For some time, and I am not sure what kernels where used for the task blocked cases, there
[15:15] <smb> was some chance that this was related to poor writeback performance
[15:16] <smb> smoser, If possible we should get reconfirmation with the latest kernel currently in proposed (for Lucid)
[15:17] <smoser> ok. so i'll leave them un-duped for the moment.  bug 667656 is the only one with a actual crash.
[15:17] <ubot2> Launchpad bug 667656 in linux (Ubuntu) "soft-crash: task flush blocked for more than 120 seconds (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/667656
[15:17] <smoser> none of those are lucid, smb 
[15:17] <smb> Ok, so at least there should be not that critical writeback problems in Maverick
[15:18] <smb> smoser, jj just started a SRU for the intel_idle option to be disabled
[15:18] <smoser> some people are suspecting that its ext4 related, which could be why you'd see them on maverick but not lucid.
[15:18] <smoser> maverick ec2 images have ext4, lucid have ext3
[15:18] <smoser> smoser, in the -virtual kernel ?
[15:19] <smb> One might do ext3 to compare, but I would need to check on the tracebacks of the task blocked bugs to say more
[15:19] <smb> and that likely will not be before next week
[15:23] <smoser> smb, so what do you think about the random kernel message timestamps ?
[15:24] <smoser> ie, apparent time travel both forward and backward by months at a time
[15:29] <smb> smoser, It would be interesting to know what clocksource is used in those cases (should be somewhere in /sys/devices/system/clocksource). So could be a bad timer there or something related to c-states handling.
[15:29] <smb> But as said, being at a conference I won't spend too much time to think on those things now
[15:29] <smoser> smb, fair enough. thanks for your time, htough.
[15:43] <komputes> Can a kernel engineer please have a look at Bug #670181 ?
[15:43] <ubot2> Launchpad bug 670181 in linux (Ubuntu) "Dell Precision M6300 SD Card Reader (Ricoh R5C592 memory stick) Will Not Mount After Upgrade To 10.10 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/670181
[16:06] <tgardner> apw, you gonna push natty?
[16:13] <smb> tgardner, He may when he stops looking disgusted
[16:29] <simar> Hey anybody have idea of progress in this very old issue. Should I forward it upstream
[16:30] <simar> Bug #372090
[16:30] <ubot2> Launchpad bug 372090 in linux (Ubuntu) "AlpsPS/2 ALPS GlidePoint gets stuck and is generally unresponsive. (affects: 4) (dups: 1) (heat: 28)" [Low,Confirmed] https://launchpad.net/bugs/372090
[16:58] <robtow> Has anyone gotten Ubuntu 10.10, kernel 2.6.35-22-generic to work with a Dell e6510 WITHOUT an Nvidia card? I can boot 10.10 with kernel 2.6.31-22-generic; but 2.6.25-22-generic gives the message: "22.2344991 Intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled" - then it boots, but with no X. Adding nomodeset to boot params doesn't help.
[17:04] <apw> tgardner, all pushed and uploaded
[18:56] <sconklin> Sarvatt: you about?
[19:36] <bullgard4> '$ sudo make menuconfig' > Linux Kernel v. 2.6.32.21+drm33.7 Configuration > i915 driver > Enable modesetting on intel by default. Where can I find a not too short introductory article about "modesetting"? 
[19:54] <tgardner> apw, armel build broke when you re-enabled CONFIG_GPIO_PCH when merging the ports config.
[19:54] <apw> tgardner, no it broke when the patch you applied after the one which disabled it, reenabled it
[19:54] <apw> but that isn't your fault, something screwey is going on
[19:55] <apw> i am trying to turn it off, and it won't stay turned off right now
[19:55] <tgardner> hmm, I thought it got tuned on in 'UBUNTU: [Config] move powerpc over from ports to distro'
[19:55] <tgardner> glp