[01:06] <elops> Hello. can yo think of any thing bad about adding splassert(IPL_NONE) to pmap_enter() ?
[02:59] <palsa> Hello, I found a bug in the gma500_gfx module. How can I obtain the sources?
[03:16] <palsa> Never mind, sorry for the stupid question.
[09:19] <apw> ppisati, i have updated the summary-matrix with your latest upload: http://kernel.ubuntu.com/~kernel-ppa/configs/quantal/reviews/Portland.html
[09:21] <ppisati> apw: still a lot of sh*t to be synced, thanks
[09:22] <apw> ppisati, now you know my highbank pain
[09:22] <guest1337> if i update kernel 3.4.2+ my wireless card does not work anymore. uses ath9k driver. anyone knows what i can do?
[09:23] <apw> guest1337, does it report anything in dmesg when you use that level of kerenl, it may be needing newer firmware for instance
[09:23] <guest1337> wlan controller is not shown at all
[09:24] <apw> thats odd indeed, whats the pci ids for it, as ath9k still exists in later kernels
[09:26] <guest1337> 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
[09:27] <apw> if you use lspci -nnvv it will include some numbers for it (xxxx:yyyy) sort of thing
[09:28] <guest1337> 02:00.0 Network controller [0280]: Atheros Communications Inc. AR9485 Wireless Network Adapter [168c:0032] (rev 01)
[09:28] <guest1337> 	Subsystem: AzureWave Device [1a3b:2086]
[09:28] <guest1337> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
[09:28] <guest1337> 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
[09:28] <guest1337> 	Latency: 0, Cache Line Size: 64 bytes
[09:28] <guest1337> 	Interrupt: pin A routed to IRQ 17
[09:28] <guest1337> 	Region 0: Memory at dea00000 (64-bit, non-prefetchable) [size=512K]
[09:28] <guest1337> 	Expansion ROM at dea80000 [disabled] [size=64K]
[09:28] <guest1337> 	Capabilities: <access denied>
[09:28] <guest1337> 	Kernel driver in use: ath9k
[09:28] <guest1337> 	Kernel modules: ath9k
[09:29] <apw> guest1337, presumably thats from an
[09:29] <apw> guest1337, presumably thats from an older kernel
[09:29] <guest1337> yes thats a working kernel
[09:29] <apw> and where did you get your 3.4.x kernel
[09:30] <guest1337> you need the output of an non working kernel?
[09:30] <apw> not sure about that yet
[09:30] <guest1337> you only need that output? have to reboot
[09:31] <apw> i am wondering where the 3.4 kernel came from first
[09:31] <apw> so i can check the config
[09:31] <guest1337> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[09:31] <apw> which one specifiically
[09:31] <guest1337> 3.4.1 works
[09:31] <guest1337> 3.4.3 tested does not work
[09:31] <guest1337> and 3.4.4 also not working
[09:31] <guest1337> all 3.5.x also not working
[09:31] <guest1337> i did not test 3.4.2
[09:32] <apw> well that would be worth testing indeed to work out which jump is the issue
[09:32] <apw> why are you using 3.4 kernels?  any reason, or just for fun
[09:32] <guest1337> part fun
[09:32] <guest1337> other
[09:32] <guest1337> tochpad is correctly recorganized in 3.4.1
[09:33] <guest1337> if i use the stock one touchpad is show as mouse etc
[09:33] <apw> which touchpad out of interest
[09:34] <guest1337> Sentelic Touchpad
[09:34] <apw> sforshee, ^^ may be an interesting data point for you
[09:35] <guest1337> also scrolling is working with 3.4.1
[09:36] <apw> there is exactly one ath9k patch between those two versions, which is also present in v3.4.2, so if you could test that version that would help work out if it is that commit
[09:37] <apw> it sound somewhat unlikely
[09:37] <guest1337> ok brb 5min 
[09:41] <dupondje> BLKSSZGET should return new disk size when I resized a disk, and did a rescan ?
[09:41] <dupondje> Did: echo 1 > /sys/bus/scsi/devices/0\:0\:1\:0/rescan
[09:41] <dupondje> dmesg shows new size, but for example fdisk not (which uses BLKSSZGET)
[09:43] <apw> if dmesg shows the new size then the disk ought to have changed, is the overall size in the partition table too?
[09:44] <dupondje> [57013390.810115] sd 0:0:1:0: [sdb] 2147483648 512-byte hardware sectors (1099512 MB)
[09:44] <dupondje> and fdisk: Disk /dev/sdb: 536.8 GB, 536870912000 bytes
[09:49] <apw> hmmm you might strace fdisk and see what was returned there
[09:49] <apw> if i am reading the current code right it should be returnign the samem number
[09:54] <guest1337> here i am again
[09:54] <guest1337> srry took bit longer
[09:55] <guest1337> apw: 3.4.2 also not working
[09:56] <apw> guest1337, there does only seem to be one commit .1->.2 which could possibly affect ath9k
[09:56] <guest1337> another problem which i forgot
[09:56] <guest1337> whole usb ports do not work anymore
[09:56] <guest1337> on top of that
[09:56] <dupondje> apw: ioctl(3, BLKSSZGET, 0x7fffffffd31c)     = 0
[09:57] <dupondje> fdisk does a BLKSSZEGET, which seems to return wrong size
[09:57] <apw> that does seem broken, i assume this is a VM of some sort given you can change the size of the disk ?
[09:57] <dupondje> blockdev --getsz /dev/sdb also returns old value
[09:57] <dupondje> yep
[09:58] <dupondje> virtual machine, extended disk, rescanned disk
[09:58] <dupondje> but now I can't extend partition because of this
[10:00] <guest1337> apw: found a difference in lspci -nnvv : 	Interrupt: pin A routed to IRQ 17 (with working kernel) and 	Interrupt: pin A routed to IRQ 5 with non working. from network controller
[10:01] <apw> dupondje, presumably a reboot of the vm will resolve it
[10:01] <dupondje> apw: indeed, but thats what we want to avoid ofc :)
[10:01] <guest1337> ath9k driver and module is not loaded at all in non working
[10:03] <smb> dupondje, Sorry I just saw and still read this, I am not sure the scsi rescan attribute works the way ... have you tried to use 'blockdev --rereadpt'?
[10:03] <dupondje> BLKRRPART: Device or resource busy, its mounted ofc :(
[10:06] <apw> guest1337, ok not sure how any change in .1->.2 could cause that, but there is an ath init change so that seems suspicious as a first cut
[10:07] <apw> guest1337, will see about getting a build with that on top of .1 to see if that it, will take me a few
[10:07] <guest1337> ok
[10:08] <smb> dupondje, Yes, none of the device old partitions or the device itself should be opened by anything at that point. And sometimes its near impossible to find out what keeps it busy. :/
[10:09] <ohsix> fuser?
[10:12] <smb> More often not that it does in that case
[10:13] <smb> dupondje, Hm, what kind of virtual machine and how did you resize the disk? Just to get a bit more context
[10:32] <dupondje> smb: ESXi host
[10:32] <dupondje> resized in the vmwware interface
[10:35] <dupondje> its just annoying imo :) resize2fs can do live resizes
[10:35] <dupondje> vmware can do live resize of disk
[10:35] <dupondje> and then your stuck just with extending the partition :)
[10:38] <smb> dupondje, Well don't know much about the internals of vmware. But I guess they just change the disk itself. To some degree this has been noticed by the kernel, but whatever makes the rereadpt fail prevents the gendisk info to get updated.  And as long as that doesn't get done the rest fails too
[10:38] <smb> I assume rebooting is not an option otherwise you'd probably done it long ago...
[10:39] <dupondje> well its an option
[10:39] <smb> None of the partitions on that disk are currently mounted?
[10:39] <dupondje> as last resort :)
[10:40] <dupondje> Well they are mounted ...
[10:41] <dupondje> alot of services running on the disk, so reboot/unmount is last option
[10:41] <dupondje> But I guess its just not possible to resize without a reboot/umount
[10:43] <smb> At least not without unmounting. You would certainly not be happy if someone stole the chair you are sitting on, even if it gets replace by a bigger one...
[10:43] <dupondje> feature request ? :p
[10:43] <dupondje> guess it should be possible?
[10:45] <dupondje> disk can be live resized, new size is mostly seen by the kernel after a device rescan and filesystem can be live resized.
[10:45] <dupondje> so just missing the fdisk/partition part :)
[10:46] <apw> guest1337, http://people.canonical.com/~apw/mainline-3.4.2-debug-quantal/
[10:47] <smb> Well "just" the partition part has a potential to move around any mapping the kernel is using (while mounted). To allow that is not sane feature in my world...
[10:47] <guest1337> apw whats that?
[10:49] <apw> guest1337, a .2 with teh ath change reverted
[10:50] <dupondje> smb: you mean if you have like 2 partitions, and second partition gets deleted it would fuckup ? :)
[10:50] <guest1337> ok ill give it a tyr
[10:50] <guest1337> try
[10:54] <smb> dupondje, Certainly, I would. :-P 
[10:54] <guest1337> apw: restarting and testing
[10:56] <dupondje> smb: but still, there could be a check that it for example only resizes partitions, and never add/delete ? :)
[10:56] <smb> dupondje, Feel free to add that and get it accepted upstream. 3:)
[10:57] <dupondje> challenge ... oh wait :)
[11:04] <guest1337> re
[11:04] <guest1337> apw: not working.
[11:10] <Daviey> smb: hey, is http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=4b727361f0bc7ee7378298941066d8aa15023ffb;hp=e1ac50f64691de9a095ac5d73cb8ac73d3d17dba not applied to precise?
[11:13] <smb> Daviey, That points to a net staging tree. Should it? Certainly this normally would need to be upstream _and_ marked cc stable...
[11:14] <Daviey> smb: I'm just vaguely looking into.. bug 997978 .. which is a set of https://bugzilla.kernel.org/show_bug.cgi?id=42829
[11:14] <ubot2> Launchpad bug 997978 in qemu-kvm "KVM images lose connectivity with bridged network" [High,Confirmed] https://launchpad.net/bugs/997978
[11:14] <ubot2> bugzilla.kernel.org bug 42829 in kvm "KVM Guest with virtio network driver loses network connectivity" [Blocking,Resolved: code_fix]
[11:14] <smb> Daviey, But checking upstream, this was in Linus tree at 3.2 time...
[11:15] <smb> And it is in Precise
[11:16] <Daviey> smb: I thought it would have been applied, which is why i am confused
[11:16] <Daviey> smb: I guess that commit is unrelated to the Ubuntu bug?
[11:16] <smb> Daviey, Well it was in from the beginning
[11:16] <smb> That patch went upstream v3.2-rc1
[11:17] <Daviey> smb: So why no worky?
[11:18] <smb> Daviey, Some other problem? Why should I know? ;)
[11:19] <Daviey> smb: you smart guy.
[11:19] <smb> Daviey, Maybe, but not almighty. ;-P
[11:19] <smb> nor omnipresent
[11:20] <Daviey> smb: Oh, i see. I looked at you as an oracle for all things.
[11:20] <smb> Daviey, Where did you find the reference to that upstream commit? In that bug of ours of rh bugzilla?
[11:21] <Daviey> smb: community member correlated them on IRC.
[11:23] <smb> Daviey, Omm. I think I found it. Its in the upstream bug before the comment saying 11.10 (Oneiric) looks good...
[11:24] <Daviey> smb: Oh sorry, i thought you meant.. what linked the kernel.org bug to LP
[11:26] <smb> Daviey, No more in the sense how or why do we assume this would be the fix. It is a bit confusing in the upstream bug report. It say "I assume it got fixed" but nothing really definitve and the next comment probably only means with a certain argument...
[11:29] <smb> Daviey, I wonder. In our bug report, is there anything said about the host? I only see guest versions but may miss something
[11:31] <guest1337> apw: just tried quantal live build wit 3.5.0.2 and it works.. Oo
[11:31] <Daviey> smb: I only started looking at this briefly before i pinged out.. hallyn has been closer to it.
[11:33] <ogra_> wow, ogasawara made it into the german IT news
[11:33] <ogra_> http://www.golem.de/news/ubuntu-zweite-alpha-von-quantal-quetzal-erschienen-1206-92862.html
[11:35] <smb> Daviey, So guess it needs more reading. The change you asked for definitely is in. So whatever the issue is in PRecise it would be different. Or maybe something that has to be changed in a driver running in the host space...
[11:36] <guest1337> can someone watch up xserver-xorg-video-intel current version in 12.04 pls?
[11:37] <brendand> is there a particular package i need to install to get the quantal xorg packages on precise?
[11:37] <brendand> looking at dpkg -l i don't have them, despite that the ppa is enabled
[11:41] <Daviey> smb: okay, thanks muchly
[12:08] <[yates]> hi, where can i find a changelog of precise's linux-image-3.2.0-25-generic and linux-image-3.2.0-26-generic?
[12:18] <henrix> [yates]: in the package itself. take a look at /usr/share/doc/linux-image-3.2.0-25-generic/
[12:19] <[yates]> ahh yeh, nice, thanks :)
[13:29]  * apw looks for an archive admin to stroke a linux-lowlatency kernel in quantal
[13:36]  * apw tries to remember where the udev persistant naming db is
[13:36] <apw> and finds them in the first place he looks, yay
[13:36] <smb> apw, network devices?
[13:36] <apw> yeah, adding a 3rd nic to my firewall
[13:37] <smb> Now you can do a network packet 3-way merge...
[13:37] <apw> heh... 4 way as i have a tunnel too
[13:38] <arges> cking, hello
[13:39] <cking> arges, hiya
[13:39] <arges> cking, finally getting around to the jack_delay testing (its been a fun  week)
[13:39] <arges> cking, where did you get jack/jack.h headers from?
[13:39] <cking> arges, something like libjack*-dev - I can't recall of the top of my head
[13:40] <arges> ah there we are
[13:40] <arges> cking, thanks
[13:40] <cking> libjackdev2-dev I think
[13:40] <cking> nope, libjack-jackd2-dev
[13:41] <arges> libjack-jackd2-dev
[13:41] <arges> yea
[13:41] <arges> wrong version causes issue
[13:42] <cking> yep, it causes all kinds of woes
[13:48] <arges> cking, ahhhh. i have it playing back via headphones and monitors... whoops
[13:48] <cking> arges, its not the most helpful of test tools
[13:49] <arges> cking, i see no variance at all ... i can't even tell my terminal is scrolling anymore
[13:50] <cking> arges, yep, I only got variance when the buffer settings were very small
[13:50] <cking> ..and on a slow machine
[13:50] <cking> but if you load it with tools like "stress" you may see some jitter
[13:52] <arges> cking, ok i may run a stress/unstressed test
[13:52] <arges> as another variable
[13:52] <cking> arges, if you see my data, I had lots of variables :-/
[13:56] <arges> cking, do you have particular stress settings you used?
[13:56] <cking> arges, I ensured all the CPUs were loaded, and followed the defaults otherwise
[13:57] <cking>  arges, for my 2 CPU laptop, I used: stress --cpu 2 --io 4 --vm 2 --vm-bytes 128M 
[13:58] <arges>  stress --cpu `grep -c processor /proc/cpuinfo` --io 4 --vm 2 --vm-bytes 128M --timeout 60s
[14:00]  * cking nods
[14:00] <arges> cking, also are you testing on quantal or precise?
[14:01] <arges> i know the ll is quantal
[14:01] <cking> Q
[14:01] <arges> hmm
[14:01] <cking> and I compared the low-latency kernel Q against P, and they behaved the same
[14:06] <arges> cking, the maximum schedule delay... where di dyou find htis?
[14:08] <cking> arges, its on the qjacktql messages window - just near the XRUN count
[14:08] <cking> but only shows up if you get XRUNs
[14:08] <arges> cking, ah
[14:11] <arges> cking, lowest latency settings just crashed jackd 
[14:11] <arges> : )
[14:11] <cking> arges, yep, I get that too, it may work after a reboot, but it was really flakey
[14:12] <arges> cking, yea i wrote a 'kickSoundcard.sh' script that just removes all the firewire modules, kills jackd, kills pulse,  and reinserts and loads everything up again
[14:12] <arges> because this stuff happens fairly frequently
[14:13] <cking> basically it's fragile like eggshells
[14:13] <cking> arges, it took me forever to collect multiple sets of reliably looking data for different kernels, different loads, different buffer size configs
[14:15] <arges> cking, i still don't see max sched delay in the qjackctl window... is it somewhere else?
[14:16] <cking> arges, urm, I need to fire up the box that I tested this on just to re-remind myself, lemme dig it out of the pile
[14:17] <arges> cking, i see it
[14:17] <arges> cking, messages->status
[14:17] <cking> arges, that's the one
[14:19] <arges> cking, did you notice if the -ll kernel was anymore stable?
[14:20] <arges> w.r.t. to audio latency / jack not crashing
[14:20] <cking> arges, nope, both were flakey
[14:20] <arges> well its time to reboot my machine
[14:59]  * ogasawara back in 20
[15:05] <josepht> after rebooting a preinstall-server image on my panda, /proc/cmdline contains only 'ro quiet splash'
[15:16] <ppisati> brb
[15:18] <ogra_> josepht, quantal ? 
[15:18] <josepht> ogra_: yes
[15:18] <ogra_> thats normal
[15:18] <josepht> ogra_: okay, thanks
[15:19] <ogra_> in the new world order the boot config lives now in /usr/share/flash-kernel/bootscript/ in case you want to change it ... the root= stanza isnt necessary anymore, flash-kernel installs an initramfs hook that reads it from fstab now
[15:31] <cking> arges_, so what was your conclusion? anything of substance?
[15:31] <arges_> cking, getting data now, but had a call so getting back on task
[15:31] <cking> arges_, ah, no sweat :-)
[15:37] <arges_> cking, hmm i think this test is invalid because something called 'unity-music-daemon' started slamming my harddrive
[15:37] <cking> arges_, :-/
[15:41] <josepht> ogra_: I still need to run flash-kernel right?
[15:41] <ogra_> yep
[15:41] <ogra_> that hasnt changed
[16:05]  * ppisati goes to buy some food
[16:10] <arges_> cking, so really >= 32 frames I'm not getting XRUNs with jack_delay and one channel + stress test
[16:11] <arges_> anything else I should be adding to test perhaps 8 channels etC?
[16:11] <cking> arges_, well, it may be your CPU is just fast enough
[16:11] <arges_> cking, yea perhaps test on my other machine
[16:11] <arges_> but i'll add that data to the study so we have it
[16:12] <cking> we could set the max freq lower and re-test
[16:12] <arges_> cking, one thing is that the stress maxes the CPU
[16:12] <arges_> cking, but harddrive operations will cause xruns
[16:12] <cking> yep, well run the bonnie test and see if that causes xruns too
[17:18]  * henrix -> EOD
[17:30]  * cking --> EOD
[18:24]  * bjf -> lunch
[18:43] <cking> apw, I've just sent you the 32/32 32/64 64/64 combo results
[18:43] <cking> no big surprises
[18:43] <apw> cking, hey thanks, will look at the tommorrow when i am more with it
[18:44] <cking> whenever reallty
[18:44] <apw> cking, which side of 32/32 is 32/64 better or worse 
[18:44] <cking> it depends on what you're looking for :-)
[18:45] <apw> that means its better for soemthing :)  i shall look forward to reading
[18:45] <cking> lets chew it over on monday when I've not got the kids pestering me 
[18:45] <infinity> Performance-wise, I can't see how 32/64 would be any better than 32/32 (since the userspace is too stupid to know it has access to native atomics and other fun stuff), but the obvious benefit of having a 64-bit kernel on your 64-bit CPU seems worth it.
[18:47] <infinity> Assuming, of course, that your "32" is i386.  If the 32 is x32, that's a different can of worms, since you just bought yourself more registers and instructions and such.
[18:47] <mjg59> Or even if your 32 assumes the presence of sse
[18:47] <infinity> Which ours doesn't.
[18:47] <cking> like always, it's a mixed bag
[18:47] <infinity> Though, it has runtime selection here and there.
[18:49]  * cking -> REALLY EOD
[18:49] <infinity> s/D/W/
[18:50] <apw> infinity, well bear in mind that your system calls we in 64bit so it could easily be faster for some operations, and hotter, and eat more battery
[18:50] <apw> *will be in
[18:51]  * apw calls it a wrap too, i smell some lovely spagbol in my future
[18:52] <infinity> You people and your living in the future.
[18:52] <apw> its better than the now in most cases ...
[18:53] <infinity> Is this why Australians always seem so unjustifiably happy?
[22:09] <palsa> Anyone still awake?