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

=== zz_bigbash is now known as bigbash
=== bigbash is now known as zz_bigbash
mfilipehow do I do to get .config of oneiric kernel?02:15
mfilipemy kernel is 32bits-pae 02:16
Sarvattmfilipe: /boot/config-3.0.0-whatever-generic02:17
mfilipeSarvatt, thanks a lot! :)02:17
Sarvattreplace whatever with a number of course, dont know what kernel you're using :)02:17
mfilipeSarvatt, default... 3.0.0. I found the config02:23
mfilipe;)02:23
=== smb` is now known as smb
* smb yawns07:38
TeTeTa customer reports random freezes on x220 (sandybridge) with 10.04 and lowell and natty-backports-lts kernel. Is there any magic sysreq thing I can ask them to run to gather useful info from the crashed systems?08:30
smbTeTeT, Depends a bit on what really happens. Is it freezing (desktop only or whole system) or a crash. First may show not much and if the whole system is frozen, the sysrq keys don't work either.08:34
TeTeTsmb: ok, seems system is completely frozen, e.g. ssh doesn't work any longer. Only at times the mouse pointer remains moveable08:35
smbTeTeT, So one thing to try could be to ssh in before and do a tail -f on the syslog and hope to catch something there.08:36
TeTeTsmb: ok, good thing to monitor in real time, I'll suggest that, maybe using the remote option of rsyslog as well08:36
ppisatimorning09:11
ckingmorning09:13
smbmorning09:14
smbcking, You know what, I fixed the jumbled characters in my battery readout that caused udev to go wild...09:15
ckingsmb, how?09:21
ckingsmb, was this a user space fix or in the kernel?09:22
smbcking, Removing the battery for a while... Now the strange characters are gone... :/09:22
ckingoh09:22
ckingthat's kinda amusing09:23
smbSo it was a hardware fix... :-P09:23
ckingstill, the udev issue still needs to be fixed IMHO09:24
smbWished I had thought of that last week. Would have saved me the annoying stop/start cycles on udev09:24
smbI tend to agree, there must be a way to stop a call that has a permanent issue instead of repeating it 09:24
apwjjohansen, hello09:31
smbmorning apw09:32
apwmorning09:32
Kanohi apw , could you take a look in pata_of_platform.c ?10:47
Kanoapw: it seems there must be a 32 bit error?10:48
ppisatiherton: hold on for the omap4 kernel, i'm respinning it11:32
hertonppisati: ok, it's ok to respin it, that problem in the changelog should be fixed11:35
ppisatiherton: yep, but Tim pushed the Linaro revert on top of the previous version, let inclue that patch too11:36
ppisati*let me include11:36
hertonppisati: ok, see if there is an abi change needed also because of the change, may be not, I'm not sure but I think abi check is enabled for this one (only disabled for armhf from what I saw yesterday)11:37
ppisatino abi changes11:38
hertonok cool11:38
ppisatiherton: ok, all done11:57
hertonppisati: ack, thanks11:58
ppisatiherton: and it passed the verify-release-ready test11:58
hertonppisati: tim pushed the patch to you? it misses the signed-off (may be I'm being too pedantic now)12:19
ppisatiherton: nope, it's alreadi in ubuntu-oneiric/ti-omap412:32
ppisati(why kernel.ubuntu.com is always so slow????)12:33
hertonppisati: indeed, I forgot to fetch12:34
ppisatigit://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git ti-omap412:34
* ppisati goes to find something for lunch...12:35
apwcking, about ?  wondering about resurecting the kernel power consumption blueprint, as a bucket for your workitems13:02
apwseems the logical thing to od13:02
tgardnerogasawara, given Rick's test policy, do you suppose we should delay uploading precise until about -rc2 ?13:56
ogasawaratgardner: that sounds safer14:02
tgardnerogasawara, shall I rebase against -rc1 ? I'd like to get some master-next testing under way14:02
smbThough potentially that policy does not apply to us as I think they say Ubuntu developed sw14:02
ogasawaratgardner: go for it14:03
tgardnersmb, folks will howl anyways if we break their kernel14:03
ogasawaratgardner: gimme 5min to push the reverted ntrig patches14:04
tgardnerogasawara, ack14:04
smbtgardner, That is true. Even more if it stops booting... So to wait an rc sounds like a save play14:04
smbtgardner, Btw, not sure whether you would still look at it but 2.6.32.47 feels like soon being followed by a fixup .48. Some patches seem to break builds...14:07
tgardnersmb, yep, saw that. armel failure, right ?14:08
smbtgardner, Well that and an allmodconfig explodes on my amd64 build in some soc module14:08
tgardnersmb, if it builds for our configs, and doesn't break omap3, then its likely still worth applying.14:09
ogasawaratgardner: pushed14:10
tgardnerogasawara, ack14:11
smbtgardner, Not sure whether we would hit those (well the first one likely). I have not yet tried any builds on our side. I'd probably delay until it is fixed, then I can push a fixed up drm33 and we could use that one.14:12
tgardnersmb, do you have some drm patches for this next stable update ?14:13
smbThere is two drm fixes from Debian that I would add as well. And then it might just be one run on the formal (tracking side)14:13
tgardnerok14:13
ogasawaratgardner: fwd'd you a patch from apw to fix a 3.2-rc1 build failure14:14
* smb finds it scary to start answering tgardner questions before he asks them...14:14
tgardnersmb, she's just that good14:14
smbtgardner, I do not count me as a she... ;-P14:15
tgardnersmb, thought you were talking about ogasawara14:15
* apw looks vague14:15
smbNah, I was typing the answer to the drm question when you asked it14:16
smbOf course I am not that fast of a typist so I did not beat you on pressing enter14:16
* smb wonders whether he needs to slap apw...14:16
* apw sends smb a typing tutor14:16
apwsmb, always14:17
tgardnerapw, how's the custom binary maintenance prototype coming? this epoll patch continues to clog my folder.14:17
apwtgardner, heh i was just checking that branch out ...14:17
ppisatitgardner: can you install u-boot-tools on tangerine inside the oneiric-amd64 chroot? need it to create the uImage kernels for arm (when i'm building from vanilla)14:49
tgardnerppisati, done14:52
* ogasawara back in 2015:05
apwtgardner, ok so i have a prototype basically working.  i am a little concerned about the semantics15:59
apwtgardner, essentially we have two options, either clean creates the patches, or we have a 'refresh' option you use for this function16:00
apwin the first instance things are automatic, but local test builds you need to know you need to push the dependant branches also16:00
apwin the latter you need to know to refresh them when changing things, which can be inforced at insertchanges time16:01
apwbut testing is much more 'as it is now'16:01
smbI'd tend towards the refresh option...16:02
ogasawaraare we having a meeting today?16:03
apwug i hope not :)16:03
smbIt would be in one hour, or?16:03
apwbjf, is the master of all things meeting16:03
bjfogasawara, who would run it?16:03
ogasawarabjf: I don't know if we actually decided who's running the meetings now16:04
* jussi waves to ogasawara16:04
apwoh did bjf abdicate ?16:04
ogasawaraapw: he did16:04
* ogasawara waves to jussi 16:04
* smb missed that, too16:04
ogasawaraI don't think it was widely circulated that he stepped down from being the chair16:05
apwwell i am pretty sure noone wants to do it, so perhaps we need to return to a rotating chair16:05
ogasawaraI vote that we postpone till next week.  I'll chair.16:05
bjfogasawara, smb and apw were at the same table with me at plumbers when i made the statement :-)16:06
apwok, works for me.  we need to make sure its nice and documented to the untrained eye so we can rotate it16:06
smbbjf, probably too drunk then... :-P16:06
apwplmbers, plumbers, you expect me to remember that far back ?16:06
bjfsmb, could be though it was in the a.m. at the hotel16:07
=== kamalmostafa is now known as kamal
ckingI recall bjf saying it16:08
smbbjf, Oh, morning bah... 16:08
jussiDO you peoples use the meeting bot for your meetings?  (meetingology) 16:09
apwcking, heh then you should have reminded us :)16:09
apwjussi, yep16:09
bjfjussi, the new bot sucks16:09
cking...and I thought "if it I join the kernel team it means somebody as disorganised as me running the meeting == fail"16:09
jussibjf: how so?16:09
bjfjussi, the output is ignored16:09
jussibjf: more specific pleasE? 16:09
apwit does tend to stomp all over what you are trying to read by repeating everything and chainging the topic all the time16:10
bjfjussi, we developed our own scripts for deailing with the meeting output, the bot doesn't come close to producing the same, so I/we just ignore it16:10
apwquite why it does that i am unsure16:10
jussibjf: and if there are specific issues, bugs would be super. 16:10
apwfor me the issue it about once a year we get a new format out of it16:11
jussibjf: so you dont like the wiki output the bot makes? 16:11
jussiAlanBell: ping16:11
apwwhich is just a pain.  we already had to make something make what we wanted to cope with the old16:11
bjfjussi, no, it's not helpful16:11
jussi(AlanBell is the author fyi)16:11
bjfjussi, i explained this to AlanBell16:12
apwbot, so ... we just continue to do the same and we are bot agnostic16:12
jussistrange. I find it most helpful. 16:12
apwdo you push many tables through it ?16:12
jussiNo...16:13
jussiI guess IRC team meetings are very different to kernel meetings ;)16:13
bjfjussi, the bot grabs the topic changes but then just adds the raw irc log at the end, i don't find that usefull16:13
jussibjf: As I said, Im sure bugs would be helpful - perhaps in the future we can create modes in it so theres a mode that puts the output to a style that works better for teams with this kind of meeting. 16:17
bjfjussi, as i said, i discussed it with AlanBell, he didn't see it as bugs, i'm more than happy to keep doing what i'm doing16:17
apwoften trying to make something do everything is a recipe for disaster16:19
apwbjf, does the new bot at least give us the beginning and end so we can find the poo to process mroe easily ?16:20
bjfapw, i just use the raw log, it's easy enough to find the beginning and end16:21
bjfapw, there is a startmeeting/endmeeting16:21
apwfair enough, was thinking if there was a url it gave you at the end and you could use that to process against that it might have value16:22
bjfapw, maybe, but i'd have to make changes to the script, and the next time they change the bot output i'd have to make more, and so on, and so on, ...16:23
apwfair enough16:23
bjfapw, the next person to run the meeting can decide if they want to do it differently16:24
ogasawaraI doubt anyone is really reading our meeting minutes that closely to even care16:25
bjfjussi, "our way" is completely documented: https://wiki.ubuntu.com/KernelTeam/RunningTheIRCMeeting16:25
bjfogasawara: that is very true16:26
joaopintoHi16:29
joaopintoafter apt-get sourcing the kernel where can I find the list of Ubuntu specific patches ?16:30
jjohansenapw: morning, so what I was pinging you about was CVE-2011-4081, it is marked as needed for hardy but at least on a first glance it looks like the code wasn't introduced until 2.6.3216:30
ubot2jjohansen: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4081)16:30
apwogasawara, that RunningTheIRCMeeting page doesn't seem to have the kteam-tools magic in it, perhaps you could slam it in when you work it out16:30
ogasawaraapw: yep, will do16:31
apwjoaopinto, the ubuntu specific patches are all directly applied in the version you get from apt-get source16:31
joaopintoah ok :\16:31
jjohansenhave you managed to fully script the meeting now :)16:31
apwjoaopinto, if you want the raw patches they are in the our public git trees16:31
apwjoaopinto, every upload has a corresponding tag in those repositories to allow you to find the exact source16:32
joaopintoI have checked the source, just wanted to be sure the patch was not applied somehow during the build process16:32
apwother than on hardy there are no patches applied at build time16:32
apwjjohansen, you should be able to mark hardy 'not-affected' then and my bot will trust you16:33
apwjjohansen, in theory if the other end was working changing it to Invalid in the bug would be sufficient16:33
joaopintothere is no patch included for bug 843431 yet :\16:33
ubot2Launchpad bug 843431 in linux "Logitech camera microphone does not work / makes "chipmunk" sound" [Medium,Triaged] https://launchpad.net/bugs/84343116:33
apwjjohansen, propogating to UCT as not-affected and triggering my ignoreing it16:33
apwjoaopinto, is it marked Fix Released ?16:34
joaopintono, actually there are many bugs related to this issue, with different status and progresses16:34
jjohansenapw: okay, so just fix it in uct, or do I need to mark invalid in the bug too16:34
apwjoaopinto, indeed from the bug it is not clear that anyone has a fix for it even16:34
joaopintohttp://pkgbuild.com/~heftig/linux-zen/usb-add-reset-resume-quirk-for-several-webcams.patch16:35
joaopintohttps://build.opensuse.org/package/view_file?file=usb-add-quirk-for-logitech-webcams.patch&package=linux&project=home%3Agrayden&srcmd5=ac65d19a58e7dbdcd8a328e124aac0b516:35
joaopintowell, someone is applying patches for it :)16:35
joaopintoI have one affected webcam, whose device id is not listed on that specific patch, I am testing it now16:36
bjfjoaopinto, it helps to know which version you are talking about16:37
joaopintobjf, version for ?16:37
apwjoaopinto, ok that patch seem to have _just_ hit mainline in v3.2-rc116:37
bjfjoaopinto, also, we get most of these cinds of patches from upstream stable releases16:37
joaopintoyeah, was checking http://www.spinics.net/lists/stable-commits/msg13878.html16:37
apwjoaopinto, and it is marked for stable so we should see it for older releases soon enough via there16:38
bjfjoaopinto, kernel version or hardy/lucid/maverick/natty/oneiric16:38
joaopintoI don't remember when the problem was introduced, it's present on oneiric16:38
bjfjoaopinto, that's all i wanted to know, what kernel you were trying to build (didn't see it in the scroll back)16:39
apwjoaopinto, ok added the useful bits of that to the bottom of the bug16:40
joaopintoapw, where can I check the v3.2-rc1 quirk patch ? (want to to check for my device id)16:40
apwit is 2394d67e446bf616a0885167d5f0d397bdacfdfc in linus' tree16:41
apwjoaopinto, ok that patch is sitting in gregs queue for 3.0 and 3.116:42
apwso we should get it in oneiric in the next weeks16:43
joaopintook, QuickCam E 3500 not there, I am going to test for a few more days to be sure that it fixed, once I am sure, how should I proceed to ask for a device id to be added to the list ?16:43
apwthe most direct way is to send a patch up to mainline and mark it for stable handling16:43
joaopinto(the issue is random, I can't reliably determine that the fix is working)16:43
apwif that too scarey you can send a patch to the ubuntu kernel list and we can help16:44
joaopintowell, I am an end-user, whatever is easier for me :)16:44
joaopintoI will email the ubuntu kernel list with the bug report link16:45
AlanBellbjf: if it doesn't work for a team then that is a bug16:45
joaopintotks for your time16:46
joaopintothis bug is present since the last LTS http://www.techytalk.info/logitech-e3500-webcam-and-cannot-set-freq-16000-to-ep-0x86/ :\16:49
* ppisati bails out for a bit...16:59
=== chrisccoulson is now known as chrisccoulson_
=== chrisccoulson_ is now known as chrisccoulson
bjfogasawara, we have a "bugs with patches" report somewhere don't we? or do we just do a lp advanced search ?17:26
ogasawarabjf: lp advanced search17:26
bjfogasawara: ack17:26
smbhttps://bugs.launchpad.net/ubuntu/+source/linux/+patches17:26
ogasawarabjf: although I had a pretty graph of it somewhere17:26
bjfsmb: thanks17:27
* bjf wonders if "patch attached" should be displayed on our custom reports17:29
htorque_hi all! is bugzilla.kernel.org down for you (or still not up after the security breach)? i'm wondering if it's known that intel wireless (ultimate-n 6300) is not working with 3.2-rc1 (just tried the mainline ppa yet).18:00
bjfhtorque_: bugzilla.kernel.org is still down18:20
htorque_bjf: thanks!18:22
* tgardner -> lunch19:01
cwillu_at_work32bit mainline ppa builds?19:50
cwillu_at_work(broken until the build tools are updated for precise?  something else?)19:51
undriedseaHey Everyone,21:48
undriedseaI am having a problem accessing /proc/<pid>/mem range after mprotect has made it readable. It almost seems the procfs driver is not aware of the updated permissions. Any ideas or hints would be great!21:48
undriedsea    1. Process A ptrace ATTACHs to process B21:48
undriedsea    2. Process A cannot access of a given range in process Bs /proc/<pid>/mem due to the associated mapping in /proc/<pid>/maps being non-readable21:48
undriedsea    3. Process A requests process B use mprotect to mark given mapping as readable (mprotect returns success)21:48
undriedsea    4. Process A now should be able to read the range in /proc/<pid>/mem but can only read part of the range...21:48
undriedseaDetails: http://codepad.org/DMItNdYa21:48
undriedseaDoes anyone know who is the maintainer of the part of the kernel that container the mprotect systemcall?22:23
SomedudeI get this when trying to turn on VT-d. (Intel VT-d tech enabled), intel_iommu=on(!): Your BIOS is broken; DMAR reported at address fed90000 returns all ones23:26
SomedudeThe BIOS is up to date, so what can exactly cause this error/warning?23:26
Kanohi, is there a reason why the generic target is dropped for 32 bit?23:37
Kanoolder pentium m do not boot with pae enabled23:37
Kanoand some other older cpus23:37
Sarvatthttp://www.linux-archive.org/ubuntu-kernel-team/596063-3-2-rc1-rebase-review.html23:41
Sarvattgeode and pentium-m yeah23:41
SomedudeSarvatt: any ideas on my one?23:42
SarvattSomedude: you literally have a buggy bios, its not exactly uncommon or anything, VT-d is all kinds of pain23:42
Kanothere are lots of pple with that hardware out there23:42
Sarvattdoes it fall back to swiotlb gracefully?23:42
Sarvattif not you can boot with intel_iommu=off to work around it23:43
Somedudehow do I check?23:43
Sarvattdmesg | grep SWIOTLB will tell you23:43
SomedudeI need it for directed I/O, that's a bit of the pain23:43
Somedudeyes23:44
Somedudeit does23:44
Somedudewhat to do to work around this problem?23:44
SomedudeSarvatt: can I get Directed I/O with swiotlb too?23:45
SomedudeI need to put an PCI card to an KVM VM23:46
SarvattSomedude: honestly I have no clue, I imagine you can though23:46
Sarvattthere was a bug awhile back where it would completely turn off iommu support if you got that error but thats fixed now apparently23:47
SomedudeSarvatt: this one you mean? http://freecode.com/articles/red-hat-updated-kernel-packages-fix-multiple-security-issues-1623:48
Somedude588638 - [abrt] crash in kernel: Your BIOS is broken; DMAR reported at address fed90000 returns all ones!23:48
SomedudeI need to contact the supplier of the motherboard and ask them for a fixed BIOS, I guess?23:49
Sarvattyeah sounds like what google pulled up when I searched for it, you might be able to get more info there :) https://bugzilla.redhat.com/show_bug.cgi?id=52480823:49
ubot2bugzilla.redhat.com bug 524808 in kernel "swiotlb should be enabled when VT-d setup fails" [High,Closed: errata]23:50
Sarvattyeah but honestly don't expect that would happen unless its really new (then theres probably still no chance..), OEMs usually just ship crap out the door and give up on it :)23:51
bjfKano, it was discussed at uds and the decision was made there, feel free to post a question to the ubuntu kernel team mailing list23:53
SarvattKano: maybe send a mail to kernel-team@lists.ubuntu.com discussing it23:53
Sarvattbjf beat me to it23:53
bjfheh23:53
KanoSarvatt: ?23:53
Sarvattregarding the dropping support for pentium m23:53
SomedudeSarvatt: I have a contact by ASUS Holland, I will tickle him until he provides me a new BIOS23:55
Somedude*A working one, that is23:55
* Somedude yawns23:58
* Somedude -> bed23:59
Somedude'night all23:59

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