=== gavin__ is now known as gavinguo [06:45] moin === smb` is now known as smb [08:09] * apw yawns [08:09] yay ... thanks bip ... [08:09] apw, YW :) === fmasi_afk is now known as fmasi [08:56] https://launchpad.net/ubuntu/+source/linux has an entry for arm64 (well, kind of since it doesn't have the 'completed' tick) [09:05] ppisati: Yeahp. It's not likely to be completed this week either, but oh well. [09:08] brendand: What's the deal with bug #1224120? [09:08] brendand: You didn't tag it pass/fail. [09:10] infinity, apparently not - it must have got lost in the flurry of bug updating i was doing yesterday evening [09:12] brendand: Also, did 1223984 slip through the cracks? It's been confirmed for 10 days. [09:13] infinity, we started testing it at the same time as the others, it should be done shortly [10:07] i've a question about 'git clone --reference' hoping someone here knows the answer.. [10:08] so I've got the upstream tree cloned, and ubuntu trees cloned with --reference to the upstream tree [10:08] 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] or is --reference only used on the first pull [10:09] er, clone [10:09] smb: what's happened to VIRTIO_BLK? [10:10] ppisati, what do you mean? [10:10] smb: if i try to execute qemu -enable-kvm blablabla [10:10] Arm? [10:10] smb: and, instead of emulating a plain disk [10:10] smb: yep [10:11] smb: i use the '-device virtio-blk-device' [10:11] Well according to my knowledge virtio does pv of PCI devices... [10:11] smb: it complains about No 'virtio-bus' bus found for device 'virtio-blk-device' [10:11] not sure whether arm likes that [10:11] uhm [10:12] If you read my plumbers report there was discussions about extending this to platform devices :) [10:12] Ah maybe that was actually vio and I am confusing things [10:15] It was some pieces or apic interrupt deliviery for virtio at least iirc [10:15] ok, it's of [10:15] *off [10:15] well, not ok [10:15] but still, i found it [10:16] i wonder if it's off for every flavour, or it's just arm [10:16] It should be on at least for x86... [10:27] smb: http://paste.ubuntu.com/6162212/ === psivaa is now known as psivaa-afk [10:54] ppisati, so ... how risky is it to install a -generic kernel to panda running saucy ? [10:54] ppisati, it is running a server image iirc [10:57] apw: it's ok, it works [10:57] apw: i'm running S/generic on my panda [10:57] ppisati, so i can just install linux-generic and it should switch over ? [10:58] apw: but there's a problem with wifi on warm boot [10:58] apw: right [10:58] wifi? the board has wifi? [10:58] apw: lol :) [10:59] ppisati, so if i am not using the wifi it should just work ? [10:59] :) [10:59] apw: the *real* problem is that i'll spam your log with some annoying msgs [10:59] apw: actually it works after a cold boot (i mean the wifi) [10:59] apw: after a warm on, it doesn't [10:59] another drb fallout [10:59] *dtb [10:59] ppisati, so are you saying i shouldn't go, or will me whining at you help [11:00] apw: go [11:05] 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] ppisati, so people will be using that kernel more [11:07] apw: well, upstream is pretty much dead wrt omap*, after the dtb switch i was the only one to catch some issues [11:08] apw: wifi is one of those [11:08] apw: they check that it boots, but that's it [11:09] ppisati, ok ... so the lights are odd since the switch, both the leds hard on, is that normal [11:09] apw: yes, correct [11:09] oh i thought one of them was the 'disk light' for the sd card [11:34] 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] apw: But I don't think either of those fancy features ever made it to mainline. === fmasi is now known as fmasi_afk === psivaa-afk is now known as psivaa [12:15] smb: still no luck... [12:15] qemu-system-arm: -device virtio-blk-device,drive=foo: No 'virtio-bus' bus found for device 'virtio-blk-device' [12:16] hm === fmasi_afk is now known as fmasi [13:53] smb: ok, up&running [13:53] smb: how can we share the thing? [13:54] 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] ppisati, I think byobu might if you add my pub ssh keys to your login and we both call it (ssh-import...) [13:54] rtg, i think i have been seeing those before [13:55] rtg, though i am not seeing them on 64bit box [13:55] apw, yet I have lots of modules loaded, so it is clearly not failing. [13:55] smb: uhm [13:56] rtg it occurs i think when things try to load very very early before the builtin key is registered [13:56] it probabally does imply a bug somewhere, though i expect udev replay is fixing it up for you [13:57] apw, there are a bunch in the 12 second range [13:57] 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] rtg, nothing on my 32 bit box either ... [13:58] rtg, for me -9 works fine on both [13:58] tarvid, "integrity test failed" ? [13:58] apw, this one is UEFI with CSM disabled. I wonder... [13:58] Option on DVD install [13:59] rtg, my 64bit box is uefi as well, and i thought it had bios off, but .. i am unsure how to tell [13:59] tarvid, oh hmmm [13:59] tarvid, can you point me to the image you are using please [14:01] http://mirror.ox.ac.uk/sites/releases.ubuntu.com/releases//saucy/ubuntu-13.10-beta2-server-amd64.iso [14:03] chksum on the image is OK [14:05] burning the daily build [14:08] tarvid, i'll pull that one down and try an install from it [14:08] tarvid, what was your checksum on the .iso [14:08] (so i can check it hasn't changed) [14:09] tarvid@fairfax:~/Downloads$ md5sum ubuntu-13.10-beta2-server-amd64.iso [14:09] 4d869a82e8bc4e88de6379a0609fe598 ubuntu-13.10-beta2-server-amd64.iso [14:14] $ md5sum ubuntu-13.10-beta2-server-amd64.iso [14:14] 4d869a82e8bc4e88de6379a0609fe598 ubuntu-13.10-beta2-server-amd64.iso [14:15] yes Checking DVD of today's daily build [14:15] get the same error [14:16] tarvid ok, am firing up the same image right now in a VM to see if it is in the image [14:18] going ahead with the install [14:23] 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] (all typos mine0 [14:24] I'll try the alternate install, I suspect issues with the D2550 [14:35] 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] apw, tagging and uploading [14:47] 13.04 server amd64 halts at Detecting network hardware, looks like Ubuntu server on a D1550 is not in the cards [14:47] D2550 Cedarview [14:48] what make is it ? [14:51] J&W Minix [14:52] we definatly won't have one of those i don't suppose then [14:55] 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] rkrishna, during boot after the installation ? [15:00] sync [15:01] how the heck did my focus end up over here, unity you SUCK === fmasi is now known as fmasi_afk [15:36] apw: right, after installation and a reboot. [15:53] * smb -> EOW === fmasi_afk is now known as fmasi === cmagina is now known as cmagina-away === fmasi is now known as fmasi_afk [17:15] * apw wanders to where there are beverages [17:18] apw: Jealous. [17:19] infinity, is there new similar things where you are [17:19] apw: No, there are no beverages in Canada. We derive all our moisture from poutine. [17:19] infinity, are you near enough the border to slip across and get some ? [17:20] apw: If I cross the border, I end up in Montana. No one wants that. [17:20] * infinity glances at rtg. [17:20] infinity, there is at least one good tap room in montana [17:20] infinity, if only I _were_ in Montana. === cmagina-away is now known as cmagina [20:36] 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] 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] 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] 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] 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] backjlack, are you able to roll back to the previous kernel ? [23:10] bjf: Yes, that's how I got it to boot with the new one as well. [23:10] backjlack, there were very fiew changes to the 3.2 kernel. do you use zram ? [23:11] multiple attempts to boot the new one -> failure -> boot to .53 -> multiple reboots -> still working with the new one [23:11] bjf: No, this is an acer aspire one 756 with 16GB of RAM. [23:11] backjlack, xfs? [23:12] backjlack, 7 patches, 1 zram, 1 xfs, 1 cifs; 2 ARM and 2 x86 [23:12] backjlack, you are successfully running 3.2.0-53.81 ? [23:13] 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] backjlack, your original msg said you can't boot with -54 and now you say you are? [23:16] 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] backjlack, that's really strange [23:16] I'm not sure what the issue was, honestly. That's why I thought I should ask. [23:17] 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] 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] Unfortunately, I have to go now. I'll report back to let you know about the issue with the wlan/bluetooth.