/srv/irclogs.ubuntu.com/2008/11/05/#ubuntu-kernel.txt

NCommanderI did all that00:01
TheMusoNCommander: Ok.00:01
NCommanderVery strange00:01
TheMusoLet me know when its ready to pull.00:01
NCommanderhttp://kernel.ubuntu.com/git?p=mcasadevall/ubuntu-jaunty-ports.git;a=summary - I pushed it, but I don't see the tag ....00:04
NCommanderTheMuso, oh, it seems tags aren't automatically pushed00:10
=== asac_ is now known as asac
TheMusoNCommander: aaaaahhhhh!00:12
NCommanderTheMuso, lets try that again00:13
TheMusoThis is a nice learning experience.00:13
NCommanderI dunno fi I call the lack of automatic pushing of tags a feature or a bug00:13
NCommanderIts uploading now00:13
TheMusoOk.00:13
TheMusoI call it a bug personally, but thats just me.00:14
NCommanderSOmeone should note that you need to git push --tags :-)00:14
TheMusoYeah.00:14
NCommanderIts designed so if you pull someone elses branch, you don't get private tags from during release00:14
NCommanderwow, 10MB worth of tags00:14
NCommanderLinus has been busy ;-)00:14
TheMusoOuch.00:15
NCommander(ubuntu-ports tags are obviously enough Ubuntu-ports vs Ubuntu so we can't accidently get the same tag)00:15
TheMusoNCommander: Well you probably need to change the debian/rules files to look for those tags then.00:15
TheMusoOtherwise the insertchanges et al commands will fail.00:15
NCommanderProbably00:15
NCommanderTheMuso, that change is in my branch, once 1.1 is released, it will be available for 1.2 (or 2.1)00:17
TheMusoNCommander: ok.00:17
NCommanderTheMuso, TADA http://kernel.ubuntu.com/git?p=mcasadevall/ubuntu-jaunty-ports.git;a=summary00:24
NCommanderThe changelog is amusingly long00:25
NCommanderand00:25
NCommanderI think incorrect00:25
NCommanderDamn it00:25
NCommanderFreaking insert changes pulled in stuff it shouldn't00:25
NCommanderactually, wait, it only grabbed 2.6.27->2.6.27.400:26
NCommanderWhich is correct00:26
=== CarlFK1 is now known as CarlF1
TheMusoNCommander: ok.00:27
NCommanderOk, so just grab my branch, build a source package (with a orig.tar.gz), sign and upload00:27
TheMusoWill do.00:28
TheMusoNCommander: Do you want me to give it a test build on PowerPC hardware?00:53
NCommanderTheMuso, sure01:42
NCommander(I tested it on my box, but I haven't tested it since fixing the other archs, but there were no code changes)01:42
TheMusoRight.01:53
NCommanderTheMuso, if you do, save the abi folder01:53
NCommanderWe'll need to generate those on all architectures from this release forward, since we'll have lbm and lrm soon01:53
TheMusoNCommander: I'm building in an LVM snapshot with sbuild.01:53
NCommanderoh01:54
NCommanderOk01:54
TheMusoI can grab it during the build however if you like.01:54
NCommanderIts not a priority until we start getting lrm and module packages01:54
TheMusoIs it created early on?01:54
NCommanderNo01:54
NCommanderTowards the very end of the build01:54
TheMusoRight.01:55
TheMusoNCommander: actually I will build it manually, so I can get the ABI folder.02:00
* NCommander nods02:00
TheMusoNCommander: I thought there was a bug opened for ports kernel in intrepid to not use gcc 4.1 for powerpc, yet I see it in the build-deps.02:01
NCommanderI haven't cleared it yet02:01
NCommander1.2 build task02:01
TheMusook02:02
NCommander(doko wants to zap 4.1, once 1.1 is uploaded, that will be the first thing I do, since I need to make sure we don't have any nasty ices on any platform and still have working kernels)02:02
NCommanderi.e., I want a baseline to work against02:02
TheMusoRight.02:03
TheMusoNCommander: Kernels are cooking.02:34
NCommanderI thought I smelled something burning ;-)02:34
* NCommander runs from the bad pun02:34
TheMusoIt still made me laugh however.02:34
NCommanderYay, 7 packages pending uploading (with an eight pending successful pbuildering)02:35
* TheMuso slaps his head. I should have told it to use both CPUs to build faster...02:35
NCommander-j2 is broken02:35
TheMusoOh ok.02:36
TheMusoThat solves that then.02:36
NCommanderIt kinda works02:36
NCommanderBut you get a weird race condition which causes dpkg to explode02:36
TheMusoRight.02:36
NCommanderI need to sit down and debug it at some point02:36
TheMusoI wonder if that can be sorted out.02:36
NCommanderEnviornmental variable which just passed -j to the kernel build02:36
NCommanderWHich is what is already implemented02:36
TheMusoYeah I saw that.02:36
NCommander(KERNEL_CONCURENCY_LEVEL or something)02:36
TheMusoYeah.02:37
TheMusoNCommander: powerpc kernel cooked, powerpc-smp kernel now cooking.03:19
* NCommander holds the extinisher ready03:21
TheMusolol03:22
TheMusoNCommander: powerpc64-smp now cooking.03:37
NCommanderTheMuso, can you test run them?03:38
TheMusoNCommander: As in try to boot from them? Sure.03:38
NCommanderTheMuso, since we're on the topic of things to be done03:50
NCommanderTheMuso, can I get a few sponsoring on other packages?03:50
TheMusoNCommander: Sure. Shall we take it to a more appropriate channel?03:56
NCommandermotu or devel, your pick03:56
TheMusoNCommander: doesn't bother me, whatever suits you.03:57
TheMuso:p03:57
TheMuso\/c03:57
TheMusoWow documentation takes a while.04:47
NCommanderTheMuso, yup04:50
* NCommander should have told you to debuild -B04:50
TheMusoOh well.04:51
NCommanderTheMuso, did you get your zinc acocunt fixed?04:51
TheMusoNCommander: Its in progress I believe.04:53
TheMusoNCommander: kernels done.05:05
TheMusoI can smoke test powerpc, and powerpc64-smp. I don't have a generic powerpc-smp box though.05:05
NCommandernow do they boot?05:05
TheMusoBout to try powerpc64-smp.05:05
NCommanderpowerpc-smp will work fine on powerpc, or on a powerpc64-smp box05:06
TheMusoOk.05:06
TheMusoNCommander: booting into powerpc64-smp.05:08
* NCommander crosses fingers05:08
TheMusoIt boots.05:09
TheMusoOk sound works, all disks present and correct, hrm not sure what else to check.05:11
NCommanderGood enough for me05:16
NCommanderThe powerpc kernel been tested05:16
TheMusotesting powerpc-smp now.05:16
NCommanderTheMuso, just as a reminder, remember to leave my name on the changelog (on the bottom) so I get the build failure notices if any occur :-)05:16
TheMusoNCommander: since you fixed the changelog, that is not a problem.05:17
TheMusohrm powerpc-smp doesn't want to boot.05:20
TheMusoon my G5./05:20
NCommandercoooooool05:20
TheMusoyeah05:20
TheMusoit brings up a screen with a lot of OpenFirmware stuff, or thats what it looks like.05:20
TheMusook will try the powerpc and powerpc-smp kernels on my mini.05:22
NCommanderHrm05:23
NCommanderthe smp kernel might be hosed05:23
TheMusohaha and the old boot option is broken. Time to dig out a desktop CD from hardy...05:23
NCommanderI'll have to smash it with a stick but unless I can find someone with a 32 bit SMP box05:23
NCommanderTheMuso, maybe the -smp kernel for some ungodly reason tries to put the G5 into little endian mode which would crash and burn05:26
TheMusopossibly.05:28
TheMusoNCommander: what makes you think that?05:29
NCommanderIts the only thing that could possibly cause the kernel to fault all the way back into open firmware05:29
TheMusoNCommander: right05:29
NCommanderAt least thats what I'm thinking05:29
NCommanderIf it works on your mini, yay, if not05:29
NCommander1.2 :-)05:29
* NCommander hears a gunshot05:30
* TheMuso slaps his head.05:30
TheMusoI was trying to boot old on my mini, not the G5.05:30
NCommanderoh05:31
NCommanderYour mini crashed and burned05:31
NCommanderNice :-/05:31
TheMusono05:31
NCommanderWait05:31
NCommanderhuh?05:31
NCommanderWhat machine failed to boot the smp kernel?05:31
TheMusoWhen I tried to boot into another kernel on what I thought was my G5, it didn't work, but it was on my mini.05:32
NCommanderOh I see05:32
TheMusothe G5 failed to boot the powerpc-smp kernel.05:32
* NCommander is resmoketesting the -smp kernel05:32
NCommanderI dunno why we have an non-smp/smp varient05:32
NCommanderEvery other architecture is compiled to smp05:32
TheMusoYeah I know what you mean.05:33
NCommanderTHere may be issues with the smp kernel on non-smp PPC hardware05:34
NCommanderTHats the only reason I can think of05:34
NCommanderThe G4 made it through a full startup with the SMP kernel05:34
NCommander(its a single chip box)05:34
TheMusoRight.05:34
NCommanderI think there must be hardware the SMP kernel crashes and burns with05:34
NCommanderTheMuso, I think we can write the issue as "Needs Investigation" and upload it05:35
TheMusoOk.05:35
NCommanderTheMuso, I just had a brainwave05:40
NCommanderTheMuso, your mini might have faulted because the kernel uses OpenFirmware to determine the presence of a second processor05:40
NCommanderWant to be on your mini crashed and burned due bad OF information?05:40
NCommander*bet05:40
TheMusoNCommander: it was the G5.05:41
TheMusoNCommander: not the mini.05:41
NCommanderOh!05:42
NCommandersame point applies ;-)05:42
TheMusoRight.05:42
TheMusoBut powerpc64-smp worked.05:42
NCommanderand powerpc-smp worked on non-smp hardware05:42
NCommanderWe need someone with an SMP G405:43
TheMusoYep.05:43
TheMusook powerpc works on the mini05:47
NCommanderso either smp is broken on smp hardware :-/, or smp is broken on smp6405:49
TheMusoNCommander: NCommander Well 64-smp is fine, as I am now back on that with my G5, and both CPUs are showing.05:52
NCommanderI think infinity or lamont have to have a multicore non-SMP G505:52
NCommandercan you boot a powerpc kernel on your G5?05:53
NCommander(maybe its a general 64-bit issue vs. smp)05:53
TheMusoNCommander: the powerpc kernel non-smp boots fine.05:53
NCommanderok05:53
NCommanderWe'll have to mark that on the Needs Debugging list05:53
TheMusoNCommander: powerpc-smp boots on mini.05:59
NCommanderwoooo06:00
NCommanderso its just a 64-bit issue06:00
TheMusosounds like it.06:01
NCommanderdo we care enough to fix it at this very moment?06:02
TheMusoI don't.06:03
* NCommander doesn't06:06
TheMusoNCommander: i have some things to do so I'll look further into this later.06:13
NCommanderTheMuso, the smp crash, or uploading ;-)?06:13
TheMusoNCommander: uploading.06:13
NCommanderok, no06:13
NCommander*np06:13
NCommanderah, abogani 07:32
aboganiNCommander: Hi07:32
NCommanderabogani, I've been working on linux-rt-powerpc, and I found a rather disturbing problem07:33
NCommanderThe current rt kernel in Intrepid isn't actually RT :-/07:33
abogani:-?07:33
NCommander(CONFIG_PREEMPT_RT is not defined)07:33
NCommanderand I can be blamed for it07:34
* NCommander whacks head on the desk07:34
aboganiNo way: it is defined.07:34
NCommanderNope07:35
NCommanderabogani, here's the debdiff07:35
NCommanderoh wait07:36
NCommanderbah07:37
NCommanderScrew me, I can't spell "PREEMPT"07:37
NCommandermorning smb_tp 08:05
smb_tpGood morning NCommander 08:06
NCommandersmb_tp, how goes your morning08:06
smb_tpNCommander, Good so far. :) Just got the first coffee. Saw your mail08:07
NCommandersmb_tp, TheMuso will be uploading the first ports kernel soon, and I'm bending linux-ports-lrm into shape :-)08:08
smb_tpNCommander, Sounds great. :) I guess I will give the mail some time today to be seen by others and then pull it to the repo.08:10
NCommander\o/08:11
NCommandersmb_tp, if you have sometime at some point to sit down with the ia64 config files, and figure out what things should be built as modules, it would be apperiated because then I can fix d-i for ia6408:11
smb_tpNCommander, I only had a config that compiled (but had to discard serial-modules) and produced some udebs but whether this really is useful for the installer, I don't know.08:16
NCommandersmb_tp, someone who knows the hardware needs to sitdown and smash the kernel into shape :-/. Even HPPA has working d-i/udeb support and thats the architecture thats usually broken08:16
smb_tpNCommander, True. I will try to ask BenC whether he got a little time to help. At least he has the HW08:18
NCommanderOh, I thought you had ia6408:18
NCommanderd'oh08:18
smb_tpNCommander, No, I only have access to one (but only as user, so I can't install new kernels)08:20
NCommanderoh right08:20
=== lamont` is now known as lamont
nodeboy_999hello14:12
nodeboy_999does apt-get <linux-kernel> provide a static or dynamic kernel image for any given kernel?14:12
=== smurfix is now known as smurf
drunkenkillahello15:04
drunkenkillai got a problem15:04
drunkenkillai can't change the brightness...the fn-keys and the applet in the panel doesn't work15:05
drunkenkillai tested even now pre-release of fedora 10 and i could change the brigthness with the applet in the panel15:05
mjg59F10 implements opregion support which is required for backlight control on a bunch of Intel graphics laptops15:15
mjg59It'll be in 2.6.28 of the upstream kernel, but it's not in Intrepid15:15
psusiisn't there a libata option somewhere for verbose debugging output?17:07
rtglamont: https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27 has finished building. this time it should _really_ fix your b44 issue.17:11
lamontrtg: and which suite does it show up in, I wonder?17:12
lamontintrepid-proposed?17:12
rtglamont: yes.17:13
lamontkewl17:13
rtglamont: adventurous souls such as yourself should always have -proposed enabled :)17:14
lamontheh.  not.17:14
lamontwell. maybe pinned at 25 :-)17:14
BenC1rtg: I'm worried about the patch that fixes backlight key...it's not in upstream yet18:05
drunkenkillaBenC1: which patch? i have problems too witch backlight18:06
BenC1drunkenkilla: what's the problem you are having?18:07
=== BenC1 is now known as BenC
drunkenkillai can't change the brightness18:07
drunkenkillai'm using ubuntu 8.10 and i can't change the brightness with the fn-keys and the applet in the panel18:08
BenCCould be fixed by this patch18:08
drunkenkillabut today i tested pre-release of fedora 10 and i could change the brightness with the applet, but not with the fn-keys18:08
BenCThe case I'm fixing is where the brightness key causes two key press events18:09
drunkenkillai will show you dmesg...18:09
drunkenkillaBenC: http://paste.ubuntu.com/67995/18:10
BenCdrunkenkilla: full dmesg would be better18:13
drunkenkillaBenC: http://paste.ubuntu.com/67998/18:15
drunkenkillare18:29
drunkenkillaBenC: when will come this patch?18:50
BenCdrunkenkilla: not sure18:51
mjg59BenC: You get an ACPI key event and an event from the keyboard?18:52
psusiwhat did you have to do to see KERN_DEBUG printks again?19:46
PiciHowdy kernel people.  It looks like the current kernel compiling help on help.u.com assumes that the user is running Intrepid. I don't really know enough about kernel compiling to split out the directions, but this is the wiki diff that appears to be the culprit: https://help.ubuntu.com/community/Kernel/Compile?action=diff&rev1=69&rev2=6120:05
Picilinux-kernel-devel is not on Intrepid and makedumpfile isnt on anything pre intrepid20:06
BenCmjg59: yeah21:02
NCommanderhey BenC 21:11
BenCNCommander: hey21:45
NCommanderBenC, did you see my email to the list?21:46
mjg59BenC: I suspect gnome-power-manager is the right place to handle that22:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!