[01:39] <kristian-aalborg> jj-afk: ah nm, it got too late
[11:38] <kristian-aalborg> morning
[11:55] <edgimar_> Could anyone give me tips on debugging a kern.log entry -- I am seeing a "bad: scheduling from the idle thread; Pid: 0, comm: swapper Not tainted 2.6.32-29-generic #58-Ubuntu; Call Trace: ..." about every 2-3 microseconds -- and the logs (kern.log, syslog, and messages) are getting HUGE (as in around 20GB each).
[12:03] <edgimar_> Here's a snippet from the syslog which could be relevant: http://pastebin.com/m3tUashf
[13:00] <kristian-aalborg> https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel 
[13:01] <kristian-aalborg> the dependencies you get with the command listed here (sudo apt-get build-dep linux-image-$(uname -r)) are way too heavy - who's to "blame"?
[13:02] <kristian-aalborg> not the quatiation marks, nobody is to blame of course :) but this could probably be fixed
[14:15] <AnAnt> Hello, anyone knows what happened to open_sem function in kernel ?
[14:15] <AnAnt> was it replaced by something else ?
[14:24] <kristian-aalborg> there should be some kind of lottery where you got a ticket each time a kernel build failed ;)
[14:28] <AnAnt> sorry, I meant DECLARE_MUTEX
[14:29] <kamal> kristian-aalborg: I'd be sooooo rich.  ;-)
[14:36] <kristian-aalborg> speaking of errors, ah few is nothing to worry about, right?
[14:39] <kamal> kristian-aalborg: actually, any *error* will stop your build dead.    perhaps you just mean warnings?   post an example of one of the "errors" you're worried about.
[14:39] <kristian-aalborg> kamal: yup, I was thinking warnings
[14:40] <kamal> kristian-aalborg: yeah, the kernel build spews lots and lots of warnings for sure...  don't worry about them, as long as your build keeps rolling along.  
[14:50] <kristian-aalborg> it would be cool if you could just upload your .config and then get the .deb
[15:07] <kristian-aalborg> bugger, it quit again
[15:24] <kristian-aalborg> I got it to build finally, installing now :)
[15:49] <kristian-aalborg> hurm, dependency problems
[16:03] <kamal> kristian-aalborg: which .deb(s) did you build and install?  If you build "binary-headers" and "binary-generic" you should end up with 3 .debs (one linux-image-...deb and two linux-headers-...deb).  That set of 3 .debs should be installed as a group.   That help any?
[16:04]  * kamal notes that the wiki page https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel fails to mention binary-headers :-(
[16:06] <kristian-aalborg> kamal: likely
[16:07] <kamal> kristian-aalborg: try this instead of just 'binary-generic':    fakeroot debian/rules binary-headers binary-generic
[16:07] <kamal> then verify that you end up with 3 .debs -- dpkg -i them all together -- should help.   I'll see about fixing the wiki.
[16:08] <kristian-aalborg> kamal I was following some instructions I got on this channel recently more than the wiki
[16:13]  * kristian-aalborg facepalmed and got some more coffee... is ready again now
[16:14] <kamal> kristian-aalborg: oh yes, I should have mentioned...  strong coffee is another prerequisite for the kernel build ;-)
[16:17] <kristian-aalborg> hurm, I actually only have two .debs - linux-headers and linux-image
[16:17] <kristian-aalborg> I got the missing modules error, then tried again with the ignore-missing (or such) flag
[16:18] <kamal> kristian-aalborg: ignoring module checks and abi is fine.  I suspect you need that third .deb, which you'll get if you build 'binary-headers'
[16:19] <kamal> FYI, the complete set of 3 will look something like this:
[16:19] <kamal> linux-headers-2.6.38-6_2.6.38-6.34_all.deb
[16:19] <kamal> linux-headers-2.6.38-6-generic_2.6.38-6.34_amd64.deb
[16:19] <kamal> linux-image-2.6.38-6-generic_2.6.38-6.34_amd64.deb 
[16:20] <kristian-aalborg> ok
[16:20] <kristian-aalborg> so, fakeroot debian/rules binary-headers
[16:20] <kamal> kristian-aalborg: yes
[16:21] <kristian-aalborg> how "heavy" is that, compared to the others?
[16:21] <kamal> very light
[16:21] <kristian-aalborg> cool
[16:21] <kristian-aalborg> who's doing the wiki, btw?
[16:22] <kamal> the wiki pages are maintained by the Ubuntu kernel team (and the community in general)
[16:23] <kristian-aalborg> it could use a little touching up, although I really like that it's rather short
[16:24] <kristian-aalborg> btw, ubuntu.com is looking real pro these days - probably the neatest OS website I have seen
[16:24] <kamal> kristian-aalborg: there have been various versions of the "how to build a kernel" instructions, some too long, some too short.   its tough to come up with one document that works well for everybody.
[16:24] <kristian-aalborg> sure
[16:25] <kristian-aalborg> there's just a point where it gets so detailed that users can be intimidated to never try, imo
[16:26] <kamal> kristian-aalborg: absolutely true -- I like the "short instructions" for that reason, but perhaps they've been trimmed down just a bit too much.
[16:28] <kristian-aalborg> yes, it is a very hard balance to find
[16:30] <kristian-aalborg> there's also a point where you keep users in the dark by insisting that they do things the "easy" way
[16:33] <kristian-aalborg> something is happening now... this might work
[16:37] <kristian-aalborg> kamal: using apmd?
[16:38] <kamal> kristian-aalborg: nope
[16:39] <kristian-aalborg> erm, my new kernel reboots the box
[16:39] <kristian-aalborg> also in recovery mode
[16:41] <kamal> kristian-aalborg: did you apply any patches, or is the source unmodified?  What version exactly did you build, and what Ubuntu version are you running?
[16:41] <kristian-aalborg> I'm running 10.4 - I did a make localmodconfig and then tweaked it
[16:41] <kamal> kristian-aalborg: I suggest that you try building a plain unmodified kernel as a sanity check.
[16:42] <kristian-aalborg> I got it via git
[16:42] <kristian-aalborg> yeah, that's probably what I should do
[16:44] <kristian-aalborg> something weird is that I called it ~custom, but it seems to have installed as -generic
[16:45] <kamal> kristian-aalborg: so are you building the ubuntu-lucid (10.04) kernel on a lucid system, and then installing it on a lucid system?  Or something more fancy (i.e. installing a newer-than-lucid kernel on a lucid system?)
[16:46] <kristian-aalborg> I'm building on Lubuntu 10.4 which should be the same, then installing on 10.4
[16:47] <kristian-aalborg> wut
[16:47] <kristian-aalborg> aptitude wants to install tzdata and similar things
[16:48] <kamal> kristian-aalborg: ok, nothing too fancy then.   I don't understand what you mean by "called it ~custom" vs. "installed as" though...  Sounds like you modified debian{.master?}/changelog and didn't get the result you expected.  post the specifics if you need help unraveling that.
[16:48] <kristian-aalborg> might fix things... lemme see
[16:48] <kamal> kristian-aalborg: tzdata gets updated often -- probably not related to your kernel build/reboot issue.
[16:49] <kristian-aalborg> yeah, I was thinking of BzImage
[16:49] <kristian-aalborg> I edited debian/changelog to have a name that'd be different from my other kernels
[16:49] <kamal> kristian-aalborg: good plan, but ...
[16:50] <kristian-aalborg> this reflects in the names of my .debs, so weird it's not showing upon install
[16:50] <kamal> kristian-aalborg: note that debian/changelog gets overwritten (copied from) debian.master/changelog during the "fakeroot debian/rules clean" phase ...
[16:50] <kristian-aalborg> I did it before 
[16:51] <kamal> kristian-aalborg: I'd say, double-check debian/changelog *now* to make sure it still has your ~custom tag in there -- does it?
[16:51] <kristian-aalborg> one moment, I have to fire up another pc then
[16:52] <kamal> kristian-aalborg: oh wait...   do you mean just that you expected to see "~custom" in the GRUB boot loader menu?  it doesn't show it there (sadly)!
[16:52] <kristian-aalborg> ah, that's okay
[16:53] <kamal> kristian-aalborg: yeah, it shows up in 'uname -a' (but it sounds like you're rebooting/crashing long before getting to a login prompt, yes?)
[16:53] <kristian-aalborg> yes
[16:54] <kamal> kristian-aalborg: likely all is fine then -- when you build your "unmodified" test kernel, you may want to go ahead and *still* mark it with a special version string, just so you can verify that its really your kernel with 'uname -a' once you do get it to boot.
[16:54] <kamal> kristian-aalborg: I often build test kernels with a "~unchanged" version string addition.
[16:55] <kristian-aalborg> I fooled around with dpkt and apt-get to try to "fix" the .deb that would not install
[16:56] <kristian-aalborg> I seem to have locked linux-generic in the process, unwise as I am
[17:01] <kamal> kristian-aalborg: I don't know what state you're in there, but      apt-get install -f          may help (or at least tell you what the problem is).
[17:07] <kristian-aalborg> they say "dependency hell" as if there is a "dependency heaven"... sigh
[17:16] <kristian-aalborg> I'm wondering... since this is from git, could it be partly unmet by the repos?
[17:17] <kamal> kristian-aalborg: unlikely -- the git repo's "master" branch should always produce a kernel that builds and installs properly.
[17:17] <kristian-aalborg> ok
[17:19] <kamal> kristian-aalborg: I wonder if you have some leftover bits installed from your first failed installs.  try this:
[17:19] <kamal> dpkg -l | grep "~custom"
[17:19] <kamal> this should list all packages that you have installed which have "~custom" in their name
[17:20] <kristian-aalborg> I still have all of it
[17:20] <hyperair> kristian-aalborg: dependency issues? how about a paste of the errors?
[17:20] <kristian-aalborg> hi hyperair 
[17:20] <hyperair> hi
[17:20] <hyperair> so how about pastebinning your errors
[17:21] <kristian-aalborg> these issues were my own fault... I was missing a .deb
[17:21] <kamal> you could remove (with dpkg) all of your "~custom" packages to clean up.
[17:23] <kristian-aalborg> I'm trying once more now the dependencies seem fixed
[18:05] <kristian-aalborg> ah, enough for now
[18:08] <kristian-aalborg> but thanks for helping out, ppl... I believe I will have this sorted in the foreseeable future
[20:19]  * kristian-aalborg is back
[20:20] <kristian-aalborg> kamal: ping
[20:21] <kristian-aalborg> fakeroot debian/rules clean
[20:21] <kristian-aalborg> fakeroot debian/rules binary-generic
[20:21] <kristian-aalborg> only these two commands needed for the "sanity check"?
[20:29] <Kano> hi, would somebody update kernel-wedge to be newer than current squeeze/sid version?
[20:48] <kamal> kristian-aalborg: I always do:   fakeroot debian/rules binary-headers binary-generic    (building and installing the headers along with image is quick enough, and never hurts)
[20:51] <kristian-aalborg> I'll do that as well, then... although not in that order
[20:52] <kristian-aalborg> btw the system I'm building on is Lubuntu 10.4, not Ubuntu... but should not matter, I think