[02:01] <wrostek> Im trying to make a kernel bisect, but my compile is failing, and not outputting an error.. can someone tell me where the error is occurring? http://pastebin.com/Ms19YxMm
[02:05] <wrostek> whoops i found it ndiswrapper way at the top
[04:06] <wrostek2> Im trying to bisect a problem with my rt2x00 wireless drivers. In 3.0.0-16-generic oneiric it works, but in 3.1.0-1-generic precise it does not.   How do I get a git pull of changes between those kernels? they are on two separate repositories no?  git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git and git://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git
[04:06] <wrostek2> Im trying to bisect a problem with my rt2x00 wireless drivers. In 3.0.0-16-generic oneiric it works, but in 3.1.0-1-generic precise it does not.   How do I get a git pull of changes between those kernels? they are on two separate repositories no?  git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git and git://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git
[04:07] <ohsix> you can add the other one as a remote head
[04:07] <ohsix> dunno how bisect will work with that, but they're like any other label afaik
[04:08] <wrostek2> thanks
[05:02] <pkh> i'm running a machine on 12.04 and the last few kernel updates have failed to find my network driver. i'm wondering what I should do wrt to reporting that.
[05:03] <ohsix> is it an rt2x00 driver device?
[05:04] <ohsix> there are a lot of people that have been talking about network drivers disappearing and stuff, if not the changelog for the kernel; there should be other people asking in bug reports
[05:07] <pkh> k, will keep searching launchpad -- and add what info I can find there.
[07:14] <wrostek> I have precise beta2 installed, can I run a 2.6 kernel?
[07:19] <wrostek> The first commit in the git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git is for a 2.6.0-r2 kernel, can I compile this and run it on my precise machine?
[07:25] <wrostek> I Have to bisect test my r2x00 wireless drivers, they worked in oneiric, but not in precise.  I have the git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git cloned, and tried to checkout from the very first commit ( to see if the earliest version in precise works ) but that version gives debian/rules: No such file or directory
[07:26] <wrostek> Is there a trick to finding which commit in precise begins, and oneiric ends?
[07:26] <wrostek> Precise git doesn't start where oneiric ends does it?
[07:26] <ohsix> have you looked at git log from precise for the files related to your driver?
[07:26] <wrostek> yes
[07:27] <ohsix> when you say it doesn't work; how do you mean
[07:28] <wrostek> and I tried compiling at points where those happened, but the problem still persists… It works in oneiric 3.0.0-18-generic
[07:29] <ohsix> describe "doesn't work" with the precise kernel
[07:29] <wrostek> The wifi driver will work, but if I go to speediest and check the speed, it will get half way through the test, then stall….  I have to restart my network to get it running again
[07:29] <ohsix> ok
[07:29] <wrostek> sorry speediest ( speediest.net )
[07:30] <wrostek> speedtest.net
[07:30] <ohsix> you may find it easier to bisect linux-wireless
[07:30] <ohsix> did you ask anyone if they knew about this problem already?
[07:30] <wrostek> in oneiric it works fine, precise is broken..   So I checked out precise, I thought precise would start at a version where oneiric ends
[07:31] <wrostek> Yes, they hadn't, and I created a bug in ubuntu https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&ved=0CD4QFjAD&url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F965043&ei=2rJ2T5y0D8ehgwer3dnTDg&usg=AFQjCNFHRs4kuBd6E1IcL1Enbb14B6r_vw&sig2=BDeONK-wyDkWkskMTANcgg&cad=rja
[07:31] <wrostek> sorry
[07:32] <wrostek> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965043
[07:32] <ubot2> Launchpad bug 965043 in linux "rt2x00 random stalls in AP Mode - 12.04 Beta 1" [Medium,Confirmed]
[07:32] <wrostek> They asked me to bisect it, Im trying to find a good point in precise ( where the drivers work ) but so far nothing
[07:34] <wrostek> I wanted to checkout precise to the very first commit in that repository, but that is a 2.6 kernel.. weird, I thought it would be like 3.0.18, ( like where oneiric ended )
[07:34] <ohsix> well they're both copies of the same repo, with some stuff on top
[07:35] <wrostek> So, in precise , should I be able to find 3.0.18 kernel?
[07:35] <wrostek> Because I couldnt
[07:35] <ohsix> there's no tag for it?
[07:35] <wrostek> I greped for Ubuntu ( as in Ubuntu-3.0.18 )
[07:35] <wrostek> no, they only have two tags
[07:36] <wrostek> Oh, sorry more than two, but they start at Ubuntu-3.1.0-1.0 ( and I built that one and it didn't work, same problem )
[07:37] <wrostek> How can I find the changes between oneiric ( 3.0.18 ) and precise ( 3.1.0-1.0 ) ?
[07:38] <ohsix> get the commit hash for 3.0.18 in oneiric and use it as "good" in the precise tree, i dunno how to find the closest common commit but there are lots of common commits
[07:39] <tdmackey> wrostek: there are plenty of ubuntu tags in precise
[07:39] <tdmackey> maybe you didn't pull all the tags down
[07:39] <wrostek> git log master -g --grep=Ubuntu-
[07:40] <wrostek> that didn't pull them down?
[07:40] <tdmackey> that doesn't pull down anything
[07:40] <wrostek> ( sorry I'm kind of new at this )
[07:40] <tdmackey> git tag -a will list all the tags
[07:40] <tdmackey> or just git tag rather
[07:41] <wrostek> oh cool,
[07:41] <tdmackey> then you can to a git checkout <tagname>
[07:41] <tdmackey> and build from there
[07:41] <wrostek> ok thanks
[07:41] <tdmackey> I wouldn't start at the first tag, I'd start at the last known good tag.
[07:41] <wrostek> i will try this
[07:42] <tdmackey> unless you've never run precise before, then you're out of luck I guess.
[07:42] <wrostek> I think it is v3.0-rc7 ( i think thats the last oneiric )
[07:42] <wrostek> thanks tdmackey
[07:42] <tdmackey> yeah, I'm just saying going in order will take a long time. Binary search is a better approach if you have no other knowledge as to a decent version.
[07:45] <tdmackey> wrostek: also of note, if you look at the top of the tag list youll see the ubuntu-version tags. the non-ubunutu tagged points are the vanilla kernel tags. 
[07:47] <ohsix> you can still just bisect net/ or net/wireless plus your driver too
[07:48] <wrostek> Maybe, I think they were giving me the impression the problem may be somewhere else than the driver though
[07:49] <ohsix> did you already see git log 3780d038fdf4b5ef26ead10b0604ab1f46dd9510 ?
[07:49] <wrostek> Is that about stalled rt2x00
[07:49] <ohsix> yes, from march 9th
[07:49] <wrostek> Yes, that did not fix this problem it was weird, 
[07:50] <wrostek> I think that guy needs to take another look
[07:51] <ohsix> the log entry is pretty concise
[07:52] <ohsix> http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2012-March/004651.html
[07:53] <wrostek> Yes,  I mentioned that in my bug report, ( and that fix is already in the precise rt2x00 drivers in beta1 ) but it did not help https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965043
[07:53] <ubot2> Launchpad bug 965043 in linux "rt2x00 random stalls in AP Mode - 12.04 Beta 1" [Medium,Confirmed]
[07:54] <ohsix> i didn't suggest it solved your problem, but that you may contact him
[07:54] <ohsix> or respond to the thread
[07:54] <wrostek> One question, is Ubuntu-3.0.0-1208.19 later than Ubuntu-3.0.0-13.21
[07:55] <wrostek> Yes, I was thinking about it, but I don't know how much spam he gets already from people with driver issues
[07:56] <ohsix> -13 is later
[07:57] <wrostek> thansk
[07:57] <wrostek> thanks
[13:17] <dileks_> hi
[13:17] <dileks_> I have installed precise-beta1 and updated to recent kernel
[13:18] <dileks_> this is linux-image-3.2.0-21-generic (3.2.0-21.34)
[13:18] <dileks_> (also I did all other software updates)
[13:19] <dileks_> I installed via wubi on an existing win7 partition on samsung series-5 ultrabook
[13:19] <dileks_> on shutdown the machine freezes
[13:19] <dileks_> I have to power-off via power-button
[13:20] <dileks_> (I had no look into syslogs, yet)
[13:20] <dileks_> with 3.2.0-17.27 and 3.2.0-20.33 kernels I am not aware I had this new issue
[13:22] <dileks_> any known issue?
[13:23] <dileks_> I can paste dmesg and more if this helps you
[13:26] <dileks_> dmesg: http://paste.debian.net/161537/
[14:42] <kklimonda> AceLan: ping
[14:46] <kklimonda> AceLan: just heads up, the patched kernel from bug 969576 fixes one oops but creates another ;)
[14:46] <ubot2> Launchpad bug 969576 in linux "BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]" [Critical,In progress] https://launchpad.net/bugs/969576
[15:53]  * popey wonders what our btrfs support is like in 12.04.
[16:09] <AceLan> kklimonda: >_<
[16:10] <AceLan> kklimonda: I just add a comment, and it's 4/1 here, I really hope you're joking me 
[16:10] <kklimonda> AceLan: no, it's still 31/3 in Europe ;)
[16:17] <kklimonda> AceLan: ok, I've attached both lsmod and dmesg from 3.2.0-20
[16:20] <AceLan> kklimonda: thx
[16:46] <AceLan> kklimonda: i got the bug, compiling the new kernel
[16:47] <kklimonda> AceLan: great, thanks - any idea if it's somehow related to the fact that I don't get neither X nor terminal o 3.2.0-21? ;)
[16:47] <kklimonda> unless I boot into the rescue mode and then select "continue" from the recovery screen
[16:49] <AceLan> kklimonda: I think the asus-wmi module lead the system hang, so there is no X nor terminal
[16:49] <AceLan> kklimonda: rescue mode may not load any kernel module, so it works
[16:50] <kklimonda> AceLan: hmm, no - I get the oops in the rescue mode
[16:50] <kklimonda> AceLan: so at least in the rescue mode it doesn't hang
[16:50] <AceLan> @_@
[16:51] <kklimonda> oh well, if it keeps happening after this bug is fixed I'll just report a new one :)
[16:53] <AceLan> no~~~~~~~~~, it won't happen again
[16:55] <kklimonda> that's the spirit! ;)
[17:00] <AceLan> kklimonda: http://people.canonical.com/~acelan/bugs/lp969576/2/ # new kernel
[17:02] <AceLan> kklimonda: I'm wating your result, so that I can fall asleep with smile :)
[17:10]  * AceLan bites kklimonda 
[17:10] <kklimonda> AceLan: I'm already rebooting ;)
[17:10] <AceLan> kklimonda: hehe
[17:12] <kklimonda> AceLan: mm, everything looks fine
[17:12] <AceLan> yooooooooooooooooooooo
[17:12] <kklimonda> no oops, and I got lightdm
[17:12] <AceLan> kklimonda: cool
[17:13] <AceLan> kklimonda: time to sleep, bye~
[17:13] <kklimonda> AceLan: good night :)
[22:23] <ohsix> anyone have some idea what a high delay for "creating block layer request" in latencytop might indicate what is going on, and what i can do about it
[22:26] <ohsix> ah, it may be fuse related; but it destroys other disk io when it happens