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

apwNg, we were missing some modules i believe in the older kernels whcih would have affected installation, try a daily around now, or beta-1 next week and see if its there09:10
apwRAOF, morning09:11
apwsmb, i see stable is going mad:09:11
apw  144 queue-2.6.32/series09:11
apw  122 queue-2.6.33/series09:11
smbapw, Yeah, I am anciously looking forward to look over it09:11
smbapw, A lot of things all over the place on a first glance09:12
apwsmb, i see those kvm patches are in there09:12
apwsmb, or perhaps some of them, a few kvm patches anyhow09:13
smbapw, Not all09:13
smbRight09:13
smbNot the breaky one09:13
smbBut this one has been fixed too09:13
apwoh yeah you must tell me about that, what the issue was, when you arn't busy09:14
smbapw, Oh, just grab a coffee 09:15
smb:)09:15
apwRAOF, so whats your feeling on our drm backport?  are we seeing generally better or the same reporting?09:20
RAOFapw: It's superb for nouveau.09:33
RAOFI don't think it's any worse than before :)09:34
apwRAOF, that is good input, thanks09:35
=== _ruben_ is now known as _ruben
Keybukhuh14:21
KeybukI/O has crept to a crawl here14:21
Keybukdpkg is trying to unpack the linux kernel deb14:21
Keybukand it's taken over an hour so far14:21
=== sconklin-gone is now known as sconklin
tgardnerKeybuk, this is a bad thing14:22
chrisccoulsonKeybuk, i've noticed the same thing while doing some builds on my machine this morning14:23
chrisccoulsonunpacking any deb at the moment is taking forever....14:23
chrisccoulsoni thought it might just be me though14:23
tgardnerI've had the opposite experience. I think Lucid is much better at load leveling then Karmic.14:24
Keybuktgardner: this is a new bug14:24
Keybukfirst time I've ever seen it on lucid, and with 2.6.32-1614:24
Keybuksorry, this is the second time I've seen it14:24
Keybukbut both have been with -1614:24
tgardnerKeybuk, I sure don't see anything since -15 that have affected the I/O path14:25
Keybuktgardner: it definitely isn't the scheduler14:26
tgardnerah, unless 'sched: Fix SMT scheduler regression...'14:26
KeybukI/O scheduler anyway14:26
Keybukcause I tried changing that to noop14:26
tgardnerduo-core? try htop to see whats busy?14:27
apwKeybuk, on -16 and not on -15 ?14:27
Keybukdon't have htop14:27
Keybukapw: I didn't see it on -1514:28
tgardnerI've been doing -j8 builds while listening to tunes and surfing.14:28
Keybukbut I didn't have -15 installed for long14:28
Keybuktgardner: it seems to be writing to disk that gets incrementally slower?14:28
* apw has been running -16 for some days longer than has been uploaded and not seen that14:28
tgardnerbut an hour? thats ridiculous14:28
tgardneris it actually doing anything?14:29
Keybukyes14:29
Keybukwriting 4096 bytes at a time14:29
Keybukabout one write a second14:29
apwKeybuk, what does top say we are doing14:30
tgardnercan you write any other files whilst this is going on?14:30
Keybukapw: top just says dpkg14:30
Keybukin fact, top thinks dpkg is hardly using any CPU because it's entirely syscall14:30
Keybuktgardner: yes, other writes seem fine14:30
apwpercentage idle/wait etc ?14:30
Keybukapw: dpkg appears always in D state14:31
apwwell -15 -> -16 had drm33, apparmor update, and that SMT update14:32
apwdrm sounds unlikely, apparmor is only open stuff as far as i know14:32
chrisccoulsonKeybuk - i'm only noticing this issue with dpkg, and I'm also running karmic's kernel and still have the issue14:32
Keybukhuh14:32
Keybukright, that just finished14:33
tgardnerapw, SMT update? could be a semantic change14:33
Keybukapt started a new dpkg run14:33
Keybukand that dpkg is running just fine14:33
apwand the SMT update is supposed to be for core to core movment14:33
* apw wonders about what chrisccoulson just said14:33
tgardnerapw, which is why I asked if Keybuk has a duo-core14:33
apwif its on karmic its unliekly a kernel issue me thinks14:33
chrisccoulsonand this dpkg change (37 hours ago) might be a clue:14:33
chrisccoulsonCall fsync(2) after writing files on disk, to get the atomicity14:33
chrisccoulson      guarantees when doing rename(2). Based on a patch by Jean-Baptiste      Lallement <jeanbaptiste.lallement@gmail.com>14:33
Keybuktgardner: two dual-core Althon 64s14:33
apwKeybuk, so he could be affected ...14:34
Keybukchrisccoulson: this is slowness in writes alone - within single files :-/14:34
apwtgardner, would an awoken but not picked up runnable show as D though14:34
tgardneruh, fiik14:35
apwchrisccoulson, can you test the same operation14:35
apwKeybuk, what op you doing exactly ... so i can try here14:35
tgardnersmb is knowledgeable 14:35
apwKeybuk, and what version of kernel and dpkg do you have14:35
Keybukapw: dist-upgrade from wednesday to today14:35
gnarltgardner, huh? what makes you think?14:35
Keybukapw: don't know exact versions, because I'm mid upgrade :p14:36
apwKeybuk, so -16.25 kernel14:36
tgardnergnarl, 'cause you've dealt with I/O stuff in the past.14:36
apwand dpkg?14:36
apwKeybuk, what extract command line you using14:36
apwso i am testing the exact same thing14:36
gnarltgardner, Heh, yeah in the past. And block layer. Not much help with filesystems14:37
gnarlBut it sounds strange that only dpkg is slow14:37
Keybuk2010-03-12 13:31:13 upgrade dpkg 1.15.5.6ubuntu1 1.15.5.6ubuntu214:37
Keybuk2010-03-12 13:32:55 upgrade linux-image-2.6.32-16-generic 2.6.32-16.24 2.6.32-16.2514:37
Keybukso both dpkg and linux-image were upgraded in this run14:37
KeybukI must be running 16.2414:37
chrisccoulsonmaybe we have different issues, but dpkg is painfully slow on my machine even with 2.6.3114:38
apwcan you not cat /proc/version_signature for us?14:38
KeybukUbuntu 2.6.32-16.24-generic14:38
Keybukapw: I didn't know about that ;)14:38
apwok so its _not_ the SMT change as that is in .2514:38
Keybukmaybe the SMT change fixes it? :p14:39
apwKeybuk, uname -a also has the same info hidden in it14:39
apwheheh14:39
apwmaybe14:39
tgardnerKeybuk, is it clipping right along now? you said it finished the one deb it was doing.14:39
apwthough what you are doing is mostly singly threaded so i'd doubt it14:39
Keybukyeah it's clipping along just fine now it's done that deb14:40
Keybukapw: ah, no, dpkg usually spreads across two cores when it unpacks14:40
tgardneranything in dmesg indicating disk corruption?14:40
Keybukone core reads the deb, the other writes to disk14:40
Keybuktgardner: first thing I checked, nup14:40
apwKeybuk, and t'is still slow as snot?14:40
Keybukapw: no, is fine now14:41
Keybukwas just that deb14:41
apwwhich deb?14:41
Keybukironically, the kernel image one ;)14:41
apwthats not even that big?14:41
Keybukoh, and kernel headers probably14:41
apwheaders is shit loads of files, an fsync after every single close would be bad performance wise14:41
apwso it would depend what this change in dpkg actually does14:42
Keybukfsync() is supposed to be ok for ext4 no?14:42
Keybukhuh14:43
apwdefine ok.  if i read this description right it does it after every rename14:43
Keybukthough saying that14:43
Keybukdpkg was upgraded first14:43
Keybukso that might have been done with new dpkg14:43
apwwhich would likely be after every single file written, write tmp file, rename in14:43
Keybukyeah14:43
Keybukit would be14:43
apwif it does that for small files, kiss your ass goodbye14:43
apwKeybuk, there are 11692 files in a linux-headers file ... an fsync after ever one of those would be ... bad14:44
apwsooo ... need to know where the fsync went14:45
Keybukyes14:45
KeybukI'm thinking you're right14:45
apwnormally if dpkg is updated in an update, that gets applied first before all others right?14:45
gnarlOn every extracted files it seems14:45
gnarlAnd on directories as well14:46
smbhttp://launchpadlibrarian.net/39182845/dpkg_1.15.5.6ubuntu2.debdiff14:46
gnarlapw, ^14:47
apwgnarl, thanks ... Keybuk got the git commit over on #u-d14:47
pgranertgardner: Hey jono tried that rfkill suggestion, no difference15:11
tgardnersaw that.15:12
pgranertgardner: I'd like to try and get to a root cause prior to you taking off next week15:12
pgranertgardner: anything I can do to facilitate that?15:13
tgardnerpgraner, I'm thinking that if an rfkill or 'modprobe -r' and 'modprobe' doesn't fix it, then its likely not a kernel issue.15:13
apwtgardner, looks like they did add an fsync per file in pkg, and they did it for good reasons due to ext4 semantics being at the loose end of whats allowed ... so ... ouch15:14
apwno the kernels fault directly15:14
tgardnerdo we have one of these 5K parts somewhere in a laptop?15:14
tgardnerpgraner, ^^15:14
pgranertgardner: NM issue?15:14
pgranertgardner: not that I know of, we can ask the hw lab 15:14
tgardnerpgraner, possibly, but its kind of the whipping boy for all connection failures.15:14
pgranertgardner: any extra debug info we can get when it does crap out?15:15
tgardnerpgraner, lemme get him to do the modprobe dance thing.15:15
pgranertgardner: ack15:15
cr3apw: I've been trying your suspend_test script in various combinations, one of which I find strange: 1. set acpi wake alarm; 2. run pm-hibernate; 3. pull the power plug out and immediately back in on a laptop without a battery.16:09
cr3apw: oddly, the system doesn't resume after the wake alarm time, but works fine if I leave the power plug alone16:09
tgardnercr3, I doubt there is battery backed RAM on a laptop, 'cause there is already a battery. does this test really make sense?16:13
cr3tgardner: I'm not sure I understand, this is for a hibernation rather than a suspend. does hibernation rely on ram?16:14
tgardnercr3, the ACPI alarm likely does16:15
cr3tgardner: oh! I thought that was a cmos thing, makes sense then16:15
tgardnercr3, CMOS on a standard AT motherboard has a battery. Thats why your BIOS loses its brains if that battery goes dead.16:16
cr3tgardner: but that has a separate battery on laptops, right?16:17
tgardnercr3, I think its likely the external battery in a laptop that serves that function, though I have to wonder why BIOS doesn't get scrambled when you pull the external battery. maybe I'm just all wet.16:19
cr3tgardner: yeah, I was wondering the same thing (regarding pulling the battery, not regarding you being all wet... tmi)16:19
jjohansenlaptop usually have a small battery or capacitor for the CMOS16:30
jjohansenI even have a laptop with a capacitor for the ram that gives me 2 min, to change the external battery during suspend16:31
tgardnerjjohansen, makes sense16:32
apwcr3, you are relying on the EC to keep running without battery or mains, not sure that is reasonable16:40
tgardnerapw, I think that dpkg change is _really_ slowing things down.16:46
apwits particularly painful for large packages like the kernel headers16:46
tgardnerone of my mojo fast serves has been updating for over an hour. Karmic->Lucid usually takes about 20 minutes16:47
apwtgardner, pitti is asking questions in the MIR bug for ti-omap, which need answering before it can continue16:50
tgardnerapw, do you have the bug number handy16:51
tgardner?16:51
tgardnernm, found it16:51
apwnot at the mo, google MIR ti-omap16:51
apwthats how i find it each time16:51
tgardnerapw, responded. I should have looked first thing this morning. I get too dependent on my email filter to send me the right stuff at the right time.16:55
apwtgardner, actually i think i got them to 'no brainer' position.  the general position of armel == 18month support only plus the fact i needs to be in main to get onto a CD ... means that its a slam dunk16:56
tgardnerapw, yeah, its not like they'll cause regressions or interactions with other packages16:57
cndtgardner: is that the normal process for a pre-stable patch?17:12
tgardnercnd, close enough. its all a bit ad-hoc.17:13
cndk17:13
tgardnercnd, it depends on whether smb demands an SRU as well17:14
cndahh17:14
cr3when I boot into the bios of a dell mini 10, the bios seems to indicate I'm not in supervisor mode. is there a way to get into the bios in supervisor mode?17:16
tgardnercr3, whatya mean? Is it passworded?17:17
cr3tgardner: if it's passworded, I can't even find where to enter the password. it allows me to boot into the bios, with f2, but it's just that some features are greyed out with some caption saying that they are only available in "supervisor mode"17:18
tgardnercr3, maybe that equates to manufacturing mode? ask apw as he has one.17:18
apwhrm not sure i've ever notices17:19
* apw reboots to find out17:19
cr3apw: in the boot menu, I see this caption on the right: All items on this menu cannot be modified in use rmode. If any items require changes, please consult your system Supervisor.17:20
apwcr3 do you have a security menu ?17:20
apwif so what is on there 17:21
apwi have 'Supervisor Password is: Clear'17:21
cr3apw: supervisor password is: clear; user password is: set17:21
apwUser password is : clear17:21
apwon mine17:21
apwi think someone has added a password on it17:21
apwnot normal i'd say17:21
cr3crap, but I can't even find how to get prompted for that password, at least I could try "ubuntu" or somesuch17:21
apwthere is a Set User Password just below17:22
apwbut i'd say its not meant to have one17:22
cr3apw: greyed out, not accessible using the arrow keys17:22
apwmine does not17:22
apwi'd say if the supervisor password is clear it'd not need one, but ... hrm17:23
* cr3 considers either flashing the bios or opening up the darn thing to clear the cmos17:23
Keybukapw: OOOOOOH17:32
apwKeybuk, WHEEE17:32
Keybuk<insert Mary Whitehouse Experience Music>17:33
Keybukapw: that was a reaction to your mincore() patch btw17:37
apwKeybuk, i thought it might be.  hopeing you are out from under plymouth enough to test it for me17:37
Keybuknot yet17:38
Keybukbut shortly17:38
claudenhi kernelers22:47
JFohi clauden 22:48
claudenhi JFo22:48
claudeni seem to be digging myself into a hole trying to set up a diskless client with readonly filesystem...22:50

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