/srv/irclogs.ubuntu.com/2011/09/26/#ubuntu-kernel.txt

=== jpds_ is now known as jpds
smbMorning +*07:33
sijihi All07:41
sijismb, GooAfterNoon07:41
siji*good07:41
sijiregd bug:82458907:42
smbbug 82458907:42
ubot2Launchpad bug 824589 in ubuntu "improper Touch Screen Driver module(for arm beagleboard) for TSC2046 in the Expansion board,and it connect with DM3730 by SPI port ." [Undecided,Incomplete] https://launchpad.net/bugs/82458907:42
sijii have compiled the module again , but still TS is not working 07:43
smbHm, not necessarily my area07:43
sijismb, ok07:43
sijinow it's not returning any error messages, but not about find anything at /dev/input/..07:44
sijiI hve tried evtest too 07:44
smbWell, if "not finding anything" means there is no automatically created dev, it may be a problem registering with the subsystem. 07:47
sijismb, so wht's the sol for it 07:47
* smb s crystal ball is broken atm07:48
smbsiji, Maybe look whether everything in the init code checks for errors and reports them...?07:49
* apw yawns07:49
sijiok let me recheck 07:49
smbMorning apw 07:50
apwsiji, does the driver even load07:51
apwsmb, morning07:51
* smb was assuming that from "not returning any error messages"07:51
sijiapw, i think no, kernel.log is not shwing anything reg.ads 07:52
apwand if you load it manually ?07:53
sijilsmod dispalying the specific driver module 07:53
apwso the driver _is_ loaded in lsmod, but you have no output in dmesg for it, and no /dev/input elements appearing, correect ?07:56
sijiapw, yes07:56
apwthen your next step i guess is to add debug into the init path of the module to tell you why its not enabling the device07:57
sijiok07:58
ppisatimorning *08:39
smbMorning ppisati 08:41
ckingyawn08:46
apwcking, sounding like a lively morning10:18
Davieysmb: Hello sir!  Do you have a status update on bug 790712?  Is it likely to be resolved pre-release?10:38
ubot2Launchpad bug 790712 in linux "20110531 i386 server ISO: order 5 allocation failure during install" [High,Confirmed] https://launchpad.net/bugs/79071210:38
apwDaviey, expect he is away currently10:44
ckingapw,  it's a slow day today - deep diving into daft bugs10:46
Davieyapw: ta, week vacation?10:46
apwDaviey, no he should be about later today10:47
Davieycking: You could speed up your day by applying for upload access for that damn package.10:47
apwcking, sounds like fun10:47
Davieyapw: ta10:47
apwDaviey, like that'll be any more fun10:47
ckingfun fun fun fun10:49
Davieyha10:49
=== smb` is now known as smb
mdeslaurhey kernel hackers, it would appear something is missing for kernel 12.19 to get pulled in by dist-upgrade12:27
apwmdeslaur, yep i wouldn't think the meta package is updated yet, that has to wait until all the arches are built and approved12:28
mdeslaurapw: cool, just wanted to let you know in case12:29
apwmdeslaur, i would expect leann has that review and upload on her list for this morning12:29
mdeslaurapw: thanks12:29
apwmdeslaur, waiting for something specific in it ?12:29
mdeslaurapw: yeah, I want to test to update bug 85845912:30
ubot2Launchpad bug 858459 in linux "lock up on boot when network cable is unplugged" [Undecided,Incomplete] https://launchpad.net/bugs/85845912:30
apwmdeslaur, you could grab the binaries by hand of course12:30
mdeslaurapw: I will, thanks12:31
apwmdeslaur, what is interesting about that bug, is i have a 533 with an atl1c and i don't see that behaviour12:32
mdeslaurapw: how odd :)12:33
mdeslaurapw: the kernel team definitely needs more buggy hardware :)12:33
apwmdeslaur, hmm mine does have a 1969:2060 whereas you have 1969:2062 ... must be significant12:34
apwmdeslaur, and i suspect it won't help, i'd check whats being offered by stable but ... with k.o down there really isn't one12:35
mdeslaurmy issue seems to be common with the 522, I've seen posts about it all over ubuntu/suse/fedora land12:35
apwmdeslaur, well if its still there in -12, which i suspect it will be then i'd suggest editing your grub entry from the grub menu, and 1) change the "set gfxpayload=" to be =text, then drop quient and splash from the command line and add debug12:37
apwand see if you get some indication as to why12:38
smbDaviey, That bug is very unlikely fixed pre-release. Mainly because neither me really looked much into it (I never saw this happen locally, though I certainly did not do that many installations. Also the question is always does it still happen? I will add the questions to the bug, but currently there is no good info to follow.12:38
mdeslaurapw: ok, thanks12:38
apwppisati, did we ever get a response on what to do with rsalveti's patches ??12:55
ppisatiapw: nope12:56
ppisatiapw: uhm wait12:57
ppisatiapw: i saw an email regarding some patches12:57
ppisatiapw: let me check12:57
apwthe patch is still in oneiric, i guess it isn't going anywhere this late anyhow12:59
apwppisati, is this item going to happen 'look into generating a trimmed down config for debug purposes'13:07
ppisatiapw: nope, that was more of a request on what i could turn on to ease debugging13:10
=== med_out is now known as medberry
ogasawaramdeslaur: fyi, I just uploaded linux-meta.  it's pending approval in the upload queue and then should be available shortly thereafter.13:16
mdeslaurogasawara: thanks!13:17
lamonthttp://pastebin.ubuntu.com/697256/ <-- ppisati why does your kernel hate on the panda?  (natty)13:26
smbThat looks a bit like that thing that maybe is caused by that panel driver (some n900 thing)13:53
* smb does a lot of hand waving gestures13:54
ppisatilamont: the natty kernel that i provided you or latest one?13:56
lamontlatest14:16
lamontdist-upgraded last week14:16
* ogasawara back in 2014:22
tgardnertyhicks, are you still getting email at your IBM address ? I see ecryptfs patches addressed to tyhicks@linux.vnet.ibm.com. Perhaps you should send a patch to update the MAINTAINERS file.14:53
=== ayan_ is now known as ayan
tyhickstgardner: thanks for the reminder - will update that today14:53
tyhickstgardner: The IBM address should be bouncing14:53
tgardnertyhicks, you're assuming IBM has noticed that you're gone :)14:54
tyhickstgardner: that is a big assumption ;)14:55
mthaddonbjf: howdy - is there any more debugging info I can provide for bug#853085? it's basically rendered by laptop unusable currently 15:08
bjfmthaddon, hi15:08
bjfmthaddon, were you running a previous oneiric and then you started having this issue after an update?15:11
mthaddonbjf: yes - I upgraded at beta, was seeing occasional issues, and then it got worse after an update (when I filed the bug)15:12
bjfmthaddon, can you go back to booting the kernel that "worked" ? and what version of that kernel is it that worked?15:13
mthaddonbjf: how do I force it to show me the grub list? normally it's hidden for me15:14
bjfmthaddon, hold the left shift as it's booting (when coming out of post and just before trying to boot a kernel)15:15
mthaddonbjf: I can boot (to a text console only) with 3.0.0-10-generic15:34
mthaddonbjf: actually, I can get to a text console with 3.0.0-11-generic too15:38
mthaddonso I'm not sure why I can't boot off today's daily build...15:42
mthaddonand once booted into unity 2d and udpated, and get another general protection fault15:47
mthaddonguess I could try older kernels and see if I can get into unity 2d15:47
mthaddonand I spoke too soon - this time it doesn't even boot with 3.0.0-10-generic15:53
mthaddonbjf: at this stage I can't see any clear pattern for one kernel versus another - all seem to fail in different ways at different attemps to boot (3.0.0-{9,10,11}-generic)15:59
jjohansenrebooting16:14
=== BenC_ is now known as BenC
* tgardner -> lunch18:01
* jjohansen -> lunch20:15
CanadianPirateDoes anyone know if the compat wireless patch is working in linux 3?22:53

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