[10:55] <ppisati> [flag@stinkpad ~]$ find /lib/modules/3.5.0-17-generic/ -name \*.ko | wc -l
[10:55] <ppisati> 3472
[10:55] <ppisati> [flag@stinkpad ~]$ find /lib/modules/3.5.0-18-generic/ -name \*.ko | wc -l
[10:55] <ppisati> 582
[10:56] <ppisati> with this kernel: https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3915554/+files/linux-image-3.5.0-18-generic_3.5.0-18.29_amd64.deb
[10:56] <ppisati> apw: ^
[10:56] <apw> ppisati, and do you have linux-image-*17-generic installed ?
[10:56] <apw> dammit fingers
[10:56] <ppisati> [flag@stinkpad ~]$ dpkg -l | grep linux-image-*17*
[10:56] <ppisati> [flag@stinkpad ~]$ 
[10:56] <apw> ppisati, do you have linux-image-extra-*17* and *18* installed
[10:57]  * cking likes the name of the machine
[10:58] <apw> cking, even seems to mean the same in .it as in .en
[10:58] <apw> if google is to be believed
[10:58] <sawrub> hello all developers, i just installed 12.10 and i'm facing the long seen problem with the Atheros AR9485 WiFi under UBUNTU. Is there any fix on the way. the people at Fedora seems to have fixed the issue long back in July https://bugzilla.redhat.com/show_bug.cgi?id=736435#c8
[10:58] <ubot2> bugzilla.redhat.com bug 736435 in kernel "kernel network driver ath9k causes connection problems with TP-Link TL WN951 Atheros AR5008" [Medium,Closed: wontfix]
[10:59] <apw> 'fixed' ? that is marked won't fix
[10:59] <sawrub> the only solution that i can find on the net is to use compact wireless http://ubuntuforums.org/showpost.php?p=11347273&postcount=63
[10:59] <sawrub> the bug is marked as won't fixed because the issue was aready fixed in different kernel
[11:00] <sawrub> anyways...i don't want to install compact-wireless'
[11:00] <apw> well we offer compat wireless as official packages in ubuntu
[11:00] <apw> though the one suggested there appears to be very old
[11:01] <sawrub> so you mean that will be good to go
[11:01] <apw> i mean it would be worth trying indeed to see if it helps
[11:01] <sawrub> ok, but is the fix for the issue down the line
[11:01] <apw> there is a 3.6 compat wireless.  though as you are on 3.5 i am not really expecting it to help
[11:01] <apw> the issue is not necessarily even known to us
[11:02] <apw> but to find and fix such a thing we would like to find some version in which it works
[11:02] <apw> now fedora claims to have it working i think you suggest from that bug
[11:03] <apw> but if you are right then the claimed fixed version is prior to the version in 12.10 so you would be good already
[11:03] <sawrub> oki...do u want me too file a bug in that case
[11:03] <apw> and as you are saying you are not ok, then the fedora i likely not either
[11:03] <sawrub> oki...
[11:04] <apw> when it goes wrong do you see the mesages in comment 4 on the fedora bug ?
[11:04] <apw> yes filing a bug is a good thing to do
[11:06] <sawrub> but i'm left with frozen keyboard and mouse when this happpes...also i'm not the end user of the machine
[11:06] <sawrub> so there is no option of the user restarting the deamon
[11:06] <apw> seems unlikely its the same problem then as those reporters are able to simply remove and readd the ath9k driver
[11:07] <apw> what makes you think it is the ath9k in your case if all that happens is the machine freezes
[11:07] <sawrub> seen the syslogs
[11:07] <sawrub> i can post them if want to see
[11:07] <apw> attach them to the bug indeed
[11:08] <sawrub> i'm new to ubuntu...can u let me know where is the bugzilla
[11:10] <sawrub> so that i can file the bug
[11:11] <apw> run 'ubuntu-bug linux' which files a bug against the kernel
[11:11] <apw> (linux is the name of the kernel package)
[11:11] <sawrub> in irc window itself
[11:12] <apw> in a terminal window
[11:12] <apw> ctrl-alt-T will get you one of those (in unity)
[11:13] <sawrub> that's smart
[11:15] <sawrub> uname -a : Linux diksha 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[11:15] <ppisati> cking: nah, that's english :)
[11:15] <sawrub> but 'ubuntu-bug 3.5.0-17-generic' fails
[11:16] <apw> 'ubuntu-bug linux' literally will file it agianst the latest you have
[11:18] <sawrub> oki...thanks but how do i attach the logs
[11:18] <apw> once you have a bug it will let you add comments and there is a button at the bottom for adding files
[11:19] <sawrub> oki....let me do that 
[11:33]  * henrix -> lunch
[11:38] <ppisati> smb: "kvm: disabled by bios"
[11:38] <ppisati> smb: problem found
[11:39] <smb> ppisati, good guess yesterday then. :-P
[11:39] <ppisati> right
[11:46] <sawrub> apw: here is the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070800
[11:46] <ubot2> Launchpad bug 1070800 in linux (Ubuntu) "Atheros AR9485 WiFi doesn’t work in Linux" [Undecided,New]
[11:48] <sawrub> apw: another help needed, till the time the bug is fixed, i plan to move to compat wireless, but could not locate that in s/w center as u said its in official repo
[11:55] <apw> sawrub, yeah the easy install package is missing and will only appear when -18 releases into -updates
[11:56] <sawrub> u mean 3.5.0-18-generic 
[11:57] <apw> yeah
[11:58] <apw> you would have to enable -proposed to get that
[11:59] <sawrub> can you make me clear what is the difference between normal and compat wireless drivers
[12:00] <apw> the 3.6 compat wireless drivers are a backport of the wireless from the 3.6 version of linux into (in this case) 3.5
[12:00] <apw> there is no guarentee they will fix anything of course
[12:01] <sawrub> oki...did u went though the bug report that i filed....is there any  thing that u can point at.
[12:02] <apw> that just shows the h/w and driver got all in a muddle and lost control.  hard to know what is the trigger
[12:02] <apw> if only they produced drivers for their own hardware
[12:10] <sawrub> apw:  oki ...have installed compat lets see, if that fixes something
[15:16] <caribou> smb: anything specific you want to discuss around crash at UDS?
[15:16] <caribou> smb: the only think I can see is to remove its dependancy for linux-crashdump meta-package
[15:17] <smb> caribou, Meh, just that now would be the time to ask the previous uploader whether you can do the merge or he want
[15:17] <smb> caribou, We seem to carry one additional change (not sure that actually would be something to finally send upstream...)
[15:18] <caribou> smb: hmm, really ? I thought we were using the same as Debian
[15:18] <smb> caribou, And UDS would have a good change the person in question being grabbable
[15:18] <smb> ;)
[15:18] <smb> caribou, No its a ubuntu1 version (just a patch about spu which seems ppc)
[15:19] <smb> s/change/chance/
[15:20] <caribou> smb: then yes, maybe we can have a chat during the kdump blueprint if it gets scheduled
[15:20] <smb> caribou, If not, there is always the hallway ;)
[15:27] <caribou> smb: I'm looking at the patch: looks to be just an extension
[15:28] <smb> caribou, Yeah, something which we incidentally (not sure this is deliberate either) not package at all
[15:28] <caribou> shouldn't be to hard to get it included upstream if needed
[15:29] <smb> I would think that most of the discussion is just about the "proper" way to do things and to find out why things are as they are and whether that is ok or just unnoticed breakage
[15:29] <caribou> indeed, so we should find out if it's worth keeping this divergence from Debia
[15:30] <caribou> n
[16:27]  * ppisati -> gym
[16:28]  * smb -> pub
[18:58]  * apw -> err
[19:19] <jsalisbury> bjf, herton, henrix, if you have a chance, can you take a look at bug 1070978 ?  
[19:19] <ubot2> Launchpad bug 1070978 in linux (Ubuntu) "eDP laptop screen does not come up until a suspend/resume cycle happens." [Medium,Triaged] https://launchpad.net/bugs/1070978
[19:26] <mdeslaur> FYI: "EXT4 Data Corruption Bug Hits Stable Linux Kernels"
[19:26] <mdeslaur> http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ
[19:29] <bjf> looking
[19:34] <bjf> mdeslaur, thanks for the heads up!
[19:35] <mdeslaur> lol, not quite sure what the picture of jcastro with a nerf gun has to do with the phoronix article :P
[19:37] <bjf> herton, ^
[19:37] <herton> may be he is a undercover ext4 developer :P
[19:37] <herton> yeah, we will have to pick the final ext4 patch for quantal
[19:41] <bjf> herton, in the mean time we may have to revert the bad commit and respin everything (including natty if affected)
[19:42] <herton> bjf, the commit which is said to introduce the problem is only on quantal -proposed so far it seems. I have to review that thread again
[19:42] <bjf> herton, i'm looking also
[19:48] <bjf> herton, i only see it in quantal
[19:51] <herton> bjf, yes, only propagated to us through 3.5 stable
[19:53] <bjf> herton, http://phoronix.com/forums/showthread.php?74697-EXT4-Data-Corruption-Bug-Hits-Stable-Linux-Kernels/page3
[19:53] <bjf> herton, ted ist still not really sure what the bad commit is and is working on a fix
[19:56] <herton> yeah, we will have to wait to have something definitive, there is more hysteria than good data
[19:57] <bjf> agreed
[20:10] <herton> jsalisbury, the i915 bug warrants an upstream report I think. Nothing against reverting the commit though, perhaps Sarvatt is already working to send a revert request/reporting upstream? The commit though says to fix an issue with Macs and retina display, would reintroduce the issue reverting it.
[20:13] <Sarvatt> herton: 3.5 seems to have the same symptom on this machine so i'm testing out a revert there too before doing any of that, tangerine is just taking ages
[20:13] <herton> ack
[20:47] <Theodorus> Does anyone know if the latest quantal kernel (and 3.5.3 it's based off of) has the ext4 corruption commit?
[20:51] <Theodorus> Actually, just found it. I guess it was introduced in 3.5.7 so is almost certainly not in ubuntu
[21:09] <bjf> you could hang around for a few minutes for an answer
[21:56] <bjf> oh, was that "hostile"?
[22:44] <infinity> bjf: Looks like that ext4 bug will invalidate -18.29 and its rebases?
[22:53] <infinity> bjf: Oh, reading more, Ted's now unsure of the cause.  Fun.