/srv/irclogs.ubuntu.com/2010/06/14/#ubuntu-kernel.txt

jamincI'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?00:07
ubot2Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/53809700:07
ubot2Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/59223900:07
Sarvattany reason the i386 kernels are using CONFIG_M586=y in maverick that went to i686 by default?00:40
ScottLdoes anyone know why the -preempt kernel keeps building uninstallable binaries?02:42
ScottLi think this is keeping the ISo testing from building a proper ubuntu studio ISO02:43
jamincI'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?02:54
ubot2Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/53809702:54
ubot2Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/59223902:54
* abogani2 waves07:38
abogani2apw, ogasawara: Are you around?07:52
MTecknologyabogani2: hi08:00
abogani2MTecknology: hi :-)08:18
* apw yawns08:36
ikepanhcgood morning .eu08:37
apwmorning08:37
smbMorning .*08:37
ckingmorning .* too08:38
ikepanhcThere is CONFIG_PREVENT_FIRMWARE_BUILD in driver/Kconfig, but seems no code use it, anyone knows how it works?08:39
ikepanhcs/driver/drivers08:40
ikepanhceh drivers/base/Kconfig08:40
apwikepanhc, isn't that an intermederary configuration option, one that gets selected08:40
smbcooloney, Heya Brian. Is Eric around today?08:41
ikepanhcoh, I see them08:41
cooloneyapw: smb cking morning guys08:42
abogani2apw: There is a bug into maverick-meta package: -preempt is still there. Could you remove it, please?08:42
* apw waves generally08:42
smbcooloney, moin08:42
cooloneysmb: he seems to be dropped.08:43
cooloneysmb anything urgent?08:43
cooloneyi can call him08:43
smbcooloney, Meh, semi-urgent. Not worth a coll I think. I write him an email08:43
abogani2smb: I suppose than you can remove the linux-rt signed directory in your home at Zinc. Thanks for all!08:44
apwabogani2, hrm, i'll get leann to drop it from the next upload, wonder how that got missed08:44
abogani2apw: Thanks!08:44
smbabogani2, I am lazy. So it gets removed the next time I add something new. :) You're welcome08:44
abogani2smb: :)08:45
abogani2apw: Only for keep you updated: the last lowlatency test build is done at https://launchpad.net/~abogani/+archive/broken/+packages08:45
ikepanhcapw: about the lucid ABI number, is it good to use a greater number such as 1000+ for oem kernel branch?08:51
ikepanhcsorry forget to trace this issue after last time I asked you08:51
ikepanhcoh, and I asked for several oem guys, seems no oem project using karmic netbook branch08:53
apwikepanhc, ABI number> it depends if they are going to be new branches or merge into the existing ones09:00
apwikepanhc, karmic netbook> seems this branch is dead then, will talk to smb about its fate09:00
apwikepanhc, so you do not have any use for the branch any more ?09:02
smbapw, ikepanhc If noboday is using that, then I'd vote for removal09:02
* apw concurs with smb, one less branch to fix :)09:02
ikepanhcapw: yeah, that's the problem, if using a greater ABI number on a branch, it will let the branch can not be merged - build server will reject uploading a smaller ABI number09:03
smbNot that I never did much with that09:03
* ikepanhc ponders for removal09:06
ericm|ubuntusmb, the merge looks good, I'm doing a building and will have a smoke test on dove hw, get back to you soon09:13
smbericm|ubuntu, Ok, great. I hold back and upload as soon as you give your ok09:14
* ericm|ubuntu feels sick about the error message: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.09:16
ericm|ubuntuanyone knows why 'fakeroot echo $LD_PRELOAD' doesn't show any clue?09:17
maxbBecause your shell expanded $LD_PRELOAD before fakeroot was invoked09:17
smbIf you were on i386 it might be a 32/64bit issue...09:18
ericm|ubuntumaxb, ah right09:18
ericm|ubuntusmb, I'm on amd64, ia32lib installed though09:18
ericm|ubuntumaxb, let me try encapsulate that into a shell script then09:18
ericm|ubuntunow it shows: LD_PRELOAD=libfakeroot-sysv.so09:19
jk-ericm|ubuntu: do you have libfakeroot for 32-bit?09:21
ericm|ubuntujk, nope09:22
jk-and are you trying to run a 32-bit binary ?09:22
ericm|ubuntujk-, that could possibly be the cause09:22
ericm|ubuntuit's a codesourcery toolchain and it should be 32-bit binary09:22
apwikepanhc, smb, karmic netbook> i propose we tag the tip of the branch netbook-mothball and remove the branch ... then we can get it back if we need to09:23
ericm|ubuntujk-, you are right: file ~/bin/arm-2010q1/bin/arm-none-linux-gnueabi-gcc09:23
ericm|ubuntu/home/ycmiao/bin/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, stripped09:23
apwericm|ubuntu, i run those in a 32bit chroot09:23
ikepanhcapw: that's a good idea09:23
ikepanhcapw: +1 from me09:23
apwsmb, ?09:23
smbapw, ikepanhc Sonds like a good middle way between complete removal and carrying it around09:23
smbapw, +109:23
* apw takes the action ...09:23
ericm|ubuntuapw, you are right09:24
* ericm|ubuntu sees apw happily removing a branch09:24
* smb finds a Lucid ABI 23 in the meta repo done by apw... I guess not uploaded, yet?09:37
apwsmb, right, its an UNRELEASED one right?09:40
apwthats there to trigger pre-proposed to pick up the abi change09:40
smbYep it is.09:40
smbI am just finalizing it09:40
smbJust a bit confused why the -22 is marked proposed too09:41
apwdid i do -22 ?  i don't recall touching that09:41
smbHm, looking at the archive, it looks ok though09:42
smbMaybe the day0 update09:42
apwyeah i wondered about that, though i thought that was not a bumper09:43
smbI just got confused because I did not do an ABI bump since release. But maybe we did and its just half erased from memory. :-P09:43
smbWe should be in sync now09:43
apwok cool09:43
ericm|ubuntusmb, it works all right09:44
smbericm|ubuntu, Ok, thanks for the verification, I will upload in a few minutes09:44
ericm|ubuntusmb, thanks for the work - really appreciated09:44
smbericm|ubuntu, It was partially the confusion about the whitespace. But I am glad it is good now09:45
ericm|ubuntusmb, yeah - their patches s*ck but I was not doing good to educate09:46
=== artnay_ is now known as artnay
=== smb is now known as smb-afk
jamincI'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?13:31
ubot2Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/53809713:31
ubot2Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/59223913:31
pgranerjaminc: you can use https://bugs.launchpad.net/ubuntu/+source/linux/+filebug to file the bug and then use apport-collect <bug number> to attach all the needed debug info13:34
jamincisn't that likely to suffer from the same issue with the automated upload?13:36
pgranerjaminc: don't know, but its worth a try, if it fails then you can upload everything manually via the web interface13:37
* apw lunches13:39
TeTeTsmb: I escalated the x201 WWAN module problem, maybe it will end in your lap13:49
jamincpgraner, can't seem to attach a file to bug report after filing it... keep getting "Cannot upload empty file." even after selecting the file and seeing it listed in the selection box13:49
smbTeTeT, Thanks for the heads up. I will see... :)13:52
=== zul_ is now known as zul
tgardnersmb, Is Lucid -meta stuck in the queue?13:55
pgranerjaminc: whats the bug number?14:02
jaminc593650, uploading the file now, forgot that the crash dumps are only accessible by root14:02
jamincany tags that are needed since the crash dump is being uploaded manually?14:03
pgranerjaminc: yea one sec14:03
pgranerjaminc: https://wiki.ubuntu.com/Kernel/Tagging look at the last table and pick the appropriate ones14:04
pgranerjaminc: I'll get out triager to get it into the right state when he comes online14:04
jamincthought there were tags to indicate a need for a retrace and such?14:05
jamincpgraner, upload got to 100%, page started to reload and then gave me: "Sorry, there was a problem connecting to the Launchpad server."14:14
pgranerjaminc: what was the name of that file? Several are on the report now14:17
jamincthose are the ones from apport-bug, the manual upload was the kernel crash dump: linux-image-2.6.32-22-generic.0.crash 14:18
apwuploading crash dumps to launchpad ... just how big is that thing?14:20
MTecknologyapw: that's a really early lunch... I wasn't even to work yet14:20
apwMTecknology, depends on where the sun is in the sky in my part of the world :)14:21
jamincthis one is smallish 309M, others are quite large... have had one up to 2.5G14:21
apwjaminc, i suspect that the upload is timing out14:21
pgranerjaminc: use apport-collect 593650 <full path to the crash file>         and see if that will get it to go14:21
MTecknologyapw: I live in the US - therefor you all abide by my time.14:22
pgranerapw: launchpad is having issues today, I'm getting timeouts just refreshing pages14:22
jpdsjaminc: I think bug #592239 is a dup of bug #585269.14:22
apwMTecknology, luckily we have learned how to ignore .us14:22
ubot2Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/59223914:22
ubot2Launchpad bug 585269 in apport "apport-retrace shouldn't expect a Package field for kernel crashes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/58526914:22
MTecknologyapw: :P14:22
pgranerjpds: we don't care about dupes, we need a new report on all kernel bugs14:22
jamincpgraner, no, he's talking about why I can't locally retrace it... different item14:23
pgranerjaminc: yea I saw that after the bug desc popped up14:24
jamincpgraner, apport-collect 593650 /var/crash/linux-image-2.6.32-22-generic.0.crash 14:24
jamincUsage: apport-collect <report number>14:24
pgranerjaminc: then it I don't know14:25
apwjaminc, i would try attaching it using the attach file option, i suspect it will puke again at which point i suspect your only choiuce is to make it available somewhere else14:35
jamincapw, already tried using the attach file option that's what resulted in the "Sorry, there was a problem connecting to the Launchpad server."14:36
apwjaminc, i suspect they never ever considered files that big being attached and its timing out in the middle14:36
jamincthe problem is that the crash needs a retrace, I'd happily do the retrace myself (have built and installed the debug version of the kernel), just not sure how to do it since apport-retrace bombs14:37
ograhmm, did we get a new defconfig for omap with the last upload ? i suddenly get weird error messages with the latest omap3 binary14:38
ograi cant relly see any valid stuff in the uploaded changelogs 14:39
jamincwould the kernel crash dump contain potentially sensitive information?14:40
amitkyes14:43
amitkit dumps your entire physical memory14:43
amitkso potentially decrypted keys14:43
jamincthen hosting it publicly isn't much of an option.  any other way I can get a useful trace from it?14:45
amitkjaminc: do the analysis yourself?14:47
jamincI'm offering to... however all the tools referred to by the documents I've found fail... so I'm asking for guidance...14:48
jaminchttps://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe refers to using apport-retrace, however as bugs #592239 and #585269 illustrate, that's not possible currently even with self built debug kernels installed14:49
ubot2Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (dup-of: 585269)" [Undecided,New] https://launchpad.net/bugs/59223914:49
ubot2Launchpad bug 585269 in apport "apport-retrace shouldn't expect a Package field for kernel crashes (affects: 2) (dups: 1) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/58526914:49
cwillu_at_workjaminc, should be easy to hack up apport-retrace to not try to include it, it's just a python script14:50
jamincseems the upload issue is a very old bug #9582214:56
ubot2Launchpad bug 95822 in apport (Ubuntu) (and 1 other project) "Malone connection generates an "Internal Server Error" on large file attachments (affects: 6) (dups: 6) (heat: 84)" [Medium,Confirmed] https://launchpad.net/bugs/9582214:56
=== rsalveti_ is now known as rsalveti
=== sconklin-gone is now known as sconklin
jaminccwillu_at_work, by george you were right... a single line change to the python script and a small change to how apport-retrace was called and I appear to have a viable trace15:10
ograhmm, the omap3 error seems to come from a patch that enables IO-CHAIN wakeups 15:18
ogra"Wake up daisy chain activation failed."15:18
ograi dont see changes related to that in the changelog ... do we not include everything in the debian/changelog file ?15:19
ogra(i mean upstream commits)15:22
=== ericm|ubuntu is now known as ericm-Zzz
ograamitk, ^^^ any idea ? 15:31
* ogra suspects http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18213.html entered mainline recently or something like that15:31
ograin any case it makes the beagle kernel unbootable atm15:31
amitkogra: which omap error?15:32
ogra"Wake up daisy chain activation failed."15:32
ograover and over15:33
amitklucid or maverick?15:33
ogramaverick indeed :)15:33
amitkogra: this is with new kernel?15:34
ograi used 2.6.34 for testing until today 15:34
ograthis error shows up with 2.6.25-2.215:34
ograerr15:34
ogra-2.315:34
ograso something changed between .34 and .3515:35
amitk_lots_ of omap changes went in then15:35
ograwhere are the changelogs for that in our package ? 15:35
ograwe should somehow generate an upstream changelog that goes into the package docs 15:36
manjoJFo, you feeling better ? are we doing the bug meeting today?15:39
JFomanjo, not much. I think something I ate in SC didn't agree with me. We will be having the bug chat15:40
tgardnerogra, we do not generate a changelog of that size since it would have tens of thousands of changes, not a manageable amount IMHO.15:40
ograhmm, i thought we used to have such a feature once15:40
manjoJFo, sorry to hear that... will talk to you at the meeting 15:40
JFok :)15:40
ograin the package changelog actually15:40
amitkogra: the entire upstream changelog isn't in debian/changelog, only a pointer to what tag we rebased to. 15:41
ograit would help a lot during development 15:41
tgardnerogra, we do for minor updates, but going from 2.6.34 to 2.6.35 is a big jump15:41
amitkogra: you wouldn't know where to even look if the entire 2.6.34..35 changelog was put into debian/changelog15:41
ograyeah, i understand ...15:41
ograwell, i could gep for buzzwords15:42
ograi.e. in the above case i would expect something like IO-CHAIN to show up in a changelog entry15:42
amitkogra: git log | grep buzzword :-p15:42
ograamitk, then i need to pull the git tree 15:42
ograhaving a changelog file would be a lot more convenient for a non kernel developer 15:43
ograbut if its to big then its indeed no option15:43
tgardnerogra, 9479 commits from 2.6.34 to 2.6.35-rc315:44
ograyeah, thats surely a lot15:45
amitkogra: I just checked, even debian doesn't do something like that. Just a one-liner saying "update from tag1 to tag2"15:47
ograamitk, yeah, seems i took wrong that changes sometimes show up and sometimes they dont 15:48
ograhttp://www.gossamer-threads.com/lists/linux/kernel/1228828 aha15:51
ograMike Chan (2): 15:51
ograOMAP3: PM: Enable IO / IO-CHAIN wakeups for PER 15:51
amitkmpoirier_: are you looking at bug 566645?15:54
ubot2Launchpad bug 566645 in linux-ti-omap (Ubuntu Maverick) (and 2 other projects) "OTG configuration is broken on omap kernel (affects: 2) (heat: 70)" [High,Confirmed] https://launchpad.net/bugs/56664515:54
mpoirier_yes and no.15:54
mpoirier_discovered a problem with SD card.15:54
mpoirier_very tedious.15:55
mpoirier_took me a week to find it.15:55
mpoirier_I'll jump on 566645 as soon as this one is fixed.15:56
mpoirier_I have the answer on SD card.  Just need to go through the patch set to see which one broke the SD card.15:57
amitkmpoirier_: ok, it would be nice if you, lag and Bryan divided up the bugs at https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap/ amongst yourselves, depending on what HW each of you have.15:57
mpoirier_to the best of  me knowledge Bryan doesn't have HW.15:58
amitkthey are important enough bugs for our maverick work too, so if the fix isn't yet in 2.6.35-rc3, then we need to apply it as a sauce in maverick15:58
mpoirier_here's a question:15:59
amitkmpoirier_: I'll see if I can make arrangements for some more HW15:59
mpoirier_What has precedence: maverick on panda or bug fixes ?15:59
mpoirier_I'm working on SD card for now while no kernel from TI for panda.16:00
mpoirier_but when kernel is given to us, I don't know what comes first.16:00
mpoirier_and where to fit OTG ?16:00
mpoirier_I just need priorities.16:00
amitkmpoirier_: that (priority) is a question for tgardner, but I believe we need to fix the confirmed bugs in lucid and make sure they don't recur on marverick16:01
mpoirier_Therefore, SD card and OTG would come first.16:01
tgardnermpoirier: for now I think amitk's suggestion is best.16:01
mpoirier_I should check in SD card today or tomorrow. tgardner, we need to talk about the problem and the fix.16:02
tgardnermpoirier: ack16:03
mpoirier_I'll jump on OTG after.  I think upstream got it working.16:03
amitkmpoirier_: with panda, we have a totally new kernel (separate branch, new HW generation, etc.). There will be new bugs. But atleast the OMAP3 stuff should work well on lucid and maverick.16:03
amitkit gives our community something to hack on widely available boards16:03
mpoirier_Ok, if priorities are to fix bugs on OMAP3, that's what I'll do.16:04
mpoirier_there aren't that many.16:04
mpoirier_Who will take care of OMAP4 then ?16:04
mpoirier_people will start asking me questions ?16:05
tgardnermpoirier: we can worry about that when we actually have HW16:05
mpoirier_I have a panda board right next to me.16:06
tgardnerogasawara, are you planning an -rc3 based upload today? I suspect it'll fix some of the process hang problems I've had with the LTS backport.16:06
tgardnermpoirier: indeed, I thought it was still under development.16:07
tgardnerbut, as amitk suggested, lets make Lucid work well first16:07
tgardnerLucid/maverick16:07
amitklucid/maverick on OMAP316:07
tgardneramitk, OMAP4 is maverick only, right?16:08
amitktgardner: right16:09
mpoirier_Who will be working with TI on panda OMAP4 while I fix OMAP416:09
mpoirier_fix OMAP3 that is.16:09
ogasawaratgardner: yep, planning to rebase this morning16:09
tgardnerogasawara, I did a test rebase, it was completely painless16:10
ogasawaratgardner: sweet, should be quick then16:10
tgardnerogasawara, I did bump the ABI before building though, just as a matter of course16:11
ogrampoirier, lag and you have the omap4 HW 16:11
ogrampoirier_, so he should be able to take over 16:12
lagogra: I have Panda16:12
ograright16:12
ograthats what i was saying :)16:12
amitkogra: do you have more beagles in your team lying unused?16:13
ogra(or at least meaning if it came across differently :) )16:13
tgardnermpoirier: between you and lag there'll be plenty to do. the pit of bugs is bottomless.16:13
lagI was agreeing with you16:13
ograamitk, not to my knowledge, lets ask davidm16:13
* lag gets a warm fuzzy feeling16:13
mpoirier_all good with me.16:14
mpoirier_We all need to agree on who does what so that we don't drop the ball.16:14
tgardnermpoirier_, thats what jfo does for you16:14
mpoirier_Just to be clear, I'll keep fixing OMAP3 while OMAP4 support is assured by lag.16:15
mpoirier_And therefore won't look at OMAP4 at this point.16:15
=== kamal-away is now known as kamal
lagI'm happy to look at either 16:17
* JFo looks at *16:17
JFo:)16:17
mpoirier_same here - no preference.16:18
lagOr both16:19
lagMy intention was to just select bugs and work on them16:20
lagI should have my OMAP3 board sometime tomorrow all being well16:20
amitkohh good, then just split up the bugs amongst yourselves16:21
mpoirier_lag: beableboard ?16:21
lagYep16:22
amitkmpoirier_: beagleboard, with a 'g' :)16:22
mpoirier_yes, sloppy fingers this morning.16:23
amitkmpoirier_: not a coffee drinker? ;)16:23
mpoirier_have been going without a drop for 4 years now.16:23
amitkhehe, good call16:24
tgardnermpoirier_, that way lies madness16:24
mpoirier_fantastic !16:24
ogrampoirier_, did yuo test the latest archive kernel already ? 16:29
ograsince i cant get it to boot at all here+16:29
* ogra wonders if it boots for anyone else16:30
mpoirier_ogra: hold on.16:30
mpoirier_ogra: you mean 35-rc3 ?16:30
ogra2.6.35-2.316:30
ogralatest uploaded archive kernel16:31
mpoirier_haven't no. I'll try and get back to  you.16:31
ograi seem to have issues with this patch http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18213.html16:32
ograending up with endless "Wake up daisy chain activation failed." messages and unresponsive board16:32
mpoirier_gruemaster was seeing something like that when I was chasing the SD card problem.16:33
mpoirier_he was trying my kernels.16:33
ograhmm16:33
mpoirier_but he had some weird user space.16:33
ograyeah, and he also had mmc timeout errors16:34
mpoirier_yep - you seem to have a blessed SD card.16:34
* ogra learned to use sandisk for actual work ... i have about ten other brands to test though and didnt see issues 16:36
ograbut i used 2.6.34 until this morning since i needed a reliable kernel for the image building stuff16:36
ogranow i built the first image with .35 which got me the new issues (no mmc timeouts though)16:36
mpoirier_fabulous !16:37
mpoirier_I should have a fix soon.16:38
ogragreat16:38
mpoirier_fix for SD card that is - no nothing about daisy chain.16:40
mpoirier_I'll try to reproduce16:40
manjolag, you can also cat /etc/issues 16:54
lagcat: /etc/issues: No such file or directory16:54
manjocat /etc/issue16:54
lagUbuntu 10.04 LTS \n \l 16:54
manjosconklin, you are cutting off 16:55
manjosconklin, stop your upload 16:55
manjosconklin, you not audiable 16:57
sconklinlet me try restarting mumble16:57
manjosucks16:59
manjosconklin, sucks16:59
sconklinI give up16:59
manjosconklin, you need a better ISP16:59
sconklinJFo: please catch me on IRC after the meeting16:59
JFowill do sconklin 16:59
manjoapw, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=&orderby=-importance&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.17:01
manjotag=kernel-candidate&field.tags_combinator=ALL&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_no_branches.used=&search=Search17:01
manjohttp://qa.ubuntu.com/reports/jfo/kernel-Top50.html17:02
manjohttp://goo.gl/jwSj17:02
sconklinI can hear.17:09
JFoheh17:10
sconklinJust that this might be a situation where we would consider attempting to write a fix17:10
sconklinSeveral of the ones I put on the list would require significant dedication of engineer resources17:11
sconklinmight just be a backport17:12
sconklinI think this can be backported but isn't in stable yet17:13
sconklinI can look at that17:15
sconklinok, I'll see if it applies and builds and send a review request?17:16
sconklinstefan, OK?17:16
sconklin:)17:16
sconklinall good on the previous one17:17
JFocool17:17
sconklinmove on17:17
sconklinX61 clone mode17:17
sconklinYeah, that's what we have to talk about mostly17:18
sconklinThis is apparently a big deal, and ~something~ should be done, but I think it falls on the HWE people17:18
sconklinIt was explained in private email that we have to fix it even in a private custom build17:19
sconklinpresales, willing to take a custom ppa build17:19
=== ogra__ is now known as ogra
sconklinI don't think we have the hardware to reproduce it17:21
sconklinI think it was all ripped out17:22
sconklinnext two and the last one on the list may all be the same bug. There is a brand-new upstream patch that I'm going to put in a PPA for testing.  There are still more bugs which may be the same one. I'm working on this whether it's on the list or not, so it doesn't matter if it's in the top 5017:37
sconklinthat sounds good17:38
sconklinNO17:38
sconklinSee whether the patch fixes all of them17:38
sconklingood!17:38
manjohttp://qa.ubuntu.com/reports/jfo/kernel-buglist.html17:48
falktx_hi guys18:05
falktx_is this the right place for kernel specific issues?18:06
abogani2falktx_: yes18:07
falktx_my friend is having issues with a new kernel18:09
falktx_the mininote 18:09
falktx_it worked on 2.6.32-2118:09
falktx_but not with 2.6.32-2218:09
_guitarman_yes this is me...18:09
falktx__guitarman_: please explain18:09
_guitarman_my hp mininote 110 seemed to work ok when upgraded from karmic to lucid, but then i wiped it and did a clean install of lucid and now although i have 2.6.32-22 kernel, only the 2.6.32-21 kernel will boot18:10
_guitarman_the other kernel just sits there nothing displays - just a flashing cursor at the top left18:11
_guitarman_i am not sure if this is updates to the system that bust it, or if it is hard disk geometry or grub or what.18:11
_guitarman_any thoughts18:11
* _guitarman_ is also googling18:11
abogani2_guitarman_: Could you try to remove the kernel command line options "quiet" and "splash"?18:14
tgardnersmb, bjf: ^^ possible Lucid regression18:14
bjftgardner, ack18:14
_guitarman_abogani2: i will try this now and let you know18:14
abogani2_guitarman_: I hope that you are using an other computer for IRC... ;-)18:15
_guitarman_heheh yup18:16
abogani2_guitarman_: In meanwhile could you give me some details about your installation? Did you have install closed video drivers for example?18:17
_guitarman_ok so... i installed the ubuntu fwcutter driver for the broadcomm wireless whereas before i think i used STA18:18
_guitarman_that may be an issue18:18
_guitarman_abogani2: i booted and it hangs while running /scripts/local-top ... final item is ata4: DUMMY usb 1-5: new high speed usb device using ehci_hcd and address 318:18
abogani2_guitarman_: The ALT+SysReq keystroke works?18:19
_guitarman_no18:19
_guitarman_its hard locked18:19
abogani2_guitarman_: Sorry I meant the ALT+SysReq+S keystroke works?18:20
_guitarman_abogani2: you mean RSEIUB? nope nothing works in here... and if you mean alt-sysrequest,S <-- letter S? that doesn't do anything either18:21
_guitarman_abogani2: pressing that now while it is sitting here doesn't help18:21
smbtgardner, That would be the day0 update18:22
smbtgardner, Maybe he wants to try the -23 kernel18:22
_guitarman_abogani2: do you think if i boot into .21, change wireless driver to sta, reboot and try 22 - would that help identify if thats the conflicting driver that is stopping boot?18:22
tgardnersmb, um, I can't remember what was in the day 0 update.18:22
ogasawaraapw, abogani2: I'm dropping preempt from linux-meta.  Was an oversight on my part when we dropped it in the linux package.18:23
apwogasawara, cool thanks18:24
abogani2_guitarman_: Yes!18:24
abogani2ogasawara: Thanks!18:24
_guitarman_abogani2: ok, i'll do that now18:24
* smb reboots to nohpet to try to fix his strange disconnects18:30
falktx_i noticed a new kernel update in proposed18:35
falktx__guitarman_: u should try it18:35
_guitarman_falktx_: sorry - i will try tihs first then look at the kernel update at least it will help isolate the issue. for some reason the hardware drivers applet is misbehaving in kubuntu18:36
_guitarman_says sorry-jockey - systemerror:installarchives()failed18:37
falktx__guitarman_: did u try other kernel versions?18:38
_guitarman_is there a way i can do this from cmd line abogani2 falktx_ ? choose the restricted driver18:38
falktx_2.6.33/34?18:38
_guitarman_falktx_: .33 is a fail18:38
_guitarman_falktx_: i haven't tried .3418:38
falktx_i have to go18:39
falktx__guitarman_: i hope it works18:39
_guitarman_ok take care falktx_ talk to ytou later18:39
_guitarman_falktx_: thx18:39
abogani2_guitarman_: :-?18:42
_guitarman_abogani2: restricted driver install isn't working in kubuntu proper for me18:44
abogani2_guitarman_: Which driver you are trying to remove?18:44
_guitarman_it says that error: sorry-jockey - SystemnError:InstallArchves()failed18:45
_guitarman_abogani2: happens when i make any change in restricted hardware. active, deactiveate etc.18:45
methril_worksome kernel release manager here*18:45
methril_work?18:46
_guitarman_i tried to deactivate the b43 and activate the sta wireless driver but it said that error18:46
_guitarman_abogani2: then when i log out and log back in, i only had sta listed as a choice and i still couldn't activate it18:46
_guitarman_abogani2: yipes, now my .21 won't boot18:47
* _guitarman_ is screwed18:47
_guitarman_abogani2: booted into recovery .21 kernel in single user, then telinit 4 , startx and i am in again.  going to see what restricted drivers looks like now18:49
abogani2_guitarman_: sudo apt-get remove --purge b43-fwcutter18:49
_guitarman_abogani2: will do that now18:50
* abogani2 goes off for 10 minutes18:50
_guitarman_abogani2: ok, i've done that18:50
_guitarman_ugh.18:51
methril_workwhat is the process to ask for a update of the luci kernel?18:52
_guitarman_abogani2: it removed it, tried to load again, and didn't have source for this kernel anymore then tryied it for my rtkernel .33 and that bailed.. now i have bcmwl-kernel-source as a error in dpkg18:52
methril_worki`ve to fill a bug asking for a release update?18:52
=== pgraner is now known as pgraner-afk
_guitarman_abogani2: how can i install and activate the broadcom sta wireless driver now - through the hardware drivers applet which doesn't seem tob e working or is there a way to do that in apt18:53
eagles0513875hey guys i have a question for yall18:55
eagles0513875what would cause a kernel panic relating to the VFS18:55
_guitarman_abogani2: will installing broadcom-sta-common and -source get it going?18:55
eagles0513875_guitarman_: what card18:56
_guitarman_eagles0513875: BCM431218:56
_guitarman_80211b/g rev0118:56
eagles0513875_guitarman_: give me a sec18:56
_guitarman_eagles0513875: the whole problem i am having is kernels 2.6.32-22 and 23-realtime don't boot on my hpmininote... i was trying to see if it was that i was using the b43-fwcutter driver being an issue. but the hardware drivers applet wasn't working proper18:58
_guitarman_eagles0513875: my 2.6.32-21 kernel boots but even it is sometimes failing and i can then get in via recovery option for the -21 kernel.18:58
_guitarman_eagles0513875: so i was trying to install and activate it via apt to then reboot and see if that driver ws the cause of hanging boot on 22 and 2318:59
eagles0513875guitarman i have always used the b43-fwcutter no  problem19:00
_guitarman_i am trying it out this way to see if that is the issue of the booting no working19:00
eagles0513875O_o19:01
eagles0513875booting not working???19:01
_guitarman_i've just tried to apt-get install the broadcom-sta-common and -source to see if the reboot into kernel -22 and -23 works with it19:01
_guitarman_eagles0513875: nope - hpmininote won't boot into the -22 and 23 kernels but will boot sometimes into -2119:01
eagles0513875strange im having other nightmares with lucid on my desktop 19:01
_guitarman_eagles0513875: i wondered if it was the driver so i tried removing it and rebooting. 19:01
eagles0513875not wifi related though :( 19:01
_guitarman_eagles0513875: heheh yeah. good times19:02
eagles0513875_guitarman_: did you upgrade from karmic to lucid19:02
_guitarman_eagles0513875: that install worke dfine19:02
_guitarman_eagles0513875: i did a clean install and had probs!19:02
_guitarman_funny eh19:02
eagles0513875what kinda problems outa curiosity19:02
_guitarman_eagles0513875: the clean install?19:02
eagles0513875ya19:03
_guitarman_eagles0513875: oddly my microphone didn't work when it did before (onboard mic)19:03
eagles0513875using a live usb for me i ended up with a kernel panic something about a VFS not being able to mount19:03
eagles0513875that was on reboot 19:03
eagles0513875trying with a cd now to install 19:03
_guitarman_eagles0513875: oh thats an odd one19:03
eagles0513875ya19:04
eagles0513875and i also get file mismatches as well when copying .so files some times which sometimes with constant hitting of retry get copied other times they dont :( 19:04
eagles0513875knock on wood that hasnt happened yet 19:04
eagles0513875ive isolated part of my issue to a faulty sata cable19:05
eagles0513875cant dual boot cuz my cd drive cant read my win 7 dvd19:05
_guitarman_oh sounds like a bit of a picle19:05
_guitarman_pickle19:05
eagles0513875ya19:05
eagles0513875thought it was the surge protector which didnt protect me 19:06
eagles0513875which was the case 19:06
eagles0513875the problem was worse then it is now atm 19:06
eagles0513875_guitarman_: join me in hi_jack_this19:07
eagles0513875its just a channel full of tech nuts hehe19:07
eagles0513875we provide support to each other etc19:07
_guitarman_heheh interesting19:07
=== JayFo is now known as JFo
abogani2_guitarman_: Could you boot your mininote on 2.6.32-22-generic without b43-fwcutter and without STA?19:22
eagles0513875btw _guitarman_ do you have both of them installed cuz i tried the sta and i had issues with it and it ended up not working so i uninstalled sta and went with the fwcutter19:23
_guitarman_abogani2: i tried it and it doesn't work19:27
_guitarman_abogani2: i wonder if there is a loose cable or something ... i'm at a loss.19:27
_guitarman_abogani2: windows 7 is still on here and it works fine19:27
_guitarman_:(19:27
eagles0513875_guitarman_: do you have the same issue with karmic19:27
eagles0513875here goes nothing on my reboot19:28
_guitarman_eagles0513875: well this is the odd thing... karmic upgrade to lucid was fine... fresh lucid install was not fine19:28
eagles0513875O_o19:28
abogani2_guitarman_: So b43-fwcutter and STA are unrelated.19:28
_guitarman_good luck on your reboot eagles0513875 19:28
eagles0513875thanks _guitarman_ :) and so far it is looking good :) 19:28
eagles0513875yay19:28
_guitarman_abogani2: i guess thats what this would indicate19:28
abogani2_guitarman_: Are your sure that STA driver is removed?19:29
_guitarman_abogani2: well, neither driver shows as active in the hardware drivers app.  i did purge on both but got some errors19:39
abogani2_guitarman_: c&p on paste.ubuntu.com19:40
_guitarman_abogani2: ok 1 moment. booting back in19:41
jjohansen-> Lunch19:45
* smb is out19:46
* JFo wanders off to get headache medicine19:47
_guitarman_abogani2: http://paste.ubuntu.com/44979019:47
abogani2_guitarman_: Please remove 33-realtime.19:50
_guitarman_abogani2: did sudo apt-get remove --purge kxstudio-kernel-realtime-33 ... done19:57
_guitarman_it still trying to build initial module for 2.6.33-1-realtime19:58
_guitarman_the bcmwl-kernel-source19:58
abogani2_guitarman_: reboot and remove b43-fwcutter and bcmwl-kernel source too20:00
_guitarman_abogani2: ok, will do20:01
abogani2_guitarman_: I'm wondering where is kxstudio-kernel-realtime-33 package come from?20:02
_guitarman_isn't it in your repo?20:02
_guitarman_abogani2: 20:02
_guitarman_abogani2:  or did falktx put it in his as well20:02
* _guitarman_ wonders20:02
abogani2I don't have idea what kxstudio stand for...20:03
_guitarman_k must be for kde20:04
_guitarman_abogani2: apparently thats done20:05
_guitarman_abogani2: removed20:05
abogani2_guitarman_: b43* and bcmwl* too?20:06
_guitarman_yes20:06
abogani2_guitarman_: uname -a?20:07
_guitarman_right now i am in 2.6.32-1220:07
abogani2_guitarman_: So now we have booting system at least. :-)20:08
_guitarman_i'm not sure why the realtime still shows in grub20:09
_guitarman_i removed the package20:09
abogani2ls -l /boot20:10
_guitarman_ah .. i searched realtime and see stuff there20:10
_guitarman_removing20:10
abogani2_guitarman_: Good.20:10
abogani2_guitarman_: Try sudo update-grub to be sure.20:10
_guitarman_thats better20:11
_guitarman_now only have the -22-lowlatency and -22-tgeneric and -21-generic20:11
_guitarman_shall i try and reboot now that we have wifi cleared out and realtime kernel removed?20:12
abogani2_guitarman_: Yes.20:12
abogani2_guitarman_: 32-22-generic20:12
_guitarman_rebooting now20:14
_guitarman_abogani2: stuck again. :(20:15
_guitarman_i guess its not that20:15
_guitarman_i wonder what the difference is between the 2 kernels20:16
_guitarman_abogani2: shall i remove 22 and reinstall it?20:16
abogani2_guitarman_: No but you can try to update initrd image: sudo update-initramfs -u -k all 20:17
abogani2_guitarman_: At the end reboot removing quiet and splash options.20:18
methril_workhow you mark a bug as superseed20:18
methril_work?20:18
JFomethril_work, what do you mean superseeded?20:19
methril_workbug #588832 superseeds #57585320:19
ubot2Launchpad bug 588832 in linux (Ubuntu Lucid) (and 1 other project) "[Lucid] Update to 2.6.32.14/15 Stable Kernel (affects: 2) (heat: 16)" [Undecided,Fix committed] https://launchpad.net/bugs/58883220:19
JFobugs don't really supersede each other20:20
JFoif one is invalid20:20
JFothen that should be the status it is changed to 20:20
JFowith a pointer to the bug that made it invalid20:20
methril_workif you apply 2.6.32.15. you could close the 2.6.32.12 one20:20
methril_workok20:20
methril_workonly release team members are allowed to do that?20:22
_guitarman_abogani2: thx did that and rebooting and will clear out those options and see what happenes inb the -22 kernel.20:22
JFomethril_work, I think bugsquad or bugcontrol can20:22
JFonot sure who else20:22
JFoI know I can, but not sure which team I get it from20:23
methril_workalso i see the same situation with #58341420:23
_guitarman_abogani2: its being a real pest... hangs at the same place - ata4:dummy20:23
methril_worki`m trying to learn the ubuntu-way of bug fixing ;)20:24
JFomethril_work, are you meaning that they are duplicates in some way?20:24
abogani2_guitarman_: Could you capture the sreen?20:26
abogani2*screen20:26
methril_workJFo: The #575853 refers to update to 2.6.32.12. the #583414 refers to update the 2.6.32.13 and the #588832 refers to update to 2.6.32.14/1520:26
methril_workJFo: i don`t think are duplicates20:27
methril_workJFo: but in some way they are20:27
methril_workthe usuall way is to mark them as duplicates?20:28
_guitarman_abogani2: i don't have a camera20:28
_guitarman_i can type it if you like into paste.ubuntu.come20:29
_guitarman_com20:29
_guitarman_abogani2: working on it now.20:30
abogani2_guitarman_: The ALT+SysRQ+H don't print anything on the screen?20:31
_guitarman_abogani2: that does nothing20:32
_guitarman_its full on locked20:32
JFomethril_work, no, that is the way things used to work. we are on a no duplication of bugs policy now20:33
JFothe effort is designed to have all reporters file new bugs per issues20:34
JFoissue*20:34
_guitarman_abogani2: almost done typing20:35
_guitarman_lol20:35
_guitarman_abogani2: http://paste.ubuntu.com/449810/20:37
_guitarman_done pheuf.  thats booting the -22 kernel... the 21 boots fine ... i going to lunch now with co-worker20:38
shadeslayerum ... just to promote my bug : bug 59304120:38
_guitarman_thx for all your sleuthwork so far abogani2 :)20:38
ubot2Launchpad bug 593041 in linux (Ubuntu) "New 2.6.35 kernel keeps toggling bluetooth radio (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/59304120:38
shadeslayerive tried the mainline kernel as well... 20:38
abogani2_guitarman_: :-)20:39
methril_workJFo, could i promote the bug as fixed or works for me? I would like to help reducing the SRUs20:40
abogani2_guitarman_: I suspect than the culprit is the line 1220:41
* _guitarman_ hasn't left yet... still chewing on sandwich20:42
_guitarman_abogani2: b43 ... bug in -22 ?20:42
abogani2_guitarman_: IMO You shouldn't have that line (aka b43*).20:42
_guitarman_because we removed it right20:43
abogani2Exactly.20:43
_guitarman_i dont understand what went wrong20:43
_guitarman_what exact command should i run20:43
_guitarman_i ran the one you suggested20:44
abogani2_guitarman_: Try to add these lines on /etc/modprobe.d/blacklist.conf:20:44
abogani2blacklist b4320:45
abogani2blacklist b43legacy20:45
_guitarman_ok doing now20:45
abogani2_guitarman_: blacklist ssb20:45
abogani2_guitarman_: sudo update-initramfs -u -k all20:46
abogani2the reboot20:46
abogani2*then20:46
JFomethril_work, I usually ping the original reporter asking if it is still an issue in the latest release version20:47
JFoif so, a test of the latest mainline is in order20:47
JFobased on the answer, I determine if it can be closed20:47
_guitarman_ack now no kernels boot - this is before i had a chance to do as suggested.20:48
_guitarman_abogani2: i am going to hit lunch now since this is going to require a livecd and chroot20:48
_guitarman_i will let you know if that works after i get back20:48
abogani2_guitarman_: Ok. 20:50
tgardnerogasawara, is the one apw was referring to? http://lkml.org/lkml/2010/6/13/15521:04
tgardneris this*21:05
ogasawaratgardner: yep, it's already in Dave's net-2.621:05
tgardnerogasawara, cool. thanks21:05
ogasawaratgardner: so I just pulled it from there21:05
tgardnerwfm21:05
=== pgraner-afk is now known as pgraner
manjosconklin, you are broken21:51
=== kentb is now known as kentb_out
dgtombsanyone here willing to help me with ACPI backlight stuff? i want to make a DebuggingBacklight page on the wiki since there seems to be no solid information on how to debug this22:04
=== 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!