=== jjohansen is now known as jj-afk [01:39] jj-afk: ah nm, it got too late === _LibertyZero is now known as LibertyZero [11:38] morning [11:55] 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] Here's a snippet from the syslog which could be relevant: http://pastebin.com/m3tUashf [13:00] https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel [13:01] 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] not the quatiation marks, nobody is to blame of course :) but this could probably be fixed === yofel_ is now known as yofel [14:15] Hello, anyone knows what happened to open_sem function in kernel ? [14:15] was it replaced by something else ? [14:24] there should be some kind of lottery where you got a ticket each time a kernel build failed ;) [14:28] sorry, I meant DECLARE_MUTEX [14:29] kristian-aalborg: I'd be sooooo rich. ;-) [14:36] speaking of errors, ah few is nothing to worry about, right? [14:39] 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] kamal: yup, I was thinking warnings [14:40] 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] it would be cool if you could just upload your .config and then get the .deb [15:07] bugger, it quit again [15:24] I got it to build finally, installing now :) [15:49] hurm, dependency problems [16:03] 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] kamal: likely [16:07] kristian-aalborg: try this instead of just 'binary-generic': fakeroot debian/rules binary-headers binary-generic [16:07] 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] 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] kristian-aalborg: oh yes, I should have mentioned... strong coffee is another prerequisite for the kernel build ;-) [16:17] hurm, I actually only have two .debs - linux-headers and linux-image [16:17] I got the missing modules error, then tried again with the ignore-missing (or such) flag [16:18] 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] FYI, the complete set of 3 will look something like this: [16:19] linux-headers-2.6.38-6_2.6.38-6.34_all.deb [16:19] linux-headers-2.6.38-6-generic_2.6.38-6.34_amd64.deb [16:19] linux-image-2.6.38-6-generic_2.6.38-6.34_amd64.deb [16:20] ok [16:20] so, fakeroot debian/rules binary-headers [16:20] kristian-aalborg: yes [16:21] how "heavy" is that, compared to the others? [16:21] very light [16:21] cool [16:21] who's doing the wiki, btw? [16:22] the wiki pages are maintained by the Ubuntu kernel team (and the community in general) [16:23] it could use a little touching up, although I really like that it's rather short [16:24] btw, ubuntu.com is looking real pro these days - probably the neatest OS website I have seen [16:24] 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] sure [16:25] there's just a point where it gets so detailed that users can be intimidated to never try, imo [16:26] 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] yes, it is a very hard balance to find [16:30] there's also a point where you keep users in the dark by insisting that they do things the "easy" way [16:33] something is happening now... this might work [16:37] kamal: using apmd? [16:38] kristian-aalborg: nope [16:39] erm, my new kernel reboots the box [16:39] also in recovery mode [16:41] 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] I'm running 10.4 - I did a make localmodconfig and then tweaked it [16:41] kristian-aalborg: I suggest that you try building a plain unmodified kernel as a sanity check. [16:42] I got it via git [16:42] yeah, that's probably what I should do [16:44] something weird is that I called it ~custom, but it seems to have installed as -generic [16:45] 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] I'm building on Lubuntu 10.4 which should be the same, then installing on 10.4 [16:47] wut [16:47] aptitude wants to install tzdata and similar things [16:48] 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] might fix things... lemme see [16:48] kristian-aalborg: tzdata gets updated often -- probably not related to your kernel build/reboot issue. [16:49] yeah, I was thinking of BzImage [16:49] I edited debian/changelog to have a name that'd be different from my other kernels [16:49] kristian-aalborg: good plan, but ... [16:50] this reflects in the names of my .debs, so weird it's not showing upon install [16:50] kristian-aalborg: note that debian/changelog gets overwritten (copied from) debian.master/changelog during the "fakeroot debian/rules clean" phase ... [16:50] I did it before [16:51] 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] one moment, I have to fire up another pc then [16:52] 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] ah, that's okay [16:53] 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] yes [16:54] 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] kristian-aalborg: I often build test kernels with a "~unchanged" version string addition. [16:55] I fooled around with dpkt and apt-get to try to "fix" the .deb that would not install [16:56] I seem to have locked linux-generic in the process, unwise as I am [17:01] 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] they say "dependency hell" as if there is a "dependency heaven"... sigh [17:16] I'm wondering... since this is from git, could it be partly unmet by the repos? [17:17] kristian-aalborg: unlikely -- the git repo's "master" branch should always produce a kernel that builds and installs properly. [17:17] ok [17:19] kristian-aalborg: I wonder if you have some leftover bits installed from your first failed installs. try this: [17:19] dpkg -l | grep "~custom" [17:19] this should list all packages that you have installed which have "~custom" in their name [17:20] I still have all of it [17:20] kristian-aalborg: dependency issues? how about a paste of the errors? [17:20] hi hyperair [17:20] hi [17:20] so how about pastebinning your errors [17:21] these issues were my own fault... I was missing a .deb [17:21] you could remove (with dpkg) all of your "~custom" packages to clean up. [17:23] I'm trying once more now the dependencies seem fixed [18:05] ah, enough for now [18:08] 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] kamal: ping [20:21] fakeroot debian/rules clean [20:21] fakeroot debian/rules binary-generic [20:21] only these two commands needed for the "sanity check"? [20:29] hi, would somebody update kernel-wedge to be newer than current squeeze/sid version? === ogra is now known as Guest23759 [20:48] 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] I'll do that as well, then... although not in that order [20:52] btw the system I'm building on is Lubuntu 10.4, not Ubuntu... but should not matter, I think