[01:27] * dandel pulls ppa of latest 2.6.29 kernel. [01:27] ><; fun... regression from irq changes from acpi persists. === JanC_ is now known as JanC [01:58] 0o fun... should i report the bug pertaining to acpi_irq to the ubuntu launchpad or the bugzilla of the linux kernel? [02:04] does anyone know where i can get the 2.6.25 and 2.6.26 kernels as ubuntu packages? [02:05] dandel: if the bug is in an Ubuntu kernel, use LP [02:06] dtchan it affects the kernel-ppa also [02:06] 2.6.29 gives a different function error string when compared to 2.6.27 lol [02:07] and i can't use lp for this, my bug i had for it, which is not solved got labeled as duplicate ( although the bug evolved as i found more issues between the 2.6.24 and 2.6.27 kernels ) [02:07] it looks like 2.6.2[56] aren't in /mainline; they're not the base of any supported Ubuntu kernel releases [02:07] (discounting -ports) [02:08] bug # 294323 is when i first found issue [02:08] i kept it updated as best i could, in hope that it would be unflagged and fixed. [02:11] hmm... actually it's faster than 2.6.27 on responding to change, however it still is not as fast to notice the change in the power plug as 2.6.24 [02:12] however, it still has issue of automatically kicking out of suspend when plugged in for some reason [02:13] first suspend attempt always fails, then second one works [06:53] dandel: if the problem is upstream, you could update the LP bug saying so, so that the triager might link it to bugzilla.kernel.org. Or, you could directly report it there. [10:54] amitk, the issue is mainstream and i believe it appeared somewhere in 2.6.25 or 2.6.26 [11:03] dandel: I suggest updating the bug with this info _and_ if possible ping ogasawara who is the kernel QA [11:12] amitk, i'll just make a new bug and make sure it refers to the old one on the lp tracker. [11:15] wow... this is a new one 0o [11:15] which lead to corrupted low memory ><; [11:30] apw: is there way to revert things in a git index? [11:30] IOW, revert the results of a 'git add .' [11:31] you can update the index as often as you like [11:31] if what was in the index was whats in a commit you can get that back [11:31] if its was an uncommpitted previous add, then no [11:32] apw: it was uncommitted [11:32] so i believe that intermediat there is no longer linked [11:32] in theory it will still be in your object store [11:33] in a loose object ... so if there is something distinctive in it you might be able to find it [11:33] ie. its likely high effort, but it might be important enough [11:33] I did "git am ; git reset --soft HEAD^;" But this leaves everything cached in the index. I want it to go back to the uncommitted state and allow me to add files interactively [11:34] apw: probably not worth it trying to recover the object [11:35] hmm so i think you are saying you want the index to be HEAD^ [11:35] 'git add --interactive' allows this, but it is quite cumbersome to do it manually [11:35] apw: yes [11:35] so i think you want git reset --mixed [11:36] amitk, reported new bug as bug #338701 [11:36] Malone bug 338701 in linux-meta "acpi_irq is not set properly." [Undecided,New] https://launchpad.net/bugs/338701 [11:36] if you are already done the --soft [11:36] dandel: thanks [11:36] i think a git reset --mixed HEAD might do the trick ... as you have already moved your HEAD back one [11:36] it didn't add the mesg log tho. [11:37] --mixed [11:37] Resets the index but not the working tree (i.e., the changed files [11:37] are preserved but not marked for commit) and reports what has not [11:37] been updated. This is the default action. [11:37] so if a git show HEAD shows the commit against which you are trying to work [11:38] (now) then i think a git reset --mixed HEAD would reset the index only [11:38] apw: --mixed for the win! [11:38] cool [11:38] thanks [11:38] i always wondered why you might want that, now i know [11:38] useful split out a patch :) [11:39] *useful to [11:39] indeed :) [11:39] apw: apparently it is the default action... Only I wasn't trying to be so smart [11:40] heh so it is, i think i use --hard almost exclusivly [11:40] i've used --soft rarely, and the default never [15:05] apw: we did talk about an intrepid backport of the floppy patch, right? [15:05] Keybuk, yep, i am on the case [15:05] ok, I'll update the bug [15:05] its building in my build far right now [15:05] i'll be doing it in a sec anyhow [15:05] sure, just to track it for SRU purposes [15:06] Keybuk, i'll handle it .. .i am pushing some test kernels for intrepid now [15:06] when we have some test acks i'll push it through the SRU process [15:06] (of course it cannot fail as its an obvious patch but hey) [15:10] cking, battery discharge when suspended ... is there a sensible value we can make as the boundary from failure to success? [15:13] apw, not sure.. let me think for a minute about this. [15:13] a test isn't much of a test if it doesn't tell you if it was good or bad [15:14] probably not. in suspend you are keeping memory alive, and that's dependant on how much memory you have and so forth [15:14] yeah i guessed as much [15:14] the issue which is important is how much current is being drawn when in hibernation. One expects that to be zero - if it's not then something is not good [15:15] very true, so perhaps this test will become more useful once we start doing hib stuff ... [15:17] apw, yep. I think it should be on the agenda for hibernation testing. I wonder what horrors one will find... [15:18] a whole heap [15:20] the tricky part will be to factor out which part of the system is doing the current stealing === JanC_ is now known as JanC === pgraner_ is now known as pgraner [17:07] apw: you have positive results on https://bugs.launchpad.net/bugs/193970. please push the patch [17:07] Malone bug 193970 in linux "iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch" [Medium,Confirmed] [17:15] rtg thanks for the heads up. i believe one of the testers was a Jaunty user, the other I am unsure. so i propose pushing the jaunty one and holding intrepid until i have some solid results on there? ok? [17:16] apw: wfm. Jaunty is the only thing I'm intereted in right now. [17:16] fair enough... will get it in shortly === TimStarling is now known as Tim-away [18:48] Hi. I can`t build promise tx2650 driver for the 8.10 kernel. Has anybody done that? [18:51] tx2650: did you see this -> http://www.colinmackenzie.net/index.php?option=com_content&view=article&id=12:promise-satasas-driver-update-tx4650tx2650&catid=8:rotator&Itemid=7 [18:53] yes. Tryed to build with warious patches, somebody said the .28 kernel supports it so I build that kernel and it didnt detect it, so baiscally I`m running out of optiones. [18:53] options* [18:54] from colins site I get Error 2 on compilation [18:56] I noticed another one complaining about failed build on .27 kernel, so, it`s not my clumsiness [18:57] I see success reports using 2.6.24-16 [18:57] but that doesn't help you much [18:57] :) [18:58] I had to upgrade to 8.10....ž [18:59] is there a way to downgrade to 8.04 or could I just build a .24 kernel? [19:01] tx2650: just download the old kernel via synaptic or apt-get and install it. Then pick the old kernel at boot. [19:03] I tried that already but it says the package has no available version. I suppose I must set sth in sourcelist [19:07] how can I tell Intrepid to look for packages in Hardy repositories? [19:11] tx2650: https://help.ubuntu.com/community/DowngradeHowto === fddfoo is now known as fdd [20:40] What does SAUCE mean in the changelog? [20:40] ion_: its a patch that is not currently upstream. [20:40] What’s the etymology? :-) [20:41] as in 'special sauce'. I use it too keep track of patches that diverge from upstream [20:41] Alright, thanks. === pgraner_ is now known as pgraner === fdd is now known as pricolici [21:20] * bradF is back [22:44] Are kernel mainline builds available for 2.6.29 kernels? [22:45] * NCommander is having issues finding them. [22:45] NCommander: http://kernel.ubuntu.com/~kernel-ppa/mainline/ [22:47] thank you! [23:21] dtchan, on the 2.6.29 kernel should i report bugs pertaining to that to the linux mainline? [23:22] considering i am using the ppa kernel sources. === Tim-away is now known as TimStarling [23:24] dandel: yes; please be sure to note the pedigree clearly in the bug report (also, it's dtchEn) [23:25] shows as all lower case here. [23:25] yes, it is lowercase, but it's an 'e' not an 'a'. Anyhow, no big deal. My nick-highlight just doesn't trigger if you misspell it. [23:25] i did note the issue on 2.6.27 kernel, however i can't confirm the 2.6.26 and 2.6.25 kernel between long term. [23:26] so it's tougher to track the originating kernel. [23:26] did you try the mainline .24 base? [23:26] 2.6.24 worked fine [23:26] so i haft to find 2.6.25 and 2.6.26 which are both not on the mainline package list. [23:26] well, only three kernel versions, then. Not too shabby ;-) [23:27] i posted latest 2.6.29 dmesg but that changed when compared to 2.6.27. [23:28] * dandel combs the changelogs as best i can to figure out where the possible change happened. [23:28] !bug 338701 [23:28] Factoid bug 338701 not found [23:28] Malone bug 338701 in linux "acpi_irq is not set properly." [Undecided,Incomplete] https://launchpad.net/bugs/338701