/srv/irclogs.ubuntu.com/2010/03/02/#ubuntu-kernel.txt

RAOFPerth's pretty nice, too. Although it's suffering somewhat from the house-requires-firstborn-child now.00:01
lifelessRAOF: what?00:03
RAOFPerth house prices are moderately nutty now, what with the (continuing) resource boom.00:04
lifelessyes00:04
lifelessbut how does the firstborn come into it? or are you just saying expensive ? :)00:04
RAOFI'm just saying expensive.00:05
RAOFPerhaps in an overly roundabout way.00:05
=== bjf is now known as bjf-afk
apwsmb, any sign of a .33.y appearing yet?10:59
smbApart from the tree which is there?10:59
smbNothing in GKH s repo11:00
smbQ-FUNK, I saw your comments/updates on the bugs. Though I don't think not having a initramfs is a real workaround as it still seems to cause issues. Just not fatal.11:04
smbQ-FUNK, Though as we had some issues with Atom based CPUs, you might try the following option "mem=nopentium"11:05
Q-FUNKsmb: correct.  it makes the bug non-fatal, but it also deprives users from the initramfs functionalities.11:05
smbQ-FUNK, I know yours is a Geode, but who knows, whether those share something11:06
Q-FUNKsmb: I was mostly currious about instructions on how to figure out exactly what part of the initramfs payload is the culprit that messes with sysfs in a fatal way, whenever an initramfs image is used.11:06
Q-FUNKsmb: well, geode technically is a i586, but sure, I can try that cmdline option.11:07
smbQ-FUNK, I don't think anything specific, the chances are high that it too changes timings. And having one less fs mounted also changes the chances of hitting a weird behavior in fs code11:07
smbQ-FUNK, The option will cause it not to use large (4M) pages but only 4K ones.11:08
smbBut the weird behavior there always could not really be associated to code in the fs. Actually the fact that reading values just put into variables back made the error go away completely very much points to something with processor caches. 11:10
smbQ-FUNK, I will be away for a bit, but please let us know if that option helps. It would give a bit more ideas on what to look for.11:12
Q-FUNKsmb: I'm about to reboot the host with that option now.11:13
Q-FUNKsmb: I'm not sure if these results are conclusive, but please see my additional comments.12:11
* apw is curious as to the bug number13:18
smbug 39628613:22
smbbug 39628613:22
ubot3Malone bug 396286 in linux "[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] https://launchpad.net/bugs/39628613:23
smbapw, ^13:24
apwta13:24
Q-FUNKapw: any ideas on how to solve this bug 396286 ?13:51
ubot3Malone bug 396286 in linux "[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] https://launchpad.net/bugs/39628613:51
apwQ-FUNK, nothing other than what has been suggested13:51
apwQ-FUNK, in the bug you say 'noraid' helped but don't indicate in what way it helped13:52
Q-FUNKapw: I did. it made the error messages go away.13:52
apwyour text says "without initramfs" to my reading it doesn't say if just the noraid is a work around with no other change13:53
mozmckI get four errors like this trying to compile the karmic kernel from git:13:58
mozmckdrivers/usb/core/hcd.c:144: error: expected expression before '>>' token13:58
mozmckI'm using tag Ubuntu-2.6.31-20.5713:59
mozmckany idea why?13:59
aboganimozmck: Try git reset --hard origin13:59
mozmckbleh, I installed a patch, will it undo that?  I'm pretty sure my patch didn't touch that file...14:00
aboganimozmck: Yes it'll do it.14:01
smbQ-FUNK, apw My guess is that using noraid just avoids disk access because it does not need to scan for signatures...14:02
Q-FUNKsmb: that sounds plausible.14:03
Q-FUNKsmb: I really thought that this nopentium was gonna be it, since what it reports is a paging error.  apparently wasn't.14:07
apwso at least we have some knd of work around with noraid right14:09
smbQ-FUNK, It was worth a try. As it prevents the need to split large pages it would help if the Geode had issues there. Not that the CPU could have other issues. But I must say that I don't know how to proceed from here14:09
Q-FUNKit feels that way, although it baffles me as to why.  14:09
smbapw, If I understood correctly this is only without having a initrd as well14:09
apwsmb, that is not what i was just told iiuc14:10
Q-FUNKright. it didn't seem to affect operation with an initrd.14:10
apwok does that mean that with an initrd it was still broken or not?14:10
Q-FUNKstill borken with an initrd.14:10
Q-FUNKit only made the errors disappear when running without initrd.14:11
smbIt feels a bit like disk activity at early boot -> problem. Maybe bad DMA? But why does it work when getting past that stage? And why does it help to read back a value that got written to a struct (is it really read or from a cache)?14:14
Q-FUNKfrom cache.14:14
Q-FUNKthe errors appeared with 2.6.31, when ACL caching was added to all filesystem types.14:14
smbQ-FUNK, I meant a cpu cache. The ACL caching just happens to be some structure that really has bad effects when being wrong14:15
Q-FUNKah14:15
apwone has to be suspicious that this cpu has a flaw14:16
Q-FUNKI doubt it, since kernels up to 2.6.30 run flawlessly.14:16
Q-FUNKthere's really something shady that was done starting with 2.6.31 that buggers.14:17
smbQ-FUNK, This can just be something that was flawed before, but with the other changes now takes place14:18
Q-FUNKthen again, a similar change happened with 2.6.23 that already killed support for older geodes.  that time, it was a known change and easy to spot.  not so this time.14:18
Q-FUNKapw had tried to help me inviestigate that older bug.  it turns out it was a complete rewrite of how some interupts are handled.14:19
Q-FUNKand there was no turning back on that change.  support for older geodes is factually gone (unless someone is willing to figure out what's wrong with the new implementation for that interrupt handler).14:25
smbQ-FUNK, Well the code change that triggers your problems this time has showed no bad parts on its own. Make a structure a bit bigger to add two pointers. Set those pointers to -1 (all bits set) and take that value as unset. Checking access functions to these pointers they are not accessed after init. But still some bits get cleared. But not if you read back the pointers directly after you written the values to the structure.14:25
Q-FUNKI'm wondering if what we're not seeing might be in some new include that implements the ACL caching's core functions or a mere copy/paste error.14:29
tgardnerapw, what are the odds that a karmic->lucid upgrade will wreck my life? nVidia dual head being the salient issue.14:46
apwdo both your heads work now?14:46
apwthere are also hints that suspend/resume does not work so well with nvidia14:46
apwi would be concerned, and recommend you take a usb stick and test it before committing14:47
apwtgardner, ^14:47
tgardnerapw, yep. both heads work. I never suspend/resume this box anyways.14:47
tgardnerapw, any reports of neauvou (sp?) working with 2 heads?14:48
apwnouveau, i think the only report i have had was from smb who had poor experience with his external14:49
tgardnerapw, thats different then a dual display14:49
tgardnerdual DVI14:49
smbRight, its only single VGA14:50
smb(but behind monitor switch)14:50
apwpoint, then i think you'd be the first.  i'd be interested to know how it worked out but have no bacjground14:50
* tgardner is not often a first adopter :)14:50
apwtgardner, what does msm stand for in our new branch14:58
tgardnerapw, mobile station modem15:00
apwtgardner, i assume i should be treating this like any other distro arm kernel and making it work with our userspace15:09
tgardnerapw, yep, did I miss some config options?15:09
apwno but there is a bunch of recent backports to handle lucid userspace15:10
apwamd pulling them over now15:10
tgardnerapw, ppoll et al?15:11
apwdevtmpfs, modules.builtin async_populatefs, kmsg permissions and ppoll15:11
tgardneregads, I missed a bunch of stuff15:12
apwnothing major, will take 10 mins i hope15:12
tgardnerapw, just rebase that branch instead of starting a new release. 15:13
apwtgardner, will do15:13
apwtgardner, how are we going to keep this branch in sync with other development?15:18
tgardnerapw, other development? do you mean the chromeos tree?15:19
apwyeah i assume its going to be developed in a way that we have this lucid delta15:20
apwand need to maintain that on top15:20
tgardnerapw, we _should_ be able to just cherrypick from the msm Qualcomm 2.6.21.12 branch. However, I don't expect that they'll be making many more changes.15:21
tgardner2.6.31.12*15:21
apwtgardner, ok cool, i guess we'll need to get that documented, where the master tree is sort of thing15:21
tgardnerapw, I created a README*15:22
apwahh good15:22
tgardnerapw, this may not be cast in stone yet. Martin is pushing to cut over to 2.6.32 sometime in March.15:23
apwso we may have a replacement branch at .32 anyhow15:23
tgardnerapw, possibly.15:23
apwtgardner, ok am bulding the 'final' branch now ...15:26
tgardnerapw, ah, at least those patches just slid in. I can't remember if the config checks ended up in the karmic tree, from whence this originated15:27
apwheh no they arn't there yet, the backport will pull those over, one more thing on my todo which is nearly done15:27
apwtgardner, you using anything special to build test this branch?15:29
apw/home/apw/build/lucid/ubuntu-lucid/arch/arm/mach-msm/avs_hw.S: Assembler messages:15:29
apw/home/apw/build/lucid/ubuntu-lucid/arch/arm/mach-msm/avs_hw.S:36: Error: selected processor does not support `fmrx r3,fpexc'15:29
manjotgardner, I saw you ans to the firmware question I had, the fw is not in any of the linux-firmware or linux-firmware-nonfree tree but it is part of the tarball source package 15:30
tgardnerapw, different cross-compile tools then I'm using?15:30
apwi am using the 2009q3 toolchains from code-sourcery, what you got?15:30
tgardnermanjo, thats not really relevant. there must be a license for the firmware.15:32
tgardnerapw, arm-2008q3, so I'm down-rev15:32
apwhrm15:32
apwtgardner, then i am suspicious its not toolchain15:32
tgardnerapw, push your changes and I'm upgrade and get it sorted.15:32
apwcan you pastebin your incantation to build it15:32
apwi suspect its me15:33
tgardnerapw, hang on...15:33
* apw holds everything and looks pensive15:33
tgardnerapw, :) 'debuild --set-envvar=CONCURRENCY_LEVEL=1 --set-envvar=CROSS_COMPILE=arm-none-linux-gnueabi- --prepend-path=$(CROSSTOOLS_ROOT)/bin -b -nc -aarmel -us -uc'15:33
tgardnerapw, nothing special really15:34
apwtgardner, ok branch pushed ... see if that builds for you15:35
tgardnerapw, ack15:35
manjotgardner, where should I be looking for a firmware license?15:37
tgardnermanjo, I assume in that tarball.15:37
tgardnermanjo, work with cnd. He's well versed in the issues.15:38
manjocnd, ^^15:38
cndmanjo, give me a minute, writing up a bug report comment15:38
apwtgardner, same when invoked direct like you did ... oddness15:40
tgardnerapw, building, it'll be done in a couple minutes15:41
apwits breaks right a the start for me, you using the old or new toolchaings15:41
tgardnerthe old one15:41
tgardner2008q315:41
apwyep, a good test15:41
apwthats a royal pain in the bottom15:42
Sarvatthas anyone seen any bugs around where 2.6.32-rc2+ need MMC/SDHC built into the kernel instead of as modules to get around hangs on suspend if a SD card has ever been mounted?15:42
tgardnerapw, looks like its gonna finish15:42
apwSarvatt, i think there was a few issues with mmc, i remember not being able to get them auto mounted, not sure i remember that specific error thoug15:43
tgardnerapw, suppose there is a compiler flag that we need? I'll get the 2009q3 version and mess with it.15:43
apwtgardner, so the only question is why the tool chain is pissed off, is that a port issue15:43
apwi could upload it and see if it builds i guess15:43
apwwould make testing hard and annoying tho15:44
cndmanjo, have you found the license in the tarball?15:44
tgardnerapw, yeah, lets try and sort it before creating archive carnage15:44
apwtgardner, works for me15:44
manjocnd, no there is no such file15:44
Sarvatti built a kernel with SDHC/MMC built in and unsafe resume enabled and I'm able to suspend, but with the ubuntu kernels where they are modules it hangs when I try to suspend if I've ever mounted the sd and suspends fine even with a sd in the slot as long as I've never mounted it15:44
Sarvattso strange15:44
apwtgardner, i am suspecting we need to get on the mir bandwagon too before we could upload it15:44
cndmanjo, does it seem to be an oversight on their part (i.e. it looks like it should be redistributable, but they don't have a license file)?15:45
apwSarvatt, i suspend routinely with SDHC cards in my mini 10v15:45
cndmanjo: if so, I suggest emailing them to let them know15:45
smbSarvatt, apw I think I tried to suspend on 2.6.32 but failed when a mmc card was mounted. But I have not tested lately...15:45
cndmanjo: for now though, we'll need to put it in linux-firmware-nonfree15:45
manjocnd, I am emailing them now to find out 15:45
Sarvattit doesnt work on a mini9, you're lucky apw :D 15:45
smbapw, Is yours the one attached to a usb controller...15:45
manjocnd, is linux-firmware-nonfree part of our repos ? 15:45
apwmanjo, is there no licence on the whole tarball?15:45
cndmanjo: for -nonfree you have to use apt-get source15:46
cndmanjo: there's no git tree15:46
apwif not its not obvious we can take the driver either15:46
cndmanjo: it should be fairly obvious how it builds in debian/rules15:46
manjocnd, wait I am confused 15:46
tgardnerapw, nah, I think this can be a universe package for the time being.15:47
Sarvattsmb: did it hang with the screen still on when you tried it?15:47
manjocnd, there are is no repo for linux-firmware-nonfree, then where do I add the fw to ? 15:47
apwtgardner, is there any hoop jumping for uploading a new package to universe?15:47
cndmanjo: there's no git tree, the process is just 1. take the latest package source 2. update it 3. upload the new source to somewhere rtg can get to 4. tell him to upload it into lucid15:48
tgardnerapw, nope, you only have to be a core-dev, or have rights to linux source package (AFAIK)15:48
smbSarvatt, backlight, yes (but blank/black screen) Seems to be the same right now15:48
manjocnd, you are suggesting a dkms package ? 15:48
manjofor the fw ? 15:48
apwgood enough you'll be able to shove it in then, i won't as i suspect i can't ask for upload rights to it till you have uploaded it once15:48
cndmanjo: no, a dkms package is only meant for kernel modules15:48
cndmanjo: this is like typical debian packaging15:49
Sarvattah my screen still shows what was on it when i suspended here, it definitely does most of the suspend because i hear the acerhdf module unloading and fan spinning up and when i reboot the network is still disabled15:49
cndmanjo: dkms is a package you install that builds a new kernel module from source for every kernel you subsequently install, so it's a special type of debian package15:49
cndmanjo: most debian packages are already built in binary form, so they just install files to the filesystem15:49
manjocnd, I know what debian packages are 15:50
smbSarvatt, This is an Acer Aspire One as well?15:50
manjoI still don't get it 15:50
Sarvattyeah acer aspire one AOA15015:50
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/477106/comments/615:50
ubot3Malone bug 477106 in linux "[regression] lucid alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware" [Undecided,Confirmed] 15:50
cndmanjo: where's the disconnect?15:50
smbSarvatt, Mine is AOA11015:50
apwmanjo, the package is only in the archive, you get the source with apt-get source <foo>15:50
apwchange it and upload that againt, it exists nowhere else but the archive15:51
manjoapw, ah! so don't add to /ubuntu 15:51
Sarvattsame thing then but mines the HDD model15:51
=== bjf-afk is now known as bjf
apwthis is just for the firmware ...15:51
apwmanjo, does this driver have any licence at all?  where did you get it?15:51
cndapw, manjo, it's just for firmware-nonfree15:51
cndlinux-firmware is kept in git15:52
apwcnd, right15:52
apwi meant in his case we were talking about just the firmware15:52
cndyeah15:52
smbSarvatt, Yes, so mine fades the screen to dark, fan is spinning to, then stays there as well. I see some disk activity before which stops at some point15:52
smbSarvatt, I believe apw's sd slot is a USB device while the aoa is a pci/jmicron15:53
apwsmb, yes could be15:53
apwplease don't tell me there are more issues, thanks a lot15:53
* Sarvatt nods15:53
smbapw, I can tell you not if you prefer. :-P15:55
Sarvatti'll have to try just building mmc/sdhci/sdhci-pci into the kernel and not enabling unsafe resume to see if that also fixes it15:55
apwSarvatt, sounds good, get a bug filed and let us know the number15:56
apwi'll need to find someone who can reproduce it to try and fix it ... :)15:56
bjf##15:57
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting15:57
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting15:57
bjf##15:57
smbSarvatt, Yes, that would provide a better pointer. With unsafe suspend the card will not get ejected on suspend. iirc. And that might be the difference that counts15:59
apwsmb, yeah mine get bounced every time i suspend i think16:00
smbapw, Though probably through a different mechanism. Just guessing, but usb probably has eject code in the core, while mmc does something similar somewhere else16:01
apwi think my big latop has an mmc, but that machine is broken for suspend already16:01
* bjf just noticed the team meeting date in the topic16:02
smbbjf, But we cannot change it16:02
smbSarvatt, In my tests I can suspend even after having had mounted the SD card. It just must not be mounted on suspend16:03
apwindeed one needs to be an op to do that16:03
Sarvattapw: there's a bug here - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/477106 building a kernel with just the sd stuff built in and no unsafe resume now to see if that also works. i always enable unsafe resume on the kernels I build because its a pain remounting every resume when I usually have files open on the SD at suspend time :D16:03
ubot3Malone bug 477106 in linux "[regression] lucid alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware" [Undecided,Confirmed] 16:03
Sarvattsmb: odd, here if I have ever mounted it even if its unmounted at suspend time it still hangs16:04
Sarvattsmb: are you using the left SD slot?16:04
smbSarvatt, Yes, the right one only work(ed)s when I have a card in on boot 16:05
apwKeybuk, hey ... i have a preliminary patch for this readahead tracking, and wondered if you fancy testing it16:05
Keybukapw: hey, could you mail me the details and stuff16:06
KeybukI'm in the middle of Plymouth at the moment and can't really drop state since this does need to be working by β116:06
apwKeybuk, will do16:07
Sarvattbtw smb, you might want to add enable_mtrr_cleanup mtrr_spare_reg_nr=1 to the kernel command line on your aspire one since they have screwy mtrr's16:17
smbSarvatt, Heh, I know. I have enable_mtrr_cleanup alone. 16:18
Sarvattany particular reason we dont enable pcie aspm in the kernel config?16:18
smbSarvatt, Because its marked experimental and "in doubt say no"?16:18
Sarvatti could have sworn experimental got removed a few releases ago but I just looked and you're right16:20
bjfsmb, did you want to change the topic?16:21
smbbjf, Yes, tried it before16:23
apwyou nneed to be an op, 16:23
bjfsmb, I'm in #ubuntu-ops asking16:24
johanbrSarvatt, https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/342096 seems related and has some useful information16:24
ubot3Malone bug 342096 in pm-utils "SD Card containing /home corrupted on resume" [Undecided,Confirmed] 16:24
Sarvatt /home on sd needs unsafe resume enabled in the kernel config, need to build your own kernel for that16:25
* smb wonders whether that was his bug filed for Karmic16:26
Sarvattthat should probably be wontfix since i doubt you guys are ever going to enable unsafe resume by default :D16:27
Sarvattoh looks like you did in hardy16:28
smbSarvatt, Somehow it feels like unsafe might be safer than safe16:29
Sarvattohh nice16:31
smbSarvatt, would unsafe resume work for you also when built as a module? Won't promise anything but it might help on a decision16:31
SarvattThis option sets a default which can be overridden by the module parameter "removable=0" or "removable=1".                   16:31
Sarvattcan test that without rebuilding the kernel now16:31
Sarvattunsafe resume depends on MMC being built in and not a module unfortunately16:36
Sarvattah nevermind CONFIG_MMC=y is what it needs and thats already there16:37
Sarvattso booting with mmc.removable=1 should work, lets see16:38
smbSarvatt, I am not sure were you exactly get that option from. The code looks to me like completely changing functions when UNSAFE_RESUME gets set16:42
apwjjohansen, hiya, i've been playing with rebasing the -ec2 kernel, as there are lots of interactions i have created ... there were two conflicts in the early patches is just correcting those the righ way forward16:46
apwjjohansen, will have some images from those for potential testing shortly16:46
jjohansenapw: okay16:46
apwam i correct to just fix conflicts or is there a magic way16:46
jjohansenapw: just fix them16:47
apwcool16:47
jjohansenand pray it doesn't break16:47
jjohansen:)16:47
jjohansenapw: I am running slightly behind (sleep caught up with me) will finish pam_apparmor today16:48
bjf##16:48
bjf## Kernel team meeting in 10 minutes16:48
bjf##16:48
apwjjohansen, heh yeah thanks ...16:49
bjf##16:58
bjf## Meeting starting now16:58
bjf##16:58
apwjjohansen, those new lucid ec2 kernels are here: http://people.canonical.com/~apw/ec2-lucid/17:11
jjohansenapw: thanks17:12
apwwe don't get much in the way of interactivity in our meeting ... hrm17:15
smbapw, At least we get it done quick17:15
cndapw, fyi I'm working on a patch against the alsa driver to prevent a warning message from polluting the boot splash screen (it's level is KERN_ERR, which upstream has acknowledged is too high)17:15
cndoops, against acpi17:15
cndnot alsa17:16
apwcnd sounds ok, that would be a minor change, and a bug fix so i am sure we can get that past the ack process after freeze if its not ready in time17:16
apwsmb, ^^17:16
smbcnd, That is a bug fix17:16
smbyeah17:16
apwcnd, but bringing it up is the right thing17:16
Sarvattsmb: i pasted that from the kernel config option, but its in drivers/mmc/core.c17:43
smbSarvatt, Seems to be upstream but not Lucid. If I am not looking at the wrong version17:47
Sarvattsmb: booting with mmc.removable=0 (aka enabling unsafe resume) changed it so the screen goes black but the backlight is still on like you were saying you get17:47
Sarvattwell thats odd, i did it with the lucid kernel and it changed what happens when i suspend17:48
smbSarvatt, That option was added in 2.6.33 and I do not remember it being in stable. Basically you know have the same behavior as I do without anything specially set.17:53
smbBut the option should have no effect other than being ignored17:53
tgardnerapw, if I was going to be able to enable 2 monitors, then one would expect they'd both be detected in 'Monitor Preferences", right?18:02
apwi would expect so, but i would also  run xrandr to see what happens when you do, and also to see what it says you have18:03
tgardnerapw, hmm, it sorta thinks I _might_ have 2 displays. I think I'm gonna install to an external HD first and do some experimenting lest I totally wreck my dev box.18:08
apwtgardner, very sensible18:09
Sarvattsmb: without mmc.removable=0 and a SD mounted suspend freezes with the screen contents still on the screen, with the option I get a vt switch and the backlight is still on and the screen is blank. I just reproduced it 4 times with each method even though mmc.removable=0 doesn't do anything on 2.6.32-15. very confusing18:12
Sarvatti still have the kernel where all the mmc stuff was built in though and I can just boot that with mmc.removable=1 to test if disabling unsafe resume with the modules built in works on .33 at least18:14
smbSarvatt, That is indeed beyond my understanding. Yes, in .33 it should (in theory work that way)18:16
Sarvatt2.6.33-rc8 + mmc.removable=1 (aka disabled unsafe resume config option) + mmc/sdhc modules built in works18:18
manjocnd, apw sorry I had to drop off I had an emergency18:33
cndmanjo: how far did you get with the firmware stuff?18:34
manjocnd, I will get together with you in 2 hrs or so and sort this firmaware stuff out 18:34
cndmanjo: ok18:34
manjocnd, I still need to be away for a little bit.18:34
cndmanjo: if you have pressing, more important issues I can do the firmware work for you18:34
manjocnd, you mean I just give you the fw files and you magically make them appear in /lib/firmaware/RTL8192SE/ ?18:35
cndmanjo: I mean I take the bug and work it and get it uploaded for you18:35
manjocnd can I skype you quickly ?18:36
cndsure, one sec18:36
cndneed to get headset18:36
cndmanjo: ready18:37
manjoI don't think I have you on my list18:37
manjocnd, what skype id ? 18:38
cndmanjo: corp18618:38
cndI'm not keen on providing my details in the skype directory :)18:38
=== KB1JWQ is now known as Sorthum
=== Sorthum is now known as KB1JWQ
cndanyone familiar with hotplug?18:51
cndI've read the README in Documentation, it says the kernel somehow calls "hotplug" in userspace to do stuff, and there's a sample hotplug script18:51
cndbut I don't know of any hotplug user space script or executable18:52
smbcnd, That sounds like old cruft, when there was a callout to a hotplug script18:52
cndsmb, do you know how it's done now?18:52
cndis it all in-kernel through vfs?18:53
smbcnd, But that has been all replaced by netlink(?) messages. And udev reads those messages18:53
cndhmmm18:53
cndsmb, looks like udev now handles hotplug events, but the mechanism is still the same18:56
cndit's just that the hotplug script is now part of udev18:56
cndI've found it in /lib/udev/firmware.sh18:56
smbcnd, The method is uevent, not netlink. Too late here. But its a bit more than that.18:59
cndsmb, I'm most interested in the firmware loading part, not the event propagation part, so I think I've found what I need18:59
cndthanks19:00
smbcnd, ok.19:00
=== Hedge|Hog is now known as Hedgehog
=== Hedgehog is now known as Guest31246
Sarvatthmm wasn't this upstream in the 2.6.29 timeframe? UBUNTU: Disable 4MB page tables for Atom, work around errata AAE44 - http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=97684193e8c6fea095adcc4928f389b090559fc619:20
Sarvattaka shouldnt be needed to be backported to karmic-lucid19:21
jjohansenapw: your EC2 kernels are as good as the last set (ie. doesn't fix outstanding bug but doesn't introduce any new ones that I can see)19:23
Sarvattyeah the fix is already there at line 535 - http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=blob;f=arch/x86/mm/pageattr.c;h=dd38bfbefd1fa1972f47403fa6b35e20663e3590;hb=97684193e8c6fea095adcc4928f389b090559fc619:24
Sarvatthttp://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=211b3d03c7400f48a781977a50104c9d12f4e22919:26
SarvattI put a note on https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/523112 about how its already in the kernel for lucid apw19:30
ubot3Malone bug 523112 in linux "Intel Atom CPU can oops because of bug listed in Intel errata AAH41 and AAE44" [Medium,Fix committed] 19:30
cndis there anything that can be done about an rfkill hard blocked device?19:36
cndthe external switch is set to on, so I'm guessing it's something that's either in the bios or set in some windows driver?19:37
cndbdmurray: I'm removing your patch tag on bug 530348 because the patch is diagnostic in nature, not a "fix"20:45
ubot3Malone bug 530348 in linux-firmware "e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin" [Undecided,Incomplete] https://launchpad.net/bugs/53034820:45
bdmurraycnd: then maybe the attachment shouldn't be flagged as a patch?20:46
cndbdmurray: it's still technically a patch20:47
bdmurraybut not a patch that fixes the bug which is what the flag should be used for20:47
ogasawarabdmurray, cnd: yah, I'd vote to not flag the attachment as a patch20:47
cndbdmurray: ok, bugzilla land is different20:47
cndyou flag things that are patches in bugzilla land so that the attachment viewer handles them correctly20:48
cndmaybe the flag should be called patch-fix?20:48
manjocnd, I added the firmware to the linux-firware-nonfree package, and it build and works fine, how do I modifiy the changelog ? 22:07
manjosince this is not a git package 22:07
manjoor git tree22:07
cndmanjo: dch -i starts a new changelog template and opens it in your $EDITOR22:07
manjoduh! ok 22:08
manjothought there was some other magic to it 22:09
cndmanjo: nope, pretty simle22:17
cndthe magic comes when you're using a git tree22:17
manjocnd, after I do that just tar up the direcotry and upload to zinc ? 22:17
cndmanjo: so you've been building by running debuild right?22:17
manjoyes22:17
akgranerbjf, ping22:18
cndso, first delete everything debuild created in .. (this will make it easier to figure out what's created in the next step)22:18
cndmanjo: then run debuild -S22:18
cndthat should create a source.changes file, .dsc file, and tarball file22:18
manjook22:18
manjoit did 22:18
bjfakgraner, yo!22:19
cndthen upload it somewhere, like I did at kernel.ubuntu.com/~cndougla/linux-firmware-nonfree22:19
cndand then yell at rtg :)22:20
manjocnd, why did mine get renamed to linux-firmware-nonfree-1.6ubuntu1 ?22:20
cndmanjo: ahhh, dch -i be default appends a new ubuntu release version (maybe there's a better option than -i?)22:20
cndso in your changelog you should change that to -1.722:21
cndmanjo: looks like dch -v 1.7 would have been the best route22:21
manjook I will redo22:21
cndmanjo: you don't really need to undo what you did though22:22
cndjust modify the changelog 22:22
manjocnd, thanks a ton 22:29
manjoits done 22:29
cndmanjo: np, you got it uploaded some where?22:30
manjocnd, sorry I had to step out a few times during the day... so get interrupted getting this done 22:30
cndmanjo: that's fine, I hope the therapy helped with whatever issues you had22:30
manjoyep its on my people page ... http://people.canonical.com/~manjo/lp530275-lucid/firmware-nonfree/22:31
cndmanjo: btw, you don't need the .build file22:31
cndthat's just a log of the build process22:31
manjoyeah I did an scp * so that got in as well22:31
cndwhich for a source package build is even less useful :)22:31
cndmanjo: what did rtg say about the format of directories in the package?22:32
manjocnd, I did not talk to him yet... I am shipping the firmware to lib/firmware and that is where the driver is picking it up from22:33
manjocnd, but looks like its really a simple change to the rules script to do it 22:33
manjoright 22:33
cndok22:33
manjocnd, too late in the cycle to mess with it now 22:34
cndheh22:35
=== sconklin is now known as sconklin-gone

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