/srv/irclogs.ubuntu.com/2011/02/14/#ubuntu-kernel.txt

=== cmagina-afk is now known as cmagina
=== _LibertyZero is now known as [DooF][HC]Libert
=== [DooF][HC]Libert is now known as LibertyZero
=== almaisan-away is now known as al-maisan
* apw yawns08:15
=== smb` is now known as smb
* smb crawls out of the first bath in new email.08:53
apwsmb, heh fun08:54
=== Artir is now known as DanteAshton3
=== DanteAshton3 is now known as Artir
=== Artir is now known as phillw3
=== phillw3 is now known as Artir
=== Artir is now known as DanteAhston
=== DanteAhston is now known as Artir
smallfoot-im using ubuntu 10.10 "maverick", does the 2.6.38-999 kernel from the kernel-ppa work?11:31
=== amitk is now known as amitk-afk
ograapw, around ?12:29
ogradid you drop linux-headers-2.6.32-410-dove from the archive (my images fail to build not finding that package, if you removed it the meta needs to go too)12:30
=== amitk-afk is now known as amitk
=== al-maisan is now known as almaisan-away
smbogra, apw had to leave for some plumbing emergency. It will be a bit till he is back13:28
ograsmb, hmm, do you know anything about the dove kernels by chance ?13:30
tgardnerogra, didn't GrueMaster test both of the recent dove uploads?13:30
smbogra, I have not followed closely. tgardner did you do stuff there by chance? Otherwise I can try to check on the status13:31
ogratgardner, there shouldnt be any dove uploads in natty13:31
tgardnerogra, true. in fact I've requested that dove be removed from the archive for natty13:31
ogratgardner, the point is that apparently the dove headers are gone from the archive 13:31
ogratgardner, but the meta seems to be still there13:31
tgardnerogra, ok, I'll see that the meta gets removed as well13:32
ograall header metas get installed during image builds on arm and the unwanted onse get removed at the end 13:32
ograso one broken meta breaks all images 13:33
tgardnerthat seems an odd way of doing things. however, there is a bug open to remove the kernels, so I'll just add the meta package to it13:33
tgardnerback in a a sec...13:34
ograits a "bug/feature" of the seed management13:34
ogratasks and seeds dont understand subarches, thesy can only operate on toplevel (i.e. armel but not armel+omap)13:34
smbtgardner, cking Maybe you are better at remembering things than me. I just stumbled indirectly over those acpi_skip_timer_override quirks that manjo had been  submitted for Maverick. Were those not intended to go upstream?13:43
yodog!ops13:44
ubot2Help! lamont, zul, T-Bone, mdz, or jdub13:44
yodog!ops13:44
yodog!join #xubuntu13:44
ubot2Factoid 'join #xubuntu' not found13:44
yodog!ops13:46
ubot2Help! lamont, zul, T-Bone, mdz, or jdub13:46
yodog!ops13:46
ckingsmb, dunno - were they upstream worthy?13:47
mjg59smb: The ones for the Lenovos? The problem got root-caused.13:47
smbmjg59, Ah, yes. Those I guess13:47
yodog!opsnigga nigga 13:48
ubot2Factoid 'opsnigga nigga' not found13:48
yodog!ops13:48
ubot2Help! lamont, zul, T-Bone, mdz, or jdub13:48
tsimpsoneh..13:48
smbmjg59, Now, sorry for possibly being dense. Does 'root-caused' mean solved better or something else?13:49
tsimpsonthough he has a dynamic IP, so probably won't last long13:49
mjg59smb: The problem turned out to be that the apic timer was marked with the wrong polarity13:50
smbmjg59, Ahhhh, that ring s a bell13:50
mjg59smb: So the initial interrupt got missed. The skip_timer_override quirk just resulted in it being tied to a pin with the right polarity, so it worked13:50
mjg59smb: But checking the polarity is a more generic fix than just hardcoding some model names, so that's what upstream went with13:50
smbSo we actually should get that fix in then we should be able to revert the other quirks from Maverick13:51
mjg59Right, though it may be a bit more intrusive?13:51
smbThat could be (have to check for the other patch). Just looked at someone asking for yet another model added to the quirks, so the question is what is the lesser evil13:53
mjg59Ah, ok13:53
ckingmjg59, is the wrong polarity marked on APIC timers a configuration bug in the firmware?13:55
mjg59cking: Yeah, though my recollection is that Windows never uses this configuration13:56
mjg59So it'd be easy to miss13:56
ckingbut easy to test for?13:56
mjg59cking: There's some details in the thread on lkml13:56
ckingok - me will look13:56
* tgardner detects another test for fwts in the making13:56
ckingyep - when I get time.13:57
ckinganother "your firmware is broken.. it should be fixed, but the kernel works around it" kind of report.13:57
loftwyrI have a USB3 dock that would not work until I changed CONFIG_USB_GADGET_VBUS_DRAW to 500 from the minimum of 2.  Is there a need for it to be 2 or can that be changed for future kernels?14:00
loftwyrI'm using Natty14:01
tgardnerloftwyr, seems that 2 is the kconfig default. I assume its a safe choice.14:05
loftwyrSafe, perhaps, but can it be changed without a problem?  14:06
tgardnerloftwyr, not without some advice from the upstream developers. They likely chose 2 for a reason.14:07
loftwyrWhere would the best place be to ask them?14:07
tgardnerseems like there ought to be a sysfs interface for changing it14:07
tgardnerloftwyr, from the MAINTAINERS file:14:08
tgardnerUSB GADGET/PERIPHERAL SUBSYSTEM14:08
tgardnerM:      David Brownell <dbrownell@users.sourceforge.net>14:08
tgardnerL:      linux-usb@vger.kernel.org14:08
tgardnerW:      http://www.linux-usb.org/gadget14:08
loftwyrI'll send him a note.  Thanks!14:09
smbmjg59, If I look at the right thread, this ended with "I will submit a patch asap". Jan-28. Maybe that is long enough to carefully ask what time frame this translates into. :)14:14
sforsheeloftwyr, tgardner: I only caught the last half of the conversation, is this about vbus power usage?14:14
tgardnersforshee, yeah, gadget current limits14:14
mjg59smb: Ha :)14:14
loftwyrand the default in the kernel14:15
sforsheeloftwyr, tgardner: the spec allows drawing up to 500 mA, I've always been curious why the default is 214:15
sforsheeI've always used 500 mA in projects I've worked on14:15
loftwyrThat's what I want to find out, is it 2 for a reason or is that a legacy setting?14:16
sforsheeyeah, I don't know the answer to that14:16
sforsheeif you find out I'd be interested to hear :)14:16
tgardnersforshee, you've worked on known HW, though, right? The x86 world is quite that stable.14:16
tgardnerisn't*14:16
sforsheetgardner, I _think_ that is the value that gets reported upstream (to the hub or the host)14:17
sforsheeso you need to know what you're hardware's actually going to try and draw so you can report the correct value14:17
sforsheehow many x86 devices are used as usb gadgets anyway?14:17
sforsheeyou're right though, seems like there should be a sysfs interface14:18
loftwyrWell, my Vantec dock wouldn't work until I upped the minimum gadget draw so I'm assuming that it doesn't report it's needs enough or uses the wrong interface.  14:18
loftwyrI can't seem to find a sysfs setting but I'm still looking14:18
sforsheeloftwyr, yeah, the hub might cut you off if you're trying to draw more than you report you will14:19
loftwyrAs it's a USB3 device, it may be reporting something strange that the subsystem doesn't recognize14:20
sforsheeloftwyr, I don't know about USB3, but USB2 was backwards-compatable14:20
sforsheedevices had to identify as USB2, and if they didn't they would fall back to USB114:20
sforsheeI'd suspect USB3 is the same14:21
loftwyrIt does if the USB3 hub has a USB2 into it.  It all falls to USB2.  It's reporting as USB3 though according to the logs, just doesn't work using the kernel defaults (writes don't get written, etc.)14:22
sforsheeand it all works if you change the vbus draw?14:23
loftwyrYep.  The drivers (JMicron) were already enabled as modules so I assume it's just a power draw issue14:23
sforsheemy initial guess is that the hub is suspending the device because it's drawing more power than what it said it will draw14:24
loftwyrLikely true. That would make sense that when I set the default higher, it doesn't cut it off.14:24
sforsheehitting up David Brownell will probably get you the best answers about it though14:27
loftwyrI've sent off the question, I'll let you all know the answer if/when I get it.14:29
tgardnerogra, natty linux-meta-mvl-dove is gone14:33
ogratgardner, awesome, thanks14:34
=== diwic is now known as diwic_afk
=== diwic_afk is now known as diwic
JFosmb, mind having a look at a bug?14:50
JFo:)14:50
smbJFo, Not if I only have to *look* at it. :)14:50
JFoheh14:50
smbBut I guess you want some comment too14:51
JFoonly if you see that one is needed14:51
JFobug 71154414:51
ubot2JFo: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/711544)14:51
smbDoh! :)14:51
JFoah right, private :-/14:51
JFosorry about that14:51
JFobut that is the bug number14:51
smbBut I should be able to look14:51
JFoyes14:52
smbJFo, Yup14:52
* smb looks14:52
JFothanks amb :-)14:52
JFosigh*14:52
JFoI fail today14:52
JFosmb that is14:52
=== xyclo_ is now known as xyclo
=== cking is now known as cking-afk
=== herton is now known as herton_lunch
=== diwic is now known as diwic_afk
* apw returns ... but he has to have a shower15:34
smbsounds ugly15:34
JFoindeed15:34
* JFo uses a stick to slide the soap toward apw15:35
* tgardner imagines apw smeared with sewage15:35
JFo:-{15:35
=== herton_lunch is now known as herton
apwtgardner, i didn't need to imagine15:43
tgardnerapw, I suspected as much15:44
apwi think i need a strong dring15:55
apwdrink15:55
sforsheeapw, i don't know, looks like your speech is already slurred15:56
apwheheh15:57
apwJFo, our key list seems to be empty ?16:04
JFo!16:04
* JFo looks16:04
apwJFo, its a newish thing cause they were there this morning16:07
JFoapw, I am running some tests16:07
JFotaking a while... apparently there is some lag on the line16:08
apwbjf yep16:08
JFowell, the buglists are generating, so the problem isn't there16:11
JFoI'm doing a run by hand to see if I get any errors16:12
JFobut there is nothing so far16:12
JFoand the list for yesterday is populated16:12
JFoso it has worked over the weekend16:13
JFoas shown here http://reports.qa.ubuntu.com/reports/jfo/kernel-buglist-by-team-archive/kernel-buglist-by-team-2011-02-13.html16:13
apwJFo, as i say it was working this morning for me, so approx 4-5 hours ago16:21
JFoodd that16:23
apwCan't look up definition in another url (https://api.launchpad.net/1.0/#bug)16:24
apwi get that from the second phase16:24
JFosigh*16:24
apwJFo, any idea what it means?16:25
JFonot at all16:25
* sforshee -> reboot16:37
sconklinJFo: From launchpad updates: API scripts talking to the edge cluster are broken with a NotImplementedError. We are investigating to resolve the issue quickly17:04
JFoapw, one sec... otp17:11
JFosconklin, yeah, been trying to figure out WTF17:14
JFosconklin, here is the latest: <leonardr> apw, JFo: the breakage was a mistake that's being fixed. edge will continue to work, but you should stop using it or one day this will happen for real17:14
JFosconklin, :-/17:20
=== sconklin is now known as sconklin-lunch
apwtgardner, i'll have a go at scrubbing lbm for upload for natty 17:50
tgardnerapw, dkms'ing some of those packages is an interesting approach. about the only thing that might not work for are some of the OEM platforms.17:51
apwyeah they do throw the old spanner in the works17:51
apwi wonder if we could use dkms to make them somehow ... like using it to produce static binaries17:52
tgardneryeah, if we could drop LBM altogether. what a time saver.17:53
apwtgardner, yeah there must be a way, i think it would make a good 'OO' project17:53
tgardnerindeed. perhaps we should float the idea at UDS ?17:54
apwas i think we can make a wrapper round them to 'freeze' them on a buildd for those systems which are too slow to really dkms17:54
apwtgardner,ea17:54
apwtgardner, yeah concur17:54
loftwyrJust circling round from this morning.  I sent an e-mail to linux-usb about the USB vbus draw and got this reply: http://ubuntuforums.org/showpost.php?p=10458053&postcount=7.  It seems I have to poke Vantec17:54
ohsixlbm?17:56
tgardnerloftwyr, perhaps you should convince them to implement a sysfs interface for controlling draw.17:56
apwlinux-backport-modules17:56
apwlinux-backports-modules17:57
ohsixah17:57
loftwyrThat's an interesting idea tgardner, I'll ask about it.17:57
tgardnerloftwyr, or failing that, a module parameter.17:58
tgardnerKconfig options are so static.17:58
apwthey are so last year18:00
tgardnerloftwyr, there may well already be a module param. I just haven't looked.18:00
loftwyrLet's see what they say.18:00
loftwyrA sysfs would be so much better as you could tune it on the fly andget the setting that most works18:01
=== sforshee is now known as sforshee-lunch
=== diwic_afk is now known as diwic
JFowow, just had some really odd sound inticator flashiness... not the good kind18:19
=== BenC_ is now known as BenC
loftwyrGetting a fast reply from the USB-linux group (Felix Balbi to be precise).  He says no to an out of kernel control to avoid people melting their USB by setting the draw too high.  "Generally we don't mess too much with things related to power18:26
loftwyrconsumption, it's quite a mess to lie to the USB host and things can go bad easily. Hope it helps."18:26
* tgardner --> lunch18:39
=== sforshee-lunch is now known as sforshee
JFo<-lunch19:09
=== zul_ is now known as zul
tgardnerbjf, did you or sconklin-lunch write anything down in the wiki about how master-next is to be used?19:27
bjftgardner, i don't think so but i've got to look19:27
tgardnerbjf, the wonderful search facilities returned no match on master-next19:28
tgardnerjjohansen, when you get a moment, please review "Lucid/Maverick SRU, NFS: fix the return value of nfs_file_fsync()" on the k-t list19:53
=== zul_ is now known as zul
* jjohansen -> lunch20:51
* sforshee -> reboot20:59
jjohansenanyone else noticed problems with gitk lately?21:24
apwjjohansen, what you seeing?21:26
jjohansenit keeps failing to provide diffs of commits, it will do a few and then it just stops21:27
jjohansenrestart it and click on the commit it failed on before and it works, but a few more and it fails again21:27
apwhow many approx ?21:27
jjohansenseems to be approx 3-421:28
jjohansenit isn't always the same for me21:28
apwjust looked at the top 30 or so without issue, on my natty tree21:29
jjohansenapw: okay thanks21:29
apwjjohansen, that was on a natty box21:30
apwjjohansen, OH i did limit history .. gitk HEAD ^v2.6.3621:30
apwcould you be runnign out of memory for 'all' history21:30
jjohansenapw: well maybe but I haven't ulimited it and I seem to have more than a gig free21:31
jjohansenI'll mess around with it a bit more21:31
apwtends to kill my machine completely21:33
jjohansenyeah pruning it down does help21:35
bjfapw, bug #67702121:40
ubot2Launchpad bug 677021 in linux "Maverick: 2.6.35-23.40 -proposed tracker" [Medium,Fix committed] https://launchpad.net/bugs/67702121:40
apwbjf ?21:42
apwbjf, oh interesting21:43
bjfapw, was that what you were thinking ?21:43
apwbjf, that looks like what pete was suggesting ... didn't know you could do that21:46
bjfapw, it's using some LP terms/ideas in ways they are not intended, but i think it would work21:46
apwi assume that the 'phases' are series ?21:47
bjfapw, yes21:47
bjfapw, so each phase/series could be independently assigned and it's status changed21:48
bjfapw, they could also be worked on in parallel (if possible)21:48
apwbjf, could you have used packages witin 'kernel workflow' for the phases too?21:49
bjfapw, not sure, bug maybe21:49
apwi ask cause this way they can't apply to the in the same way to ubuntu series21:49
apwand wonder if that might be something we might want21:49
bjfapw, not sure i'm tracking why you'd want to do them as packages21:50
apwbjf, i am assuming that you can only have one set of series for a project21:57
apwso if for example we wanted to have one bug for 'this round of uploads'21:58
apwthen we'd want 'upload-it' to have series for each series we have live21:58
apwso i was just musing if we used packages in your new project to represent the21:58
apwphases, we could also have a task in each phase for each series (maverieck, lucid etc)21:59
apwmusing is we were backing self into a corner by using series for phases if it can be either21:59
apwbjf, ^^21:59
bjfapw, every uploaded package get's it's own tracking bug21:59
apwyeah it does currently so it currently makes no difference indeed22:00
apwjust wondering if we might want to both at some point22:00
bjfapw, nothing cast in stone at this point, it's just an experiment for now22:00
apwyeah assumed so, just a thought nothing more, wondering wondering22:01
apwbjf, i can see that working either way pretty well22:05
* sforshee -> reboot22:15
=== sconklin is now known as sconklin-gone
=== bjf is now known as bjf[afk]

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