[06:45] <ppisati> moin
[08:09]  * apw yawns
[08:09] <apw> yay ... thanks bip ...
[08:09] <smb> apw, YW :)
[08:56] <ppisati> https://launchpad.net/ubuntu/+source/linux has an entry for arm64 (well, kind of since it doesn't have the 'completed' tick)
[09:05] <infinity> ppisati: Yeahp.  It's not likely to be completed this week either, but oh well.
[09:08] <infinity> brendand: What's the deal with bug #1224120?
[09:08] <infinity> brendand: You didn't tag it pass/fail.
[09:10] <brendand> infinity, apparently not - it must have got lost in the flurry of bug updating i was doing yesterday evening
[09:12] <infinity> brendand: Also, did 1223984 slip through the cracks?  It's been confirmed for 10 days.
[09:13] <brendand> infinity, we started testing it at the same time as the others, it should be done shortly
[10:07] <tjaalton> i've a question about 'git clone --reference' hoping someone here knows the answer..
[10:08] <tjaalton> so I've got the upstream tree cloned, and ubuntu trees cloned with --reference to the upstream tree
[10:08] <tjaalton> now if I have extra remotes on the upstream tree (like, stable etc), and add those to the ubuntu tree, are they also using the referenced tree or not?
[10:09] <tjaalton> or is --reference only used on the first pull
[10:09] <tjaalton> er, clone
[10:09] <ppisati> smb: what's happened to VIRTIO_BLK?
[10:10] <smb> ppisati, what do you mean?
[10:10] <ppisati> smb: if i try to execute qemu -enable-kvm blablabla
[10:10] <smb> Arm?
[10:10] <ppisati> smb: and, instead of emulating a plain disk
[10:10] <ppisati> smb: yep
[10:11] <ppisati> smb: i use the '-device virtio-blk-device'
[10:11] <smb> Well according to my knowledge virtio does pv of PCI devices...
[10:11] <ppisati> smb: it complains about No 'virtio-bus' bus found for device 'virtio-blk-device'
[10:11] <smb> not sure whether arm likes that
[10:11] <ppisati> uhm
[10:12] <smb> If you read my plumbers report there was discussions about extending this to platform devices :)
[10:12] <smb> Ah maybe that was actually vio and I am confusing things
[10:15] <smb> It was some pieces or apic interrupt deliviery for virtio at least iirc
[10:15] <ppisati> ok, it's of
[10:15] <ppisati> *off
[10:15] <ppisati> well, not ok
[10:15] <ppisati> but still, i found it
[10:16] <ppisati> i wonder if it's off for every flavour, or it's just arm
[10:16] <smb> It should be on at least for x86...
[10:27] <ppisati> smb: http://paste.ubuntu.com/6162212/
[10:54] <apw> ppisati, so ... how risky is it to install a -generic kernel to panda running saucy ?
[10:54] <apw> ppisati, it is running a server image iirc
[10:57] <ppisati> apw: it's ok, it works
[10:57] <ppisati> apw: i'm running S/generic on my panda
[10:57] <apw> ppisati, so i can just install linux-generic and it should switch over ?
[10:58] <ppisati> apw: but there's a problem with wifi on warm boot
[10:58] <ppisati> apw: right
[10:58] <apw> wifi? the board has wifi?
[10:58] <ppisati> apw: lol :)
[10:59] <apw> ppisati, so if i am not using the wifi it should just work ?
[10:59] <apw> :)
[10:59] <ppisati> apw: the *real* problem is that i'll spam your log with some annoying msgs
[10:59] <ppisati> apw: actually it works after a cold boot (i mean the wifi)
[10:59] <ppisati> apw: after a warm on, it doesn't
[10:59] <ppisati> another drb fallout
[10:59] <ppisati> *dtb
[10:59] <apw> ppisati, so are you saying i shouldn't go, or will me whining at you help
[11:00] <ppisati> apw: go
[11:05] <apw> ppisati, are we working on the wifi issue, as you know that 90% likely we are scrapping -omap4 for those boards in saucy
[11:05] <apw> ppisati, so people will be using that kernel more
[11:07] <ppisati> apw: well, upstream is pretty much dead wrt omap*, after the dtb switch i was the only one to catch some issues
[11:08] <ppisati> apw: wifi is one of those
[11:08] <ppisati> apw: they check that it boots, but that's it
[11:09] <apw> ppisati, ok ... so the lights are odd since the switch, both the leds hard on, is that normal
[11:09] <ppisati> apw: yes, correct
[11:09] <apw> oh i thought one of them was the 'disk light' for the sd card
[11:34] <infinity> apw: In the TI kernel, one was an access light for the SD, the other was a heartbeat (that even changed pulse speed with load, if I recall, very fancy).
[11:34] <infinity> apw: But I don't think either of those fancy features ever made it to mainline.
[12:15] <ppisati> smb: still no luck...
[12:15] <ppisati> qemu-system-arm: -device virtio-blk-device,drive=foo: No 'virtio-bus' bus found for device 'virtio-blk-device'
[12:16] <smb> hm
[13:53] <ppisati> smb: ok, up&running
[13:53] <ppisati> smb: how can we share the thing?
[13:54] <rtg> apw, hmm, I've some new dmesgs (I think) in 3.11.2: Request for unknown module key 'Magrathea: Glacier signing key: 8a252c84f3b9b2da535eae5c388d144dc7a3e0d4' err -11
[13:54] <smb> ppisati,  I think byobu might if you add my pub ssh keys  to your login and we both call it (ssh-import...)
[13:54] <apw> rtg, i think i have been seeing those before
[13:55] <apw> rtg, though i am not seeing them on 64bit box
[13:55] <rtg> apw, yet I have lots of modules loaded, so it is clearly not failing.
[13:55] <ppisati> smb: uhm
[13:56] <apw> rtg it occurs i think when things try to load very very early before the builtin key is registered
[13:56] <apw> it probabally does imply a bug somewhere, though i expect udev replay is fixing it up for you
[13:57] <rtg> apw, there are a bunch in the 12 second range
[13:57] <tarvid> Getting Integrity test failed on a D2550 on linux-image-extra-3.11.0-8-generic_3.11.0-8.15.amd64.deb
[13:57] <apw> rtg, nothing on my 32 bit box either ...
[13:58] <apw> rtg, for me -9 works fine on both
[13:58] <apw> tarvid, "integrity test failed" ?
[13:58] <rtg> apw, this one is UEFI with CSM disabled. I wonder...
[13:58] <tarvid> Option on DVD install
[13:59] <apw> rtg, my 64bit box is uefi as well, and i thought it had bios off, but .. i am unsure how to tell
[13:59] <apw> tarvid, oh hmmm
[13:59] <apw> tarvid, can you point me to the image you are using please
[14:01] <tarvid> http://mirror.ox.ac.uk/sites/releases.ubuntu.com/releases//saucy/ubuntu-13.10-beta2-server-amd64.iso
[14:03] <tarvid> chksum on the image is OK
[14:05] <tarvid> burning the daily build
[14:08] <apw> tarvid, i'll pull that one down and try an install from it 
[14:08] <apw> tarvid, what was your checksum on the .iso
[14:08] <apw> (so i can check it hasn't changed)
[14:09] <tarvid> tarvid@fairfax:~/Downloads$ md5sum ubuntu-13.10-beta2-server-amd64.iso 
[14:09] <tarvid> 4d869a82e8bc4e88de6379a0609fe598  ubuntu-13.10-beta2-server-amd64.iso
[14:14] <apw> $ md5sum ubuntu-13.10-beta2-server-amd64.iso
[14:14] <apw> 4d869a82e8bc4e88de6379a0609fe598  ubuntu-13.10-beta2-server-amd64.iso
[14:15] <tarvid> yes Checking DVD of today's daily build
[14:15] <tarvid> get the same error
[14:16] <apw> tarvid ok, am firing up the same image right now in a VM to see if it is in the image
[14:18] <tarvid> going ahead with the install
[14:23] <apw> tarvid, ok ... from that image above using the 'test ISO' option i get a "The CD-ROM intefrity test wsa successful.  The CD-ROM is valid." here
[14:23] <apw> (all typos mine0
[14:24] <tarvid> I'll try the alternate install, I suspect issues with the D2550
[14:35] <rkrishna> Hi all, I am trying to install a video card, and I see this "BUG: unable to handle kernel paging request at 00000000117d4300" error in the kernel.log. Any Ideas?
[14:39] <rtg> apw, tagging and uploading
[14:47] <tarvid> 13.04 server amd64 halts at Detecting network hardware, looks like Ubuntu server on a D1550 is not in the cards
[14:47] <tarvid> D2550 Cedarview
[14:48] <apw> what make is it ?
[14:51] <tarvid> J&W Minix
[14:52] <apw> we definatly won't have one of those i don't suppose then
[14:55] <rkrishna> Hi all, I am trying to install a video card, and I see this "BUG: unable to handle kernel paging request at 00000000117d4300" error in the kernel.log. Any Ideas?
[14:57] <apw> rkrishna, during boot after the installation ?
[15:00] <apw> sync
[15:01] <apw> how the heck did my focus end up over here, unity you SUCK
[15:36] <rkrishna> apw: right, after installation and a reboot.
[15:53]  * smb -> EOW
[17:15]  * apw wanders to where there are beverages
[17:18] <infinity> apw: Jealous.
[17:19] <apw> infinity, is there new similar things where you are
[17:19] <infinity> apw: No, there are no beverages in Canada.  We derive all our moisture from poutine.
[17:19] <apw> infinity, are you near enough the border to slip across and get some ?
[17:20] <infinity> apw: If I cross the border, I end up in Montana.  No one wants that.
[17:20]  * infinity glances at rtg.
[17:20] <apw> infinity, there is at least one good tap room in montana
[17:20] <rtg> infinity, if only I _were_ in Montana.
[20:36] <backjlack> Did something change from kernel 3.2.0-53-generic to 3.2.0-54-generic amd64? My machine doesn't boot any more with it - as in it seems to not be able to start X.
[20:37] <backjlack> 3.8 from raring-lts seems to reset the state of my wlan/bluetooth to all enabled after rebooting / waking from sleep.
[21:05]  * rtg -> EOW
[21:30] <backjlack> It looks like the issue with wifi+bluetooth being activated all the time and their state being ignored is present in the mainline kernel as well. A 3.10 kernel built from sources has the exact same problem.
[21:48] <eLpm> Hello. After the latest saucy update, I receive this error on startup: Sep 27 17:40:57 pc4 kernel: [   42.380067] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 2, found 0)
[21:51] <eLpm> Don't know if this is the right channel (ubuntu-devel, maybe?) to ask this. (BTW, Ubuntu logs perfectly, so I am not sure about the severity)
[23:08] <bjf> backjlack, are you able to roll back to the previous kernel ?
[23:10] <backjlack> bjf: Yes, that's how I got it to boot with the new one as well.
[23:10] <bjf> backjlack, there were very fiew changes to the 3.2 kernel. do you use zram ?
[23:11] <backjlack> multiple attempts to boot the new one -> failure -> boot to .53 -> multiple reboots -> still working with the new one
[23:11] <backjlack> bjf: No, this is an acer aspire one 756 with 16GB of RAM.
[23:11] <bjf> backjlack, xfs?
[23:12] <bjf> backjlack, 7 patches, 1 zram, 1 xfs, 1 cifs; 2 ARM and 2 x86 
[23:12] <bjf> backjlack, you are successfully running 3.2.0-53.81 ?
[23:13] <backjlack> bjf: I am now running -54 after booting -53 just once. I am not using xfs, cifs, btrfs, zfs or anything else other than vanilla ext4.
[23:14] <bjf> backjlack, your original msg said you can't boot with -54 and now you say you are?
[23:16] <backjlack> bjf: I forgot to get back to the channel and mention that. It was just a set of about 5 boots. I was able to boot -54 after booting -53 manually just once.
[23:16] <bjf> backjlack, that's really strange
[23:16] <backjlack> I'm not sure what the issue was, honestly. That's why I thought I should ask.
[23:17] <bjf> backjlack, none of those 7 changes *should* cause any issues but you can't be 100% certian. i think only 2 of them could possibly affect you
[23:20] <backjlack> bjf: Thank you for helping me out with this. I'll try 3.5 next to find out if the issue with wlan/wifi ignoring state is still there. Maybe I can track down the exact kernel version which broke this.
[23:21] <backjlack> Unfortunately, I have to go now. I'll report back to let you know about the issue with the wlan/bluetooth.