/srv/irclogs.ubuntu.com/2011/05/23/#ubuntu-kernel.txt

=== 64MAAJNBW is now known as sunnydrake
=== _LibertyZero is now known as LibertyZero
=== yofel_ is now known as yofel
=== fairuz_ is now known as fairuz
=== cking_ is now known as cking
=== smb` is now known as smb
=== johanbr_ is now known as johanbr
ppisatireboot14:14
* ogasawara back in 2015:42
diwicbjf, latest update for c-o-t-d 2.6.38 seems to have been 2011-05-05 15:43
bjfdiwic, that was the first and only, was waiting feedback15:43
diwicbjf, aha 15:44
bjfdiwic, i can fire off another if desired15:44
diwicbjf, if it's simple, please do15:45
bjfdiwic, will do15:45
=== jdstrand_ is now known as jdstrand
diwicbjf, meanwhile I installed the package and it seems to work fine, so I think you're good to go for enabling daily builds for Natty as well15:53
bjfdiwic, just uploaded a new one, thanks for the feedback, will start doing them automatically15:53
diwicbjf, thanks!15:55
bjfdiwic, added, if you see any issues with it now, don't hesitate to mention it/them15:57
JFobjf, how would I add that kernel call to my collection?16:38
JFoI tried by the URL, but no joy16:38
JFoand I am too stupid just now to figure it out :)16:38
bjfum, one sec16:38
hggdhbjf, sconklin: I do not see any pending karmic kernel to be tested. Am I missing something?16:40
bjfhggdh, looks like someone went ahead and promoted the karmic kernel to updates16:41
bjfskaet, ^16:41
skaetbjf, hggdh,  looks like we have a process failure then.16:41
skaet:P16:41
hggdhwell, we can still go ahead and validate it, just in case16:42
skaethggdh,  please do so.16:42
bjfJFo, did you get some notice about that calendar? i just added you to the share list16:42
skaetI'll take this up with pitti and see if we can figure out what happened.16:42
hggdhk16:43
* JFo looks16:43
JFobjf, looks like it just showed up in my main calendar now. Thank you :)16:43
bjfJFo, np16:44
skaethggdh,  please let me know if there's any problems with it, soonest.   16:44
* apw pops out to get a replacement hdmi cable16:45
bjfogasawara, we going to do a status meeting this week ?16:50
ogasawarabjf: yep, that's the plan16:51
bjfogasawara, always good to have a plan, do we have a list of blueprints we are going to be tracking ?16:52
ogasawarabjf: https://wiki.ubuntu.com/KernelTeam/Specs16:52
bjfogasawara, we're going to want all of them on the agenda or you want me to pick the ones I think are relevant?16:53
ogasawarabjf: I'd only pick out the relevant ones.16:54
bjfogasawara, ack16:54
bjfogasawara, i've updated the meeting agenda, most of the blueprints are for you, let me know if there are others you think should be added17:06
ogasawarabjf: ack17:06
ogasawarabjf: I'm gonna move the one work item from the misc blueprint to the server-reqs blueprint and then we can just drop the misc blueprint from the agenda17:10
bjfogasawara, wfm17:12
* apw notes that plugging and unplugging hdmi outputs on intel leads to crashes :/17:43
jjohansenapw: is that with the latest intel driver?17:46
apwjjohansen, with whatever is latest in natty17:56
apwnow on a .39 kernel shall see if its any better17:56
jjohansenapw: ah there where some hdmi improvements in the latest intel drm tree, not sure what made it into .39 though17:56
apwjjohansen, ok will see how this pans out17:58
JFoogasawara, just saw your response :-)19:06
ogasawaraJFo: pick a time when you want to start your kernel patching and git-fu, I'll put it in my schedule.  not sure it'll require a full hour each week, but we should just start19:11
BenCAny chance that bug #424142 will get fixed in lucid's kernel?19:11
ubot2Launchpad bug 424142 in linux "Address Collision" [Undecided,Confirmed] https://launchpad.net/bugs/42414219:11
BenCI've just had a couple customers get bit by it, upgrading them to maverick kernel fixed it19:11
JFoogasawara, right, my hope is that some of these will taper off and not be needed.19:13
JFojust wanted to get them started and indicate how serious I am about them to everyone :)19:14
BenCI suspect no, since linux-lts-backports-maverick is available19:16
ogasawaraBenC: if it came through the next 2.6.32.y upstream longterm release, it'd get applied to Lucid.  or use the backports kernel.19:19
BenCogasawara: No chance of someone actively searching for the fix? Isn't 2.6.32.y inactive? :)19:21
ogasawaraBenC: I thought 2.6.32.40 just came out, was that the last one?  /me hasn't been following19:22
BenCwait, I didn't realize upstream was maintaining longterm kernels now, so hopefully they do a 2.6.32.y to fix it19:22
bjfBenC, GregKH still maintains .3219:24
sforsheeBenC, ogasawara: looks like the fix was in 2.6.33 (commit 8c8def26) so it just never made its way to stable19:25
BenCRight, I knew it was fixed in 2.6.33, was just hoping for some love in lucid, even if 2.6.32.y isn't getting it upstream19:25
sforsheeI'm just saying that if we wait for it to show up in .32 stable it's never going to happen19:26
BenCThat's exactly what I'm saying :)19:26
bjfsforshee, you want to do an SRU for it?19:27
sforsheebjf, sure, I'll try to get some testing on it first to make sure it really fixes the problem19:28
bjfsforshee, that looks like a reasonable candidate19:28
bjfwfm19:28
bjfsforshee, looks like BenC might be able to help test :-)19:29
BenCCustomers gave me sudo access to the affected machine, so I plan to abuse it as much as possible...19:29
ogasawarahehe19:30
BenCif you get something testable, I'm happy to toss it on there19:30
sforsheeBenC, I'll post a kernel to the bug report shortly, then I'll submit it for SRU as soon as you can get it verified19:30
bjfsforshee, not a rush, just information, if you can get a fix verified soonish, we are prep'ing kernels for the next cadence cycle19:31
sforsheebjf, ack19:31
BenCsforshee: ok, please ping me on here, launchpad traffic doesn't get through my usual filters19:32
sforsheeBenC, will do. If you tell me whether you'll use a 32-bit or 64-bit kernel for testing I'll make sure the one you need is built first.19:33
BenCsforshee: Thanks, 32-bit19:34
BenCsforshee: this patch doesn't affect ABI, correct?19:43
sforsheebjf, would you be so kind as to accept the lucid nomination on bug #424142 ?19:43
ubot2Launchpad bug 424142 in linux "Address Collision" [Undecided,Confirmed] https://launchpad.net/bugs/42414219:43
sforsheeBenC, it shouldn't19:44
BenCif it does, I would need to get the headers to fully test against this module19:44
bjfsforshee, you bet19:44
BenCsforshee, bjf: a huge thanks for the effort on this as well19:44
bjfBenC, np19:44
sforsheeBenC, I'll give you the headers, but as it only changes a function body it shouldn't affect the abi at all19:44
bjfsforshee, done19:45
sforsheebjf, thanks19:45
BenCsforshee: I could have approved it for you :)19:45
sforsheeBenC, 32-bit test build is posted at http://people.canonical.com/~sforshee/lp424142/2.6.32-32.62~lp424142v201105231936/19:53
hertonbjf: can you approve nominations for bug 78714519:54
ubot2Launchpad bug 787145 in linux-ti-omap4 "CVE-2011-1494" [Undecided,New] https://launchpad.net/bugs/78714519:54
bjfherton, working it19:55
bjfherton, done19:56
hertonthanks bjf19:56
bjfnp19:56
BenCsforshee: ok, give me 30 minutes20:26
BenCsforshee: not stalling...this box doesn't boot unattended so I'm just waiting for some one to kick it21:03
BenCsforshee: I've at least smoke tested here locally, but not on a box that exhibits the problem21:03
sforsheeBenC, cool, I've got everything ready to go for once we know it fixes the problem21:07
BenCsforshee: confirmed that it fixes the issue, and commented on the bug report22:22
shankara hi all, i'm having a weird issue trying to reboot with linux 2.6.38 (x86_64), ubuntu LTS 10.04, this is on atom D525 - dual core atom22:26
shankarasystem hangs on restart with: "will now restart" and then "[<some varying number>] Restarting system"22:26
shankara i've tried recompiling a variety of kernels22:27
shankarai've even compiled specifically for the atom, not using generic22:27
shankarasame issue. but soft halt works fine22:27
shankarais this a known kernel support issue with atom dual core cpus ?22:27
BenCshankara: It sounds like an issue with the kernel you are compiling, like a panic, maybe related to your root filesystem22:28
BenCSounds suspiciously like you are just compiling the kernel wrong22:28
BenCshankara: And specifically, it sounds like an issue you just have to figure out through more generic channels #kernelnewbies perhaps?) since it isn't an Ubuntu issue22:29
shankaraBenC: i found this on the generic default kernel that  came with lts 10.0.422:29
BenCYou said it was 2.6.3822:29
shankaraafter a couple of binary kernels, i decided to compile my own22:29
shankarasame issue22:29
bjfshankara, have your tried our lts-backport kernel?22:29
shankarathat's the most recent kernel i tested22:29
shankarabjf: not yet, maybe i should22:30
shankarai only  resorted to source compiles after all the binary kernels in the apt repo gave me the same  soft reboot issue22:30
BenCshankara: Booting with single (so without quiet) would be more helpful22:31
BenCThe reason for the panic might give some clues to the real problem22:31
shankaraBenC: i'm inclined to the some clues to the real problem might provide a reason for the panic22:32
shankaraactually ... i wouldn't say it's a panic22:32
shankarathere's no "ooops"22:32
BenCI would say it is a panic22:32
shankarait jsut doesn't actually restart the hardware, just promises to22:32
BenCThe "will not restart" message comes right after a panic22:32
BenCerr "will now restart"22:32
BenCshankara: If it fails to exec /sbin/init or similar, it will panic22:33
BenCpanic != BUG22:33
shankaraBenc: yes, sorry: "Will now restart"22:33
BenCit means "oh crap, I don't know what to do next"22:33
shankaraBenC: it actually get's past stopping all system services, unmounting all filesystems ... then it jsut doesn't , so it seems init runs it's full course22:34
shankarasorry "then it just doesn't restart the hardware"22:34
BenCshankara: Do you mean it will actually boot, just not reboot?22:34
shankarait'll boot, it'll even halt. Just it wil not soft restart22:35
shankaractrl-alt-delete has the same effect - no restart22:35
BenCOh, I misread "trying to reboot with.." as "trying to reboot into..."22:35
BenCshankara: I have some tips for this problem...22:35
shankarayeah, it's a weird one22:36
shankaramost people are trying to boot their boxes, I'm trying the opposite22:36
shankararestarting is critical for remote support on appliances22:36
BenCshankara: Try adding reboot=bios to your kernel command line22:37
shankaraBenC: let me try that and get back to you 22:37
BenCshankara: reboot=acpi might be worth trying too22:37
shankaraack.22:37
sforsheeBenC, just sent SRU patch to kernel-team list, thanks for testing22:38
BenCsforshee: np, thank you for taking on the logistics to get it in an SRU22:40
broderis there anything i can do to accelerate getting help with bug 784335? i don't really have any kernel debugging-fu, but the machine in question isn't my primary machine and doesn't have any data on it, so i can re-install or re-configure it 10 ways to sunday if that helps22:43
ubot2Launchpad bug 784335 in linux "Heavy network utilization with r8169 leads to kernel panic" [Undecided,Confirmed] https://launchpad.net/bugs/78433522:43
BenCbroder: I would argue that r8169 is a horrid driver and would suggest you'd have better luck wedging an e1000 card in there :)22:45
BenCbut I'm not the official spokesperson, so I digress22:45
BenCbroder: a pic of the on-screen panic would help22:47
broderBenC: is the core dump not good enough?22:47
BenCbroder: I'd have to set aside time to dig into that, perhaps later tonight22:49
broderif i were to go and play the role of the apport retracer, would that get the bug more attention?22:55
shankaraBenC! you're a genius! reboot=acpi worked :D22:59
shankarathanks!22:59
TheSevenas some people seem to be awake currently, I'd like to re-ask my question from like a week ago: http://paste.ubuntu.com/612064/23:02
TheSevenany hints?23:02
JFoTheSeven, have you filed a bug?23:04
TheSevenno, as i don't have a clue what to file it against23:06
TheSeventhis kinda seems to be an OMAP or ARM specific problem23:06
TheSevenbut it doesn't seem like the OMAP guys would know what's the cause for it23:07
TheSevenso i'd like to check if there are any general hints for situations like this (some tunables maybe?)23:08
JFoso you would file it against linux which encompasses all of them and then I would go about determining if it was specific to one of them.23:08
JFovery simple process too... from a term run 'ubuntu-bug linux'23:09
TheSeventhe maximum throughput being at a sub-sector block size and the fact that it happens both with USB and SD makes me think that this can't really be coming from the MMC/USB controller, but must be coming from some generic I/O code23:09
JFopresto! bug report! :-) How is that for the soul of ease? :)23:09
JFovery possible23:09
JFobut I would like to see the logging we collect from the bug report tool to dig a bit deeper.23:10
JFoso when it is behaving thus, if you could file that bug it would be most helpful23:10
TheSevenJFo: https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/78724623:20
ubot2Launchpad bug 787246 in linux-ti-omap4 "Slow SD card and USB HDD I/O for block sizes bigger than a couple of bytes" [Undecided,New]23:20
broderBenC: does http://pastebin.ubuntu.com/612078/ look like it has the information you wanted?23:22
broderi'm not super-familiar with digging around in vmcores23:22
hggdhsmb: there?23:41
jjohansenhggdh: its pretty late in the day for smb to be here (00:47) for him23:47
hggdhjjohansen: yeah, I had just remembered he is UTC+1 or 2...23:48
hggdhjjohansen: perhaps you -- I am unable to boot the curretn maverick proposed on AWS, i386/m1.small23:48
jjohansenugh, I can have a look23:49
hggdhjjohansen: what do you need?23:51
jjohansenhggdh: hrmm, nothing just yet.  I will boot an m1.small and install a proposed kernel and try to duplicate, and go from there23:52
jjohansenhggdh: actually, which region/zone, and even machine type if you can get that info23:53
hggdhjjohansen: OK. What I did -- what I always do --: I booted the current AWS Maverick, then run a dist-upgrade with -proposed enabled23:53
jjohansenhggdh: right, I think I will be a little more selective and just pull the kernel23:53
hggdhjjohansen: ec2-run-instances ami-b21de3db --instance-type m1.small --region us-east-123:54

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