/srv/irclogs.ubuntu.com/2011/11/10/#ubuntu-kernel.txt

jsalisburybjf, I'm pinging bdmurray and the landscape team now.00:04
jsalisburybjf, s/landscape/launchpad/ :-)00:05
bdmurrayabout what?00:05
jsalisburybdmurray, do you know whether the lp expiration bot is running? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/399911 looks like it should have expired a while ago.00:06
ubot2Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete]00:06
jsalisburybdmurray, from my understanding launcpad itself expires bugs, versus manual bots.00:06
jsalisburybdmuarry, s/manual bots/bots we create/00:06
bdmurrayjsalisbury: yes the launchpad janitor expires bug reports00:06
bdmurrayjsalisbury: I'd expect to see "This bug can expire in xyz days" on the page00:07
bdmurrayjsalisbury: for example in bug 846652 you can see this00:08
ubot2Launchpad bug 846652 in xserver-xorg-video-intel "Screen shifted right and incorrect refresh rate when switching VTs and unsuspending" [High,Incomplete] https://launchpad.net/bugs/84665200:08
jsalisburybdmurray, could there be a bug in the expiration janitor?  Does it only trigger off of an incomplete status00:08
bdmurrayjsalisbury: it must be incomplete and a not match a few other criteria00:08
jsalisburybdmurray, yeah, maybe the number of affected people has something to do with it?00:09
bdmurrayjsalisbury: that criteria is listed at https://help.launchpad.net/BugExpiry00:09
bdmurrayjsalisbury: no its not that I'm thinking / looking at it00:09
jsalisburybdmurray, thanks for the link, I'll take a look at that page.00:09
=== zz_bigbash is now known as bigbash
bdmurrayjsalisbury: I don't see anything my only thought is it might be because date_incomplete is so old00:10
jsalisburybdmurray, you think because it was set to incomplete back on 2009-12-10, and maybe the expiration logic was different then?00:12
bdmurrayjsalisbury: no that maybe the janitor only looks at date_incomplete within the past 90 days ... I'm grasping at straws though00:14
jsalisburybdmurray, I wonder what would happened if I marked the bug as confirmed then incomplete again?00:15
bdmurrayjsalisbury: there is a bug.isExpirable method that returns False00:15
bdmurraywell you'd have to wait 90 days for the actual expiration to happen00:15
jsalisburybdmurray, I also noticed the background for Incomplete in bug 399911 is a brighter yellow compared to incomplete say in bug 846652, not sure if that actually means anything00:16
ubot2Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete] https://launchpad.net/bugs/39991100:16
ubot2Launchpad bug 846652 in xserver-xorg-video-intel "Screen shifted right and incorrect refresh rate when switching VTs and unsuspending" [High,Incomplete] https://launchpad.net/bugs/84665200:16
bdmurrayjsalisbury: don't think so00:17
jsalisburybdmurray, do you have a script, or is that one in arsenal that you used to pull the bug.isExpirable method?00:18
jsalisburybdmurray, I guess I could just write a quick one.00:18
bdmurrayjsalisbury: I just used ipython to check on that bug00:19
jsalisburybdmurray, ahh, ok.  I wonder if it has anything to do with being assigned to someone, then reassigned to nobody.00:20
jsalisburybdmurray, bjf, I'll dig further and maybe see if someone on the launchpad team knows.00:21
bdmurrayoh, I've an idea now00:21
jsalisbury:-)00:21
bdmurrayjsalisbury: I'm pretty sure its because the status for 846652 is "Incomplete w/o response" and the status for 399911 is just "Incomplete"00:23
bdmurrayjsalisbury: and the API only tells you that they are Incomplete00:24
jsalisburybdmurray, I'm not sure I understand the "Incomplete w/o response", Are comments in the bug not responses?00:25
jsalisburybdmurray, or is it comments added after the bug was marked Incomplete?00:25
bdmurraythe latter00:26
jsalisburybdmurray, ahh, ok.  00:26
jsalisburybdmurray, and once a bug has a response after marked incomplete, it looks like it can't be forced to expire.  For bug 399911, I marked it confirmed, then incomplete again, and the message "This bug report will be marked for expiration in N" did not show up.00:28
ubot2Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete] https://launchpad.net/bugs/39991100:28
jsalisburybdmurray, oh wait, I also see that that bug has a duplicate!00:29
jsalisburybdmurray, but the Expiry page says that the bug must be a duplicate itself not to expire :-/00:30
bdmurrayjsalisbury: having a duplicate isn't a factor00:30
jsalisburyright00:30
=== bigbash is now known as zz_bigbash
martijnQuick question, forgive the newbie on this, I'm trying to get the ubuntu kernel to diagnose a USB driver issue I'm having, but I run into "fatal: The remote end hung up unexpectedly" when git clone'ing from kernel.ubuntu.com - is this something really obvious I should know about?01:17
martijn(cmd was: git clone git://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git lixsrc )01:18
martijn(now trying git clone http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-oneiric.git -- will post here when/if that fails, not aware of any firewall issues between me and the inet)01:18
martijn(USB issue in question is isochronous URB reception seems to not work from userland, my suspicion is a problem in drivers/usb/core/devio.c line 1347 processcompl() and I'd like to add some printk's there to diagnose.. but that requires the kernel.)01:27
=== mfisch is now known as Guest83317
=== ericm-Zzz is now known as ericm
bjfmartijn: there is something wrong with kernel.ubuntu.com right now01:43
martijnbjf: Thanks for the response! does the http request have any hope of succeeding or should I retry tomorrow?01:44
bjfmartijn: i think there is no hope right now01:45
martijnAssuming that statement is limited to kernel.ubuntu.com, I'll try again tomorrow - thanks for the info & good luck to who is working on fixing it.01:46
martijn(http also failed as expected, tomorrow!)01:59
T3CHKOMMIEhey guys. i need some help with a kernel project im doing. Im having the hardest time and ive spent well over 40 hours trying to figure this crap out. i feel like I am missing just a small piece of the puzzel.... can someone help me?02:07
T3CHKOMMIEmaybe someone can help me. i downloaded ubuntu kernel from source. did a make menuconfig and tweaked it how i liked. then did a make...02:17
T3CHKOMMIEim pretty sure that compiled the kernel. now im just trying to get it to an install CD so i can install it on my test machine. can anyone help me?02:17
T3CHKOMMIEhey guys, i still cant figure out how to "use" a kernel. i compiled one and cant figure out how to get it working. i tried using UCK and that was a miserable failure. has anyone compliled their own kernel?03:15
T3CHKOMMIEanyone?03:29
semitoneshello, valorie suggested I come here from #kubuntu to ask about my bug06:09
semitoneshttps://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/88841506:09
ubot2Launchpad bug 888415 in pulseaudio "Speakers do not mute when headphone jack is in use. Multimedia keys unmute speakers." [Undecided,New]06:09
semitonesshe said it ended up being a kernel problem for her06:09
semitoneslet me know if that sounds familiar -- I can idle here for a while :)06:12
=== ericm is now known as ericm-Zzz
=== ericm-Zzz is now known as ericm-afk
=== ericm-afk is now known as ericm
diwicbjf, if you're awake - I'm trying out your kernel scripts (the alsa cod), but when try to "make source", it fails with "file not found: source/debian/control". What is the correct way to fix this problem? I notice that there is no debian/control, but debian/control.stub.in, debian/control-scripts, and control.d/ 10:44
diwicall exists in the debian directory10:44
diwicaha, "fakeroot debian/rules debian/control" did the trick10:48
apwdiwic, likely you really wanted fakeroot debian/rules clean11:48
apwthat creates all the transient debian stuff11:48
diwicapw, aha, thanks11:48
apwelse you won't have a changelog later in the process11:48
apwsemitones, yep that is likely a kernel issue11:49
apwdiwic, do we have a good debugging guide for jack problems11:49
diwicapw, eh 11:50
diwicapw, could you specify "jack problems" a little11:50
apwdiwic, classic is "i insert headphones and speakers don't turn off"11:51
apwhttps://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/88841511:51
ubot2Launchpad bug 888415 in pulseaudio "Speakers do not mute when headphone jack is in use. Multimedia keys unmute speakers." [Undecided,New]11:51
apwis one we got asked about in scrollback last night11:51
diwicapw, only one of 84 open bugs for pulseaudio :-/11:51
apwheh yeah, i assume its more likely a kernel issue in this case right ?11:52
apwsemitones, is this machine reallly running maverick ?11:52
diwicapw, probably, but determing that is non-trivial11:52
apwdiwic, so pulse also takes a hand in jack handling ?11:53
diwicapw, hmm, since oneiric it does, but if this is maverick, it's definitely kernel11:53
apwoh ... thats news, i am unsure i want to know how pulse is involved ... yeeks11:54
apwdiwic, i'll shove it over to kernel anyhow, then it can be 1/6k bugs and even more lost11:54
diwictelling user to try https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS11:54
* apw tells them to test an oneiric liveCD11:56
diwicheh11:57
diwiceither should be just fine.11:57
apwdiwic, thanks11:57
apwman maverick seems like so long ago, and yet its only a year11:58
apwdiwic, i note that all of those dkms packages failed to build on i38612:01
diwicapw, fixed today, but yeah, maybe I should trigger a new build12:02
diwicapw, is this something to worry about: "package linux-alsa-driver-modules-oneiric-generic in control file but not in files list"12:02
apwits poor on our behalf but likely not an issue that stops you, thats an lbm package12:03
apwoh are you trying to start up auto builds of alsa for oneiric ?12:03
apwi suspect lbm doesn't have an alsa backport in it yet which would lead to that error12:04
apwit'd all be commented out, still in there but off12:04
diwicapw, yeah, I started off with bjf's tree for cod-natty and trying to make something launchpad based for oneiric12:08
diwicapw, as bjf's stuff is non-existent for oneiric and broken for the older12:08
apwdiwic, nice, so yeah it may well be we have no alsa in lbm if that is what you are using12:18
apwthough how would that differ from your dkms package ?12:18
apwif you used that against the crack of the day alsa tree ?12:18
diwicthey use the same source, the dkms package is for snd-hda-* modules only and is dkms based12:19
diwicif you need all modules (i e testing something different than HDA Intel cards you'll need the full sound tree12:19
apwahh yes, there is a lot more poo in there12:19
brendandsmb - sorry to bother you, but if i were to use 'skipabi' where would i put it?13:13
smbbrendand, depends a bit on what command you use to run the build I believe13:14
smbI use it rarely so it is easy to forget. Would skipabi=true dpkg-buildpackage -b ... work?13:15
brendandthe instructions i am using use debian/rules13:15
* smb thinks there both "skipabi=true debian/rules ..." and "debian/rules skipabi=true ..." may work13:16
smbbrendand, Seems right. You can use debian/rules printenv to check what settings get used13:19
brendandsmb - great, trying that now13:25
=== yofel_ is now known as yofel
=== zz_bigbash is now known as bigbash
=== bigbash is now known as zz_bigbash
=== zz_bigbash is now known as bigbash
=== chuck__ is now known as zul
=== BenC__ is now known as BenC
ogasawaraapw, tgardner: I'm trying to remember bits from UDS, wasn't there discussion about building in SATA_AHCI?14:45
tgardnerogasawara, yep, in fact that is what I set out to do, but got confused with xhci instated.14:46
apwogasawara, there was confusingly conversations about XHCI for usb3 and ahci as its the common sata.  they got conflated at times14:46
tgardnerinstead*14:46
apwogasawara, overall though i think we should move that one boot essential14:46
apwtgardner, indeed :)14:46
tgardnerogasawara, i did build in xhci in precise though. we'll need to make sure it doesn't break suspend14:47
ogasawaratgardner: ack14:47
* apw is just doing some of those annotations as it happens14:47
ogasawaraapw: I'll add it as a work item so we don't forget14:47
apwogasawara, cool thanks14:47
* tgardner pours gas into ubuntu-devel15:14
KiallHiya - I'm trying to figure out the cause of a kernel panic, anyone about to understand the logs? ;) http://dl.dropbox.com/u/1400487/panic/IMG_20111026_040053.jpg15:15
* ogasawara back in 2015:17
apwKiall, from the log that looks like a problem in a combination use of bridging and netfilter15:17
apwKiall, what release is this on as the kernel version is off the top on that dump15:17
apwsmb, didn't we have a problem in a stable update recently in this area ?15:18
apwtgardner, ^15:18
Kiallapw: Mine is running 3.0.0-13-server on oneiric15:18
smbapw, Nothing I know of...15:18
tgardnerKiall, you have bridging enabled with iptables rules ?15:19
Kialltgardner: yes15:20
tgardnerapw, IIRC it was netfilter and lxc that had issues15:20
KiallIts a server running OpenStack, So a combination of VLAN's, NF, Bridging and KVM (ie .. everything)15:20
tgardnerKiall, a VPN with tun/tap ?15:21
KiallNo - no VPN involved15:21
KiallI think the tap is KVM15:21
apwits the bridge for kvm then in this case15:21
tgardnerKiall, right. I haven't setup KVM in awhile15:21
tgardnerKiall, what net filters are you using ?15:22
apwKiall, was this the host or the VM that dumped15:23
Kiallapw: the host15:23
tgardnerapw, only yhte host can see the bridge15:23
apwtgardner, point15:23
Kialltgardner: DNAT, SNAT, and standard accept/deny rules..15:24
tgardnerKiall, nothing particularly dangerous there15:24
apwso this is a NAT bridge not a native one (that how virtmanager talks about it)15:24
apwso ... he is running a v3.0.6 base, so it'd be worth a scan of everything in stable after15:25
tgardnerKiall, is this a recent change in behavior ? and how often does it happen ?15:25
KiallI've seen it twice, and I've just found another person who's its just happened to..15:26
KiallObviously, Oneiric installs so they haven’t had very long lives yet15:26
apwcirtianly worth getting a bug filed with that on it, we are bound to see it plenty as well15:26
Kiallyea, will do15:29
apwif you can reproduce it i'd like to know if its there in -12, though i suspect it is15:31
* smb wonders wehter the 200+ patches pending on 3.0.y will help or do worse...15:32
KiallStandard traffic seems to trigger it, but I haven't figured out what traffic in particular :(15:32
apwsmb, yeah15:33
tgardnerogasawara, did 3.1 compat-wireless for Lucid stay on your list ?15:56
ogasawaratgardner: it did, was planning to get to it today or tomorrow.15:57
tgardnerogasawara, np, thanks15:57
smbWasn't tomorrow a holiday over there?15:57
apwogasawara, also do we have an alsa backport in oneiric yet ?15:57
ogasawarasmb: it is, but I'm planning to swap it for another day15:58
tgardnersmb, yep15:58
smbah ok15:58
ogasawaraapw: we don't15:59
apwi assume we should now/soon, i wonder if thats on -stable's radar15:59
ogasawaraapw: do we have a strong need for an updated alsa in oneiric?16:01
apwa good question indeed16:01
bjfapw, did we have a backported alsa for maverick or natty ?16:05
tgardnerI'm thinking we should only bother with backports to the current release and Lucid.16:06
tgardnerbackports being compat-wireless and possible alsa16:06
tgardnerpossibly*16:06
apwso current == oneiric right now ?16:07
apwbjf, another good question16:07
bjftgardner: my question was more along the lines of, "do we regularly backport alsa to N-1?"16:07
tgardneron the other hand, with the LTS kernels, does it make sense to backport anything to Lucid ?16:07
* apw was thinking the same as tgardner on lucid16:07
tgardnerapw, thats one more bit of maintenance that we could shed16:10
apwif we are doiing the work to support backports then they should be sufficient in theory16:11
apwi guess the only question is whether we get alsa/wireless backports sooner than the 'next' kernel16:11
apwas they are synced to upstream releases and not ours16:12
tgardnerapw, I'm sure I care about a 3 month gap16:12
tgardnerI'm *not* sure16:12
* apw has assumed sarcasm16:12
* ppisati bails for a bit16:13
* smb would be using alsa backports at least on his media pc... I could probably change to an LTS backports kernel. But assumes much whining about any support that gets dropped16:13
tgardnerapw, ogasawara: whats the story on powerpc flavours ? can we drop support for the old Apple G4 ?16:20
ogasawaratgardner: I think we were meant to chat with lifeless and jk about it16:21
apwtgardner, is that the 32bit non-smp job?  didn't jk do some work to confirm we didn't really need that16:21
apwogasawara, get a WI made perhaps then we won't forget16:21
ogasawaratgardner: bah, not lifeless, luke16:21
tgardnercan you guys run that ground ?16:22
apwogasawara, i am thinking we want to resurect our power blueprint so that cking's work is visible16:22
tgardnerthat to ground *16:22
apwogasawara, also i suspect we are going to have some work on boot speed which i suspect i'll want to make a new bleuprint to track; see any problems with me doing that16:22
ogasawaraapw: sounds fine16:23
ckingapw, that sounds like a good idea - needs to be trackable16:23
apwcking, have you done your WIs for your stuff yet ?16:23
ogasawaracking: let me see if I can find that blueprint16:23
apwogasawara, it was power-management or something16:23
ckingapw, nope, I'm draining my HWE worklist this week16:23
apwcking, ok16:23
ckingall 37 mins left of it16:23
apwcking, :)16:24
ckingnot that I'm counting ;-)16:24
apwrm HWE-TODO16:24
ckingoh yeah16:24
apwsleep 2160; rm HWE-TODO16:24
ogasawaracking: I couldn't find the existing one so I just made you a new blueprint.  I'll let you fill it in accordingly.  https://blueprints.launchpad.net/ubuntu/+spec/hardware-p-kernel-power-management16:40
cndbjf, do we still pull everything from upstream stable releases?16:49
cndI've got a patch that is working its way through stable for macbook trackpads16:49
tgardnercnd, yes16:50
bjfcnd, yes16:50
cndok, thanks16:50
bjfcnd, which release you hoping it gets into ?16:50
ckingogasawara, thanks16:50
cndbjf, it's in the review for the next one16:50
cnd3.0.9 I think?16:50
bjfcnd, ok, oneiric then, yes we will pick that up16:50
cndok16:51
bullgard4http://kernelnewbies.org/Linux_2_6_26: "2.6.26 adds support for ... BDI statistics and parameters exposure in /sys/class/bdi, ... Linux 2.6.24 merged per-device dirty thresholds: The limits that the kernel put to the amount of memory that a process can "dirty" changed from being global to be per-device. 2.6.26 exposes a interface in /sys/class/bdi that allow to set several parameters....17:06
bullgard4...There's another set of read-only parameters that are exposet in debugfs (debug/bdi/<bdi>/stats) " What does »BDI« stand for?17:06
tgardnerbullgard4, block device interface ?17:14
cndbullgard4, probably a debugger used for doing low level hardware bringup17:14
cndwait, nm, that doesn't make sense given the rest of the comment17:14
cndunless they are unrelated17:14
smbDocumentation/ABI/testing/sysfs.class-bdi: "Provide a place in sysfs for the backing_dev_info object." 17:27
bullgard4tgardner, cnd, smb: Thank you very much for your help. --  I will continue snooping. 17:31
broderhow frozen is the upstream kernel during the rc period? i have a patch i'd like to see get in (http://paste.ubuntu.com/734424/, based on https://lkml.org/lkml/2010/3/10/188), but i've never interacted with the lkml before and don't really know what i'm doing17:44
brodererr, http://paste.ubuntu.com/734429/ would be the one actually rebased onto master, but whatever17:46
tgardnerbroder, you'll likely need to run it past the list and the maintainer.17:55
tgardnerrtg@lochsa:~/proj/linux/linux-2.6$ scripts/get_maintainer.pl -f drivers/leds/led-class.c17:55
tgardnerRichard Purdie <rpurdie@rpsys.net> (maintainer:LED SUBSYSTEM)17:55
tgardnerlinux-kernel@vger.kernel.org (open list)17:55
broderso just send it off and hope for the best? :)17:56
tgardnerbroder, you should check with Samuel Thibault that it hasn't already been reviewed17:56
brodertgardner: ok, thanks for the pointers17:57
=== smb` is now known as smb
=== kamalmostafa is now known as kamal
* tgardner -> lunch18:52
tgardnerapw, ogasawara: can you remember any reason why CONFIG_MEMSTICK_R592 is not enabled in either Oneiric or Precise ?19:23
ogasawaratgardner: no idea19:23
apwtgardner, nothing jumps out at me, its not in any of our groups we check regularly19:24
tgardnerseems like it should have popped up in our config review19:24
apwit may be one we have on our list for review19:24
tgardnerapw, well, we clearly missed it in oneiric19:24
tgardnerbug #23820819:25
apwwe didn't have the same tooling in oneiric, but ogasawara lets add a wi to investifate it19:25
ubot2Launchpad bug 238208 in linux "Need MemoryStick driver Ricoh R5C592 (part of R5C832/822chipset)" [Wishlist,Confirmed] https://launchpad.net/bugs/23820819:25
ogasawaraapw: ack19:25
tgardnerapw, I'm just gonna write a patch to enable it.19:25
GrueMasterbjf: Erm, arm Lucid is EOL.  No need for Bug 888698 .19:29
ubot2Launchpad bug 888698 in linux-fsl-imx51 "linux-fsl-imx51: <version to be filled> -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/88869819:29
apw|| CONFIG_MEMSTICK_R592 || n || n || n || - || - || n || n || n || n || n || n ||  '''EXPERIMENTAL''' ||19:29
apwGrueMaster, until the buildd's are transitioned off on to panda we are stuck with supporting them19:29
GrueMastergrmbl.19:29
apwGrueMaster, they have _told_ me 'weeks', we shall see19:30
tgardnerapw, isn't that inconsistent with policy ?19:30
apwtgardner, its experimental and not special cased19:30
apwif the option is dependent on EXPERIMENTAL then our normal policy is to not enable it,19:31
tgardnerapw, oh, I thought we _were_ turning on experimental options if they were modules.19:31
tgardnerwe sure seem to have turned on a bunch so far19:31
apwwe have tended to if they are very definatly only going to pop up with hardware19:31
tgardnerwell, this one counts then19:32
apwyep, and it sounds like MEMSTICK_* is a class of exceptions19:32
apwtgardner, its a bit frightening if that option has been available since jaunty and still EXP19:33
tgardnerif it breaks, I'll let 'em keep both pieces19:34
apwyep19:35
apwi'm going through the annotations so i'll look see if there are any more patterns19:35
apwogasawara, as we'll nearly be on final kernel by rally, do we want to have a re-config review, as we already have new problems introduced by -rc2.  i'll be adding WIs for them shortly19:36
apw(at rally)19:36
ogasawaraapw: sounds like a good idea19:36
apwogasawara, added to the agenda19:37
ogasawaraapw: thanks19:37
bjfapw, have we reached out to upstream stable to see if they have any plans to support 3.2 ?19:38
bjfapw, also, have you heard anything about bugzilla.kernel.org coming back ?19:38
apwbjf, the only thing i've heard in that space is what jjohansen said about 'one per year' and i think that means we miss19:39
apwbjf, not heard a thing on bugzilla, though as people are only just getting back on at all i am not supprised19:40
jjohansenapw: I don't know that is really 1 per year, but that is the talk I heard19:40
* jjohansen can't remember where he heard it though19:41
* herton -> eod19:44
apwjjohansen, yeah, i was likely tipsy during that conv.20:04
tgardnerapw, do you have some kvm runes that work on precise ? testdrive seems to have stopped working for me20:08
kirklandtgardner: hmm, what's wrong with testdrive?20:08
tgardnerkirkland, can't find a display, -vga cirrus20:09
kirklandtgardner: hrmf?  how odd20:09
kirklandtgardner: you can edit that, fwiw20:09
kirklandtgardner: sudo vi /etc/testdriverc20:09
tgardnerRunning the Virtual Machine...20:10
tgardnerkvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0,boot=on -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus20:10
tgardnerCould not initialize SDL(No available video device) - exiting20:10
kirklandtgardner: find the line that says "-vga cirrus"20:10
kirklandtgardner: and change it20:10
kirklandhallyn: ^20:10
tgardnerto what?20:10
kirklandhallyn: what would be wrong with tgardner's kvm invocation?20:10
kirklandtgardner: you can try -vga std|vmware|cirrus20:10
tgardnerI also had to figure out the pxe-virtio.bin problem20:10
kirklandtgardner: honestly, though, we need to figure out why cirrus isn't working20:10
kirklandtgardner: sudo apt-get install kvm-pxe ?20:11
hallynkirkland, dunno "kvm -cdrom /iso/precise-mini-amd64.iso -boot d -vga cirrus" at least works for me20:12
hallyni do have ipxe installed of course20:12
tgardnerkirkland, lemme check if that fixes kvm-pxe20:12
tgardnerkirkland, kvm-pxe is already the newest version. the issue is that qemu wants pxe-virtio.rom, not pxe-virtio.bin20:13
kirklandhallyn: mind troubleshooting that for tgardner ?20:13
tgardnerkirkland, so hallyn's command works.20:15
tgardnereven over 'ssh -X'. I also tried testdrive on the physical console.20:15
hallyntgardner, can you remove 'boot=on' from your drive spec for hard drive in your command?20:16
tgardnerhallyn, on the war kvm command? or testdrive ?20:17
tgardnerraw*20:17
hallynkvm command20:17
hallynkvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0, -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus20:17
hallynuh, (sigh)20:17
hallynkvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0 -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus20:18
hallynthat20:18
hallyntgardner, is this on an oneiric host?20:18
tgardnerhallyn, precise host20:18
hallynok, i'm on oneiric host but with precise's kvm...20:18
tgardnerso I reran 'sudo testdrive -u file://`pwd`/precise-server-i386-daily.iso' to populate the COW image and now its working.20:19
tgardneretf ?20:19
tgardnerwtf?20:19
hallyntgardner, i'll blame it on the kernel :)20:20
tgardnerlemme go rerun this on the console.20:20
hallynoh, i hadn't seen some of the history20:21
hallyn'could not initialize SDL" - sounds like it may be an sdl lib problem then20:21
hallynor weird perms20:22
tgardnerhallyn, the console hates me, but I can run it over an 'ssh -X' session.20:23
hallyni can try to reproduce on my precise laptop.  you just ran 'testdrive' and chose precise-i386?20:23
tgardnerit paints a little slow, but its a server install so I don't really care20:23
tgardnerhallyn, yes20:24
tgardnerclean install from today20:24
hallynok, thanks. 20:24
tgardnerplus archive updates20:24
hallynI really do wish I could live my live without having to itneract with SDL20:24
kirklandsdl blows20:24
kirklandtgardner: thanks for the info;  when/if you ever find testdrive broken, poke hallyn and roaksoax20:25
kirklandtgardner: hallyn maintains the kvm pieces, roaksoax testdrive itself20:25
tgardnercan do20:25
kirklandtgardner: it's *supposed* to be working at all times;  if it ain't, we wanna get it fixed ;-)20:25
tgardnerkirkland, I was actually trying it out in order to verify that generic-pae still worked. next I'll try the same combo on a 64 bit host20:26
kirklandk20:26
tgardnerstill worked in kvm-qemu taht is20:26
hallyntgardner, oh, right, i saw that thread, was curious myself20:27
matthias_Hi there. I'd like to report a kernel problem, however the command "ubuntu-bug -p linux" does not do anything :)20:55
matthias_Should I manually file a report or is there another recommended way?20:57
tgardnermatthias_, thats a good start. would the nature of your kernel bug cause ubuntu-bug to stop working?20:57
matthias_No, I do not think so.20:58
matthias_My system is running. The problem is that I frequently see a bunch of annoying messages in my syslog. I wonder whether it is a hardware problem or a kernel problem.20:58
tgardnermatthias_, seems like it ought to work. what release ? oneiric ?20:59
matthias_11.10, fresh install20:59
tgardnermatthias_, other folks have been using it.21:00
matthias_The problem is: I bought a new Laptop (Thinkpad T520) and received it today. Ubuntu runs, however I see the following errors:21:00
matthias_kernel: [  781.456768] ata4: irq_stat 0x00000040, connection status changed21:00
matthias_kernel: [  781.456775] ata4: SError: { CommWake DevExch }21:00
matthias_kernel: [  781.456787] ata4: limiting SATA link speed to 1.5 Gbps21:01
matthias_kernel: [  781.456794] ata4: hard resetting link21:01
matthias_kernel: [  782.177920] ata4: SATA link down (SStatus 0 SControl 310)21:01
matthias_kernel: [  782.193880] ata4: EH complete21:01
tgardnermatthias_, one time, or repeating ?21:02
matthias_repeating frequently21:02
matthias_say every 20 seconds21:02
matthias_btw, thanks for your help!21:02
tgardneryou could try the 3.1 kernel: http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-3.1.0-2-generic_3.1.0-2.3_amd64.deb21:03
matthias_So if it was a hardware problem I'd return the laptop to the dealer. But somehow I guess that it is a kernel problem (since the system is running)21:03
tgardnerit might be power management messing with your link. 21:04
matthias_tgardner, software or hardware related?21:05
tgardnersoftware21:05
matthias_Would you think it is worth to report a bug?21:06
tgardnermatthias_, yep21:06
matthias_The interesting thing is that someone with another T520 reported a similar problem: http://comments.gmane.org/gmane.linux.kernel/120766121:07
matthias_tgardner, would you recommend me to file the bug manually or do you have an idea how to get the "ubuntu-bug" running?21:10
* ogasawara lunch21:10
tgardnermatthias_, manually21:10
matthias_thanks, and sorry for the many questions ;)21:11
matthias_ok, filed the bug (#888764)21:32
hallyntgardner, yeah i386 precise starts fine for me on just-upgraded precise21:37
hallyn(boy that was a slow iso sync)21:37
tgardnerhallyn, well, I'm installing a 64bit precise host, so I'll see if that is any different21:41
apwtgardner, i have a precise install but that was an oneiric-i386 which i think upgraded it to precise22:05
apw(in a KVM i mean)22:06
tgardnerapw, I've now a 64bit precise host installing a PAE server ISO22:06
apwahh, i see22:06
apwi guess i have an early enough kernel to have generic anyhow22:06
tgardnerapw, I believe this combo addresses cjwatson's concerns about qemu not working with PAE22:06
apwahh is 32 bit only really only 32bit not pae capable, interesting22:07
tgardnerapw, you've just bent my mind22:07
apwis 32bit kvm not actually pae22:08
tgardnerI was really only concerned that PAE work in all cases22:08
* tgardner is outta here22:10
ppisatihave we ever released a kernel for the n900?23:15
jjohansenppisati: nothing official that I know of23:32
ppisatiuhm23:34

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!