[08:41] <smb> morning
[09:10] <lynxman> smb: moin moin
[09:11] <smb> lynxman, hey :)
[09:16] <lynxman> smb: :)
[09:27] <brendand> can anyone think of a good reason why iwlist wouldn't be able to scan properly where network manager can? wouldn't they use the same interfaces? (in Oneiric)
[09:28] <brendand> http://paste.ubuntu.com/763594/
[09:29] <brendand> apw - this is another Broadcom system, but this time the wl driver is installed
[09:30] <brendand> (from jockey-text -l) kmod:wl - Broadcom STA wireless driver (Proprietary, Enabled, In use) [auto-install]
[09:35] <apw> brendand, often the act of connecting to and aquiring a channel affects the ability of the card to scan
[09:35] <apw> so you find with some cards that if you run ilist constantly it will show the selected channel sometimes and a fuller listing others
[09:35] <apw> as nm cycles the card through the two modes
[09:36] <brendand> apw - no connections created on this system (/etc/NetworkManager/system-connections is empty)
[09:37]  * smb wonders whether that actually mean nm cannot scan either...
[09:38] <brendand> smb - i thought i got a scan out of nmcli a few minutes ago, but now that's not happening either
[09:38] <smb> is by chance some rfkill actiuve?
[09:38] <apw> on my brcm based systems i see the list come and go a lot from the command line
[09:39] <apw> and nm always has a list, i suspect nm i simply caching the result for some time
[09:39] <brendand> http://paste.ubuntu.com/763601/
[09:39] <brendand> apw - i'll just check, i certainly didn't activate it myself
[09:40] <brendand> crap, yes there is a hard block (i don't have physical access so no idea if the switch is actually flicked)
[09:41] <smb> There also was once a problem of two laptop drivers fighting over rfkill on Lenovo's
[09:41] <brendand> http://paste.ubuntu.com/763604/
[09:42] <smb> (somehow it went away for me and I think there has been a propoer fix too)
[09:42] <brendand> dell-wifi and brcmwl-0?
[09:43] <smb> one for what the hw thinks and the other often showing bios setting
[09:45] <brendand> i guess i'll have to wait for the lab engineer to confirm the state of the switch
[09:46] <smb> could be physical switch or hotkey
[09:49] <brendand> heh, i rebooted and now it's not hardblocked. not according to rfkill
[09:49] <caribou> morning; Do we provide a kernel module for the Realtek 8190 wireless adapter ?
[09:50] <brendand> but still iwlist doesn't work
[09:50] <apw> caribou, what are the PCI ids for it
[09:50] <caribou> apw: hold on ...
[09:50] <brendand> and nmcli now does
[09:50] <brendand> (i have no idea how dell-wifi got hardblocked before)
[09:50] <caribou> apw: 0a:02.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8190]
[09:50] <caribou> apw: Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8190] 
[09:56] <apw> caribou, sounding like it may be in a staging driver, at least in precise, no idea if it works, being realtek your milage may vary
[09:57] <apw> seems to have some support in oneiric too, but ... quality, from a realtek driver ... erm
[09:57] <apw> yet to be proven, you would need to test for sure
[09:57] <caribou> apw: yes, this is what I read from a few LP bugs.
[09:57] <caribou> apw: ok, thanks for checking
[09:58] <caribou> apw: may I ask what is a "staging driver" ?
[09:58] <caribou> and expect an answer ;-)
[09:58] <apw> new drivers which are too crap to be accepted into the kernel as they are
[09:59] <caribou> apw: ok, thanks. That's how I understood it
[09:59] <apw> that may be functionally, stylistically, structually
[09:59] <ogra_> philosophically :)
[10:01] <brendand> apw - so if iwlist isn't working and network-manager is, does anyone care?
[10:01] <apw> brendand, i think i heard yesterday that iwlist was using an old interface which was going to be deprecated
[10:01] <apw> and that we should demote the iw* commands
[10:02] <brendand> apw - i didn't expect it to be the case in Oneiric though. and that too on only one system
[10:02] <apw> brendand, on O am not sure 
[10:02] <brendand> or one network card as it were (BCM4322 802.11a/b/g/n)
[10:02] <brendand> tgardner said it could break in P anytime soon
[10:03] <brendand> is network manager the only authoritative tool, or what's replacing iw tools?
[10:05]  * apw would have to defer to tim, he mentioned it yesterday for the first tim to my ears
[10:14] <brendand> one last question before i go. who do i talk to about getting an item on the agenda for the kernel team meeting?
[10:18] <smb> brendand, joe (the one that sends out the meeting notes) or you just raise your hand when there is the question about open discussion
[10:21] <dupondje_> sforshee: thanks for replying to the bug.
[11:24] <apw> ppisati, fyi that 3.2 ti-omap4 kernel is in the archive now, it'd better work :)
[11:25] <ogra_> apw, yeah, else the masses of pand users will start compleining 
[11:27]  * apw prepares for both of them to complain at once
[11:27] <ogra_> i'll just give them paolos address ;)
[11:34] <apw> ogra_, heh good plan
[11:40] <ppisati> it boots here :)
[11:40] <ppisati> and it drives my lcd, so it's good
[11:41] <ppisati> release it! :)
[11:44] <apw> ppisati, oh i already did ... :) ... meta will be in the archive shortly, and the screaming will begin
[12:19] <apw> ppisati, ok all published, let the fun begine
[12:45] <ppisati> apw: cool, just found a problem
[12:51] <apw> ppisati, bad ?
[12:52] <ogra_> campfire on the SoC surface ? :)
[12:52] <ppisati> :)
[12:52] <ppisati> nope
[12:52] <ppisati> hangs on reboot in there's a usb hdd mounted (musb problem)
[12:52] <ppisati> didn't notice cause i was running off the sd card
[12:52] <ppisati> i'm testing a workaround now
[12:53] <ppisati> and perhaps i found the guilty commit
[13:15] <smb> crashtime...
[13:15]  * ppisati -> lunch
[15:22]  * ogasawara back in 20
[15:26] <cking> it's getting really stormy here, if I dropoff line it's 'cos my power has gone
[15:30] <ppisati> cking: i've 14C here, do you want some? :)
[15:31] <ppisati> seems the winter is really late this year...
[15:31] <cking> ppisati, I will swap you the warmth with the UK wind + rain
[15:52] <herton> GrueMaster, about bug 893190, it's needing verification. I think you will want to verify it while doing qa of current maverick ti-omap4? In this case we can mark that as verification-done
[15:52] <ubot2> Launchpad bug 893190 in linux-ti-omap4 "Qa-testing failures for 2.6.35-903.27" [Undecided,Fix committed] https://launchpad.net/bugs/893190
[15:53] <GrueMaster> herton, yes I plan on it.  I have been working with the security team to get the QRT suite working on arm.  That came up as a "needs kernel fix", hence the bug report.
[15:55] <GrueMaster> And actually, I will test it as part of the "Regression-testing".
[15:55] <herton> GrueMaster, ok, I'll mark that bug as verified then, so the tracking bug of current maverick ti-omap4 can go to Testing
[15:55] <GrueMaster> ok
[16:06] <tgardner> arges, mumble ?
[16:06] <arges> tgardner, ahh was just about to call 
[16:06] <arges> let me unmute
[16:06] <arges> tgardner, ok hold on getting mic
[16:08] <arges> tgardner, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/836250
[16:09] <ubot2> Launchpad bug 836250 in linux "[Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops" [Critical,In progress]
[16:09] <arges> https://bugs.launchpad.net/bugs/876147
[16:09] <ubot2> Launchpad bug 876147 in ubuntu "Intel Corporation Centrino Wireless-N + WiMAX 6150 (rev 67) not working after upgrade to 11.10 (dup-of: 836250)" [Critical,Confirmed]
[16:14] <ogasawara> arges: just fyi, I've pinged our intel contact about bug 836250.  they were unfortunately unable to reproduce.  I've got jsalisbury working with the original bug reporter to narrow down the regression window.
[16:14] <ubot2> Launchpad bug 836250 in linux "[Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops" [Critical,In progress] https://launchpad.net/bugs/836250
[16:17] <arges> ogasawara, yea i've been speaking with him too
[16:59] <brendand> rtg_ - hi
[16:59] <rtg_> brendand, dude
[17:00] <brendand> rtg_ - quick question, how reliable is iperf going to be in a high noise environment?
[17:00] <brendand> rtg_ - say i have 3-4 systems hitting the iperf server simultaneously?
[17:00] <rtg_> brendand, its as reliable as the underlying TCP connection.
[17:01] <rtg_> I presume the iperf server is at the end of an ethernet cable ?
[17:01] <brendand> rtg_ - it will be. right now it's not because i'm testing it in my home office
[17:02] <rtg_> brendand, so I'm not sure what you mean by reliable.
[17:28] <brendand> rtg_-  in terms of the bandwidth figures given by iperf
[17:29] <brendand> rtg_-  in my current setup i get a figure of between 5 and 8 Mbits/sec
[17:29] <rtg_> brendand, with multiple simultaneous wifi clients?
[17:30] <brendand> rtg_-  would that go down significantly given a few systems trying to hit the same server?
[17:30] <brendand> rtg_-  this is with just one
[17:30] <rtg_> brendand, try it with an ethernet client
[17:31] <brendand> rtg_-  the client is always going to be wireless in these tests though
[17:31] <brendand> rtg_-  the server could well be wired to the router
[17:31] <brendand> so the scenario would be 1+ clients connected to a router with a server wired to that router
[17:31] <rtg_> brendand, _first_ establish the stability of iperf wrt consistent bandwidth measurements.
[17:32] <brendand> rtg_-  are you suggesting to wire both systems to the router?
[17:33] <Awsoonn> Hi all, Can I get some feedback on my line of thought in bug 901770 plase? Thank you~
[17:33] <ubot2> Launchpad bug 901770 in linux "Kernel Bug in bluetoothd?" [Undecided,New] https://launchpad.net/bugs/901770
[17:33] <rtg_> brendand, not to the router, but to the switch so that both are in the same subnet and have not extraneous HW between them.
[17:34] <rtg_> s/not/no/
[17:35] <brendand> rtg_-  right, i'll try that if i can
[17:36] <brendand> rtg_-  are there any other ways we could detect these wireless issues?
[17:37] <rtg_> brendand, there will be connect/disconnect messages in dmesg if you've a troubled connection.
[17:37] <brendand> rtg_- i only wish i had access to a system troubled by problems like this
[17:39] <brendand> rtg_-  what phrases might i look for?
[17:39] <rtg_> brendand, yank the plug on your AP and look in your dmesg
[17:40] <brendand> rtg_-  ok. i was wondering if that would be a realistic test. i'll try it
[17:40] <rtg_> brendand, there is also prolly some dbus traffic that goes to NM when a connection fails.
[17:40] <brendand> i'll see if i can try both those things. thanks
[18:01] <smoser> smb, ping
[18:01] <smoser> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/876956
[18:01] <ubot2> Launchpad bug 876956 in linux "starting interactive atop causes kernel alignment check" [Undecided,Incomplete]
[18:11] <Awsoonn> another newb question, If I'm tracking down a kernel bug, which version of the kernel source shoudl I be making modifications to? The latest Linus release, or the latest ubuntu release, or something else altogether?
[18:14] <bjf> Awsoonn: if you intend to submit a patch to upstream, you should be moding Linus' tree
[18:16] <Awsoonn> bjf: Thanks! Will I be able to use the latest kernel with 11.10 without much issue? Or is it luck of the draw?
[18:16] <bjf> Awsoonn: you should be able to use it
[18:17] <bjf> Awsoonn: note, the current upstream kernel is currently at rc4 meaning it could be problematic
[18:18] <bjf> Awsoonn: it's probably safest to start with our Oniric sources, determine your patch then port it to Linus' tree (which shouldn't be much of a port depending on what you are doing)
[18:18] <Awsoonn> I'll be working in the bluetooth stack, do you think it would be reasonable to use the latest release rather than -RCx?
[18:19] <bjf> Awsoonn: i don't know how much churn that area of the kernel is getting
[18:19] <Awsoonn> not much by the looks of it, last modification was on Oct 24 if I'm reading things correctly...
[18:21] <bjf> Awsoonn: then i'd do as i suggested and hack on the oneiric sources and then work with the upstream maintainer to get it upstream (they'll want patches against linus' tree)
[18:22] <Awsoonn> ok, that's great! :) Now I've got someplace to start.
[18:27] <Awsoonn> ok, I just did a little bit more digging and found that upstream has already changed the function I was about to modify. I'm wondering if my bug is already fixed, so is there a prefered method for installing a more recent kernel?
[18:33] <vanhoof> herton: looks like lts-backport-oneiric should be released soon, yeah?
[18:33] <vanhoof> herton: (based on the tracking bug)
[18:33] <herton> vanhoof, it's released on updates
[18:33] <herton> -updates/-security
[18:34] <herton> at least rmadison already shows it
[18:42] <bjf> Awsoonn: just download the appropriate .deb for Precise and install it
[18:44] <bjf> Awsoonn: are you running amd64 or i386 on a desktop ?
[18:44] <Awsoonn> bjf: fair enough, I wondered if that would work or not, thanks! AMD64
[18:45] <Awsoonn> and it's on a laptop if that matters at all to you
[18:45] <bjf> Awsoonn: https://launchpad.net/ubuntu/precise/amd64/linux-image-3.2.0-3-generic/3.2.0-3.9
[18:47] <Awsoonn> does the version string 3.2.0-3 and no '-ubuntuX' indicate that this is RC3 and there is no Ubuntu sause added yet?
[18:48]  * rtg_ -> lunch
[18:50] <apw> Awsoonn, https://wiki.ubuntu.com/Kernel/FAQ#Kernel.2BAC8-FAQ.2BAC8-GeneralVersionMeaning.What_does_a_specific_Ubuntu_kernel_version_number_mean.3F
[18:50] <Awsoonn> that's quite the URL, thanks!
[18:50] <apw> yeah the wiki is a bit pants
[19:04] <bjf> Awsoonn: our kernels always come with sauce :-)
[19:33] <brendand> rtg_-  all i get in dmesg that looks useful is:
[19:33] <brendand> [ 1295.068497] cfg80211: All devices are disconnected, going to restore regulatory settings
[19:36] <jsalisbury> bjf, I'll be updating bug 836250 shortly.
[19:36] <ubot2> Launchpad bug 836250 in linux "[Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops" [Critical,In progress] https://launchpad.net/bugs/836250
[19:36] <vanhoof> herton: perfect, thanks!
[19:36] <bjf> jsalisbury: thanks, sorry to bother you
[19:37] <jsalisbury> bjf, heh, no problem.  Thanks for keeping up with the bug ;-)
[19:42] <brendand> rtg_-  it looks like that bug above should affect a few systems we have. i can test my test on that
[19:45] <awsoonn> well, the percise kernel still contains my bluetooth bug, onward to vanila-RC4 I suppose.
[20:11] <rtg_> apw, I keep getting Mainline Build v3.2-rc4 messages
[20:22]  * cking kicks off an overnight soak test and calls it a day...
[21:08] <chrisccoulson> i've just updated my precise machine for the first time since i switched to precise, and i can't boot the current precise kernel
[21:08] <chrisccoulson> i just get a whole bunch of these messages flashing rapidly by on screen:
[21:08] <chrisccoulson> http://paste.ubuntu.com/764247/
[21:09] <chrisccoulson> it doesn't even get as far as plymouth
[21:09] <chrisccoulson> i left it for a few minutes, but had to switch it off when my laptop felt like it was going to burst in to flames
[21:12] <Awsoonn> chrisccoulson: I'm no expert, but it looks like you have a HDD that is failing. :( (I could be very wrong but that's what it looks like to me)
[21:12] <chrisccoulson> Awsoonn, how come it only fails with the latest kernel? i can boot and use 3.1 without any problems
[21:13] <rtg_> chrisccoulson, start a bug and attach your apport info. I guess you'll have to use 3.1 to do it.
[21:13] <rtg_> what device is 03:00.0 ? Is that the display ?
[21:14]  * ogasawara lunch
[21:15] <ogasawara> chrisccoulson: bug 894070
[21:15] <ubot2> Launchpad bug 894070 in linux "IOMMU error loop early in boot" [High,Triaged] https://launchpad.net/bugs/894070
[21:16] <chrisccoulson> rtg_, 03:00.0 CardBus bridge: Ricoh Co Ltd Device e476 (rev 02)
[21:16] <chrisccoulson> ogasawara, thanks!
[21:16] <ogasawara> chrisccoulson: there's a test kernel there, or alternatively just try booting with "intel_iommu=off"
[21:16] <ogasawara> chrisccoulson: it's on my list of bugs to get to
[21:16] <chrisccoulson> excellent, thanks
[21:17] <rtg_> ogasawara, good eye. I knew I'd seen something like that
[21:17]  * ogasawara really goes to eat really quick
[21:29]  * rtg_ -> EOD
[22:30] <Awsoonn> I followed the instructions on https://wiki.ubuntu.com/Kernel/CrashdumpRecipe but my /var/crash dir is still empty, even after the sysrq test. Why might this be happening?
[22:59] <Awsoonn_> How can I get a crash dump or a stack trace if wiki:Kernel/CrashDumpRecipe leaves me with an empty /var/crash dir?
[23:32] <hggdh> should installation of linux-image-extra-virtual kick update-initramfs?