[00:17] <crimsun> sigh, cs46xx hardware is largely broken :(
[00:18] <crimsun> I suppose we can reprobe the register until it appears to return valid data
[00:37] <bladernr_> anyone around who can answer a question about filing a bug ?
[00:45] <bryceh> bladernr_, don't ask if you can ask.  bad irc etiquette
[00:45] <bryceh> better to just ask your question straight off, then people can answer or ignore as appropriate ;-)
[00:46] <bryceh> bladernr_, also you probably should ask on #ubuntu or #ubuntu+1, as this is more a developer-oriented channel
[00:52] <bladernr_> bryceh:  sorry... was talking in other channels too ... I know better :/
[04:23] <slackguru> Hey! Is there a working PPA?
[04:24] <slackguru> 2.6.31-20-generic-pae is killing me.
[04:24] <slackguru> Slowest kernel I've seen in a long time.
[04:24] <slackguru> Memory consumption is off the charts and I am actually swapping...
[04:26] <slackguru> If not, I am going to give a little script I wrote a try to see if I can successfully make synaptic think kernel.org and its change log is a valid ppa
[05:35] <slackguru> Out of 93 people nobody is awake?
[05:45]  * hyperair compiles his own kernels
[05:46] <hyperair> isn't PAE supposed to have some pretty bad performance, though?
[05:55] <jjohansen> well it depends on what you are doing
[05:55] <jjohansen> PAE does have a penalty
[05:56] <jjohansen> memory consumption off the charts just seems wrong though
[06:04] <slackguru> Well, I am building a 2.6.33 right now on the laptop that crashed and see if its any better, but my ubuntu box, I want to stay with something known not to mess with the tool chain, I am building my own tool chain and all on the crashed laptop
[06:06] <slackguru> I don't want to have to do that for my main box and frankly I don't even know how pae got on here, I only have 512MB of ran and I didn't go looking for pae so it should be the vanilla generic kernel, but it is not
[06:06] <slackguru> The only added repositories I have in my source.list is for the ubuntu debugging symbols.
[06:07] <jk-> slackguru:  https://launchpad.net/~kernel-ppa/+archive/ppa has builds of mainline kernels
[06:07] <jk-> and you should be able to just install the linux-image-*-generic to replace the pae one
[06:08] <slackguru> Number of packages:
[06:08] <slackguru>     0 source packages (0 bytes)
[06:08] <slackguru>     0 binary packages (0 bytes)
[06:08] <slackguru> Repository size:
[06:08] <slackguru>     0 bytes (0.00%) of 8.0 GiB
[06:08] <jk-> i'd try the generic before installing a mainline one from that PPA.
[06:09] <slackguru> that repo is dry
[06:09] <jk-> yeah, odd
[06:09] <slackguru> nothing there.
[06:09] <jk-> anyhow, try -generic
[06:09] <slackguru> I am actually thinking of switching to -rt
[06:09] <jk-> and if that doesn't work, file a bug
[06:10] <jk-> -rt that may improve latency, but not performance
[06:10] <jk-> http://kernel.ubuntu.com/~kernel-ppa/mainline/ for the builds
[06:10] <jk-> but still, try -generic first.
[06:11] <slackguru> thanks jk- 
[06:12] <jk-> np
[06:12] <slackguru> I am actually looking for a ppa that has stable development releases, kernel.org has 2.6.33 and ubuntu has only caught up to 2.6.32
[06:13] <jk-> you're probably best off using the default kernel, it's had the most testing with the ubuntu userspace.
[06:13] <slackguru> with 2.6.31-20 I feel like I am the testing ground
[06:14] <slackguru> let me know if their is a daily ppa if you hear anything.
[06:15] <slackguru> thanks
[06:17] <RAOF> There is an upstream kernel build, but it's not a great idea to switch kernels.
[06:18] <RAOF> There's a lot of GPU work going on in the kernels, and you'll hit a poorly-tested version combination quite quickly with different kernel versions.
[09:28] <psurbhi> hie! i am looking at bug 537465
[09:28] <ubot3> Malone bug 537465 in ttf-sazanami "package ttf-sazanami-mincho 20040629-2ubuntu2 failed to install/upgrade:  (dup-of: 533609)" [Undecided,Incomplete] https://launchpad.net/bugs/537465
[09:28] <ubot3> Malone bug 533609 in mono "package mono-runtime 2.0.1-4ubuntu0.1 failed to install/upgrade: " [Undecided,Incomplete] https://launchpad.net/bugs/533609
[09:28] <psurbhi> and in the lspci output attached by apport
[09:28] <psurbhi> i cannot seem to see any driver module against the VGA compatible controller
[09:28] <psurbhi> any guesses why this might be happening?
[09:31] <psurbhi> will this be an in kernel compiled driver?
[09:32] <ogra> amitk, psurbhi, http://paste.ubuntu.com/397697/ has the first two panics i get with the omap kernel
[09:32] <amitk> ogra: dmesg?
[09:33] <smb> psurbhi, the lspci -vvvnn output would list a driver attached to the device even if it is build-in
[09:33] <ogra> amitk, the board hangs hard, no way to get to dmesg at that point
[09:34] <psurbhi> ogra, any snap possible?
[09:34] <ogra> amitk, but i assume you should see the same on your board if you have other ways to get data
[10:26] <cking> apw, have you delved into acpi debugging your dell after s/r w.r.t the temp sensor issue?
[10:40] <apw> cking, nope not had a second to look at it other than to be annoyed by it
[10:40] <apw> you can teach me when i get back
[11:48] <pmatulis> a netxen (10 Gb) network adapter (NC522SFP) is not having it's module (netxen_nic) loaded automatically on hardy.  what to do?
[12:00]  * cking appreciates apw's daily kernel builds - makes bisecting so much easier
[12:02] <apw> cking, cool
[12:03] <tgardner> apw, at least smb will have something to do whilst we're gone. I see a bunch more .32 stable updates in the pipe
[12:03] <apw> tgardner, yeah wouldn't want him to be bored now would we
[12:49] <smb> and for extended self flagellation he even tries to add to them
[12:51] <tgardner> smb, IIRC there was an igb patch you can skip
[12:52] <smb> tgardner, I think I saw some drop thing. But I usually check with whats really in the queue anyway
[12:52] <smb> tgardner, Btw, have we been having problems with tg3 based cards?
[12:53] <tgardner> smb, nothing thats attracted my attention
[12:54] <smb> Ok, might just be my imagination by half seeing things passing by
[12:56] <tgardner> smb, the tigon driver is quite popular, and generally stable
[12:56] <smb> Just because that is in the queue "tg3: Fix 5906 transmit hangs"
[12:57] <smb> and another on on that
[12:57] <smb> tg3: Fix tg3_poll_controller() passing wrong pointer to tg3_interrupt()
[12:57] <tgardner> smb,  perhaps its a rare circumstance
[12:58] <smb> Quite possible. Usually the commit message does not say how high the probability of an issue is
[13:30] <psurbhi> hey, does anyone know what the bcdDeviceMin, bcdDeviceMax parameters in the UNUSUAL_DEV macro in drivers/usb/storage/usb.c signify?
[13:30] <smb> psurbhi, IIRC those were version numbers
[13:31] <psurbhi> ok, so how do you aquire those?
[13:31] <smb> Like device version/firmware version x to y
[13:31] <smb> lsusb -v
[13:31] <psurbhi> aah, ok :) thanks
[13:32] <smb> psurbhi, Of course you only get one number for the device and version you actually have
[13:32]  * psurbhi checks
[13:32] <smb> psurbhi, so the limits usually grow over time or were gathered by asking around
[13:33] <psurbhi> so then is it safe to put the min as 0x0000 and max as 0xffff?
[13:33] <psurbhi> as i see for other entries?
[13:34] <smb> psurbhi, Only if you assume all are broken. So not safe
[13:34] <psurbhi> ok..
[13:34] <smb> The safe approach is only to use the one you have (or a range if you have that)
[13:34] <psurbhi> so then safer is to be specific and put it for the specific version that lsusb gives
[13:34] <smb> right
[13:34] <psurbhi> smb, ack! thanks
[13:35] <smb> psurbhi, btw its the bcdDevice entry
[13:35] <psurbhi> smb, thanks a lot! just when i was searching :)
[13:35] <smb> And I believe it was a bcd encoding used for the integer
[13:36] <smb> so a bcdDevice = 6.01 woule be 0x0601, but better check that
[13:36] <psurbhi> which is why the name has a bcd om ot
[13:36] <psurbhi> ok..
[13:37] <psurbhi> s/om ot/in it
[13:37] <smb> psurbhi, Yeah, actually true :)
[13:40] <psurbhi> smb, i have the hal output.. and am hoping the lshal entry "revision_bcd" is the same
[13:41] <smb> psurbhi, You could check with a usb device you got?
[13:42] <psurbhi> yeah
[13:46] <psurbhi> got that :) thanks smb!
[13:46] <smb> np :)
[15:17] <KB1JWQ> Found a bug that affects me that I'd like to pitch in on.  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/532374 -- comment 21 and 22 shows where we're stalled, and I suspect it's something I can overcome with a bit of guidance.
[15:17] <ubot3> Malone bug 532374 in linux "[Lenovo 2537AD3, 2537AB8] one successful suspend/resume per boot" [Undecided,Confirmed] 
[15:17] <KB1JWQ> ubot3: You just scared the crap out of me.  Don't do that. :-)
[15:17] <ubot3> KB1JWQ: Error: I am only a bot, please don't think I'm intelligent :)
[15:19] <KB1JWQ> Specifically, the question becomes "how do I compile a kernel 'The Ubuntu way' with ACPI_PROCESSOR as a module.
[15:24] <KB1JWQ> The docs for kernel recompilation on Karmic seem a bit outdated for Lucid; is there a pointer to fresher documentation on this than https://help.ubuntu.com/community/Kernel/Compile ?
[15:25] <tgardner> KB1JWQ, https://wiki.ubuntu.com/KernelTeam/KernelMaintenance
[15:29] <slackguru> RAOF, how can I find it? I wouldn't be asking if I didn't understand what I was getting myself into.
[15:30] <KB1JWQ> tgardner: Thanks!
[16:03] <alexmoldovan> Hello everybody, I'm currently an intern @ Canonical's office in Montreal and I have some questions about the kernel's ACPI management.I want to be able to wake up the computer after a period of time, and I use the following script to do it: http://pastebin.ubuntu.com/397848/, with pm-hibernate of poweroff on the last line. We have over 60 laptops in the lab and I've tested most of them. Last week, a machine, woke up just from  poweroff stat
[16:03] <alexmoldovan> e and not from pm-hibernate. This week, it wakes up from both states. It happens alos with several others machines. My question is  Were there some changes in the kernel in the last week that are related to this issue? If yes, please point me into the right direction to further investigate. Thanks!
[16:09] <smb> alexmoldovan, It might help to say which kernel (series) you are using. Lucid?
[16:10] <alexmoldovan> yes
[16:10] <alexmoldovan> I'm testing lucid in the lab
[16:10] <johanbr> alexmoldovan, kernel freeze was March 11, so if your results have changed since then, it's related to userspace changes
[16:10] <BenC> alexmoldovan: IIRC, the wakeup is mostly hardware induced (IOW, no kernel changes affect whether it wakes up or not)
[16:11] <BenC> it's a case of the ACPI alarm working or not (if it's software related, then it's a case of access to the ACPI alarm, not so much kernel really)
[16:12] <BenC> alexmoldovan: if it's a case of the kernel not working on wakup, then it's unrelated to the alarm itself, and just a suspend/resume issue
[16:12] <BenC> alexmoldovan: do your tests show that a forced wakeup works, and just that the alarm isn't waking the system up?
[16:13] <alexmoldovan> the wake from the power button works fine
[16:13] <alexmoldovan> but not with the alarm
[16:14] <BenC> Ok, then it sounds like that the ACPI alarm just isn't triggering, which is usually a bug in BIOS more times than userspace/kernel
[16:14] <smb> The power button is a different source for wakeup.
[16:14] <BenC> alexmoldovan: do these systems have a BIOS setting where you can set the alarm in setup?
[16:15] <alexmoldovan> I'll check if some of them have, but the netbooks have a very limited BIOS options
[16:15] <BenC> if you test that, and it works, then it sounds like userspace just isn't setting the alarm properly
[16:16] <cking> Here is some thing that may be helpful: http://smackerelofopinion.blogspot.com/2009/08/acpi-wake-alarm-bugs.html
[16:16] <BenC> alexmoldovan: it's been awhile since I messed with setting the wakeup alarm...does the script verify that the alarm was set by reading back the value?
[16:16] <smb> cking, I think you also had some test script
[16:16] <JFo> chrisccoulson_, given your explanation, I am not entirely sure, it sounds like a network manager issue.
[16:16] <cking> it references a test script in the blog 
[16:17] <alexmoldovan> the one I use is taken from chackbox : http://pastebin.ubuntu.com/397848/
[16:17] <cking> http://kernel.ubuntu.com/git?p=cking/scripts/.git;a=blob;f=acpi-wakealarm-test/wakealarm.sh;h=a1674689dc49d0ffbea8f3bf76e529cfe445901c;hb=c88cec173caa995d3737437a82082152e34a46fc
[16:17] <JFo> chrisccoulson_, I'll look at the bug a bit deeper
[16:17] <chrisccoulson_> JFo - yeah, possibly. although I can't recreate it today ;)
[16:17] <JFo> hmmm
[16:17] <JFo> fun :)
[16:17] <chrisccoulson_> but, i'm sure the issue i saw yesterday was not kernel related
[16:17] <cking> alexmoldovan, perhaps those links may be useful for resolving your bug
[16:18] <JFo> chrisccoulson_, yeah, I agree
[16:18] <alexmoldovan> We want to find a way to automatize the tests in the lab even further. So far, we have to manually start up each machine from the power button.
[16:19]  * BenC thought that's what interns were for ;)
[16:19] <alexmoldovan> Thanks for the quick response to everyone!
[16:20] <amitk> BenC, reminiscing your internships? :)
[16:22] <BenC> hehe, a little grunt work never hurt anyone
[16:22] <cking> well, that's the theory, anyhow
[16:23] <alexmoldovan> I like it, though it would save time. So far we have ~70 laptops, but we'll have more in the future.
[16:24]  * JFo suggests a long stick with a pencil taped to the end :-P
[16:24] <JFo> j/k
[16:24] <cking> alexmoldovan, well, checkout that blog article and see if it helps. If not, it's probably a ACPI/BIOS issue :-(
[16:25] <alexmoldovan> I thought we could buy a trained monkey from a circus. After that our only worry will be buying bananas
[16:26] <BenC> alexmoldovan: and banana peels on the lab floor...
[16:26] <cking> not very appealing
[16:26] <JFo> alexmoldovan, that and cleaning up monkey poo that he slung at you :-)
[16:27] <JFo> nice one cking 
[16:27] <alexmoldovan> I'd like to thank those who worked on the core i5 with graphics integrated in the CPU, we have one of those in the lad and in lucid it works flawlessly
[16:30] <cnd> JFo: are you running amd64 or i386 on your mini 10?
[16:33] <cking> isn't the mini 10 an Atom?
[16:35] <JFo> cnd, i386
[16:36] <JFo> cking, it is
[16:36] <cking> which case it can only do i386
[16:36] <JFo> yup
[17:17] <bjf> x
[17:29] <Sarvatt> apw: do you have a mmiotrace enabled kernel anywhere by any chance?
[17:29] <Sarvatt> tseliot needs it to make a dump so his nva3 GPU can get supported by nouveau, they've been trying to find someone with one to do a dump for months
[17:30] <apw> Sarvatt, its possible that one you are testing has it
[17:30] <Sarvatt> oh let me check
[17:31] <Sarvatt> sweet it does, thanks!
[17:31] <apw> Sarvatt, yeah it should have ... yay
[17:33] <Sarvatt> apw: what did you change in the disable FBC on i915GM/i945GM patch I sent you for this kernel you built?
[17:36] <apw> Sarvatt, i didn't reformat the layout of the options at the top when removing the .has_fbc options
[17:36] <apw> as that makes the end stay the same, where new options are likely to appear
[17:36] <apw> reducing the likelyhood of collision with other patches
[17:37] <apw> Sarvatt, second i changed the bit where it assigned the fbc functions instead of removing the bits down there, i added HAS_FBC to the surrounding if
[17:37] <apw> the first change to reduce collissions if we have to carry it, the second cause it seemed safer in the future as it reminds us that bit is about FBC
[17:41] <apw> Sarvatt, make sense?
[17:41] <Sarvatt> i'm not sure about the change to the latter hunk, I think its the way it is to account for some other devices
[17:42] <apw> though those functions are only for fbc
[17:43] <apw> they are called _fbc and only called from places which check for fbc as far as i can see
[17:43] <apw> all of the MOBILE things have FBC until we stop some of them
[17:44] <apw> my main reason to change it was i felt we lost information, which fbc routines when with those cards
[17:44] <apw> but i can be persuaded
[17:44] <apw> ...
[17:44]  * apw has to run to another location, will check in later
[17:45] <KB1JWQ> Ooh, kernel bug!  http://pastebin.com/DZm70xam Note the end, causes ndiswrapper to die
[17:47] <KB1JWQ> I'm open to suggestions besides "return the USB wireless card"
[17:58] <Sarvatt> apw: guess it doesn't matter unless they add something later with has_fbc and  is_mobile and doesn't use i8xx_fbc-* for setup and is checked after that part
[17:58] <Sarvatt> ironlake-m FBC support that'll be coming in any time now is checked before if (IS_GM45(dev)) so thats safe
[18:03] <Sarvatt> just about to hit the 4 hour mark of stability with disabled FBC post resume and powersave=1 on my 945 \o/