[02:37] <Kano> hi, is it known that iwlwifi_rc80211_simple has an unknown symbol in module error
[02:37] <Kano> btw.that error comes on a system without iwl
[03:59] <thully> hi - I'm curious if anyone may be interested in tackling a recent kernel regression I've come across...
[04:00] <thully> In the -12 kernel, my machine (MacBook) suspends fine, but now with -13 and up, it doesn't resume one out of every 3 or 4 times.
[04:41] <TheMuso> TheMuso: Have you filed a bug?
[04:41] <TheMuso> ugy missed him. No wonder tab completion backfired. :p
[05:44] <superm1> is another LUM uploaded planned to be released between RC and final?  
[05:45] <superm1> and if not, will i be allowed to commit a fix to bug 147886 for after release for a sru kernel update, it should just be a header change?
[05:45] <ubotu> Launchpad bug 147886 in linux-ubuntu-modules-2.6.22 "ivtv-fb module has not been merged into mainline yet" [Low,Fix released]  https://launchpad.net/bugs/147886
[09:14] <kraut> moin
[12:34] <verwilst> zul: my test with the patch that hopefully would fix the "Time went backwards" doesn't help :(
[01:57] <ubuntu_demo1> Hi
[01:57] <ubuntu_demo1> anyone here ?
[01:57] <ubuntu_demo1> /nickname ubuntu_demon
[02:00] <ubuntu_demon> Hi. I think I have found a Gutsy kernel bug which might be very important (causing data-loss)
[02:02] <ubuntu_demon> Any kernel devs around I could talk to ?
[02:03] <ubuntu_demon> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/151938
[02:03] <ubotu> Launchpad bug 151938 in linux-source-2.6.22 "gutsy kernel is causing data-loss.somehow related to SATA (media-error)" [Undecided,New]  
[02:10] <ubuntu_demon> I'll return tonight on irc.
[06:45] <superm1> BenC, according to http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-ubuntu-modules-2.6.22/linux-ubuntu-modules-2.6.22_2.6.22-14.36/changelog , the ivtv patch i had didn't get included, but according to http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-gutsy-lum.git;a=commitdiff;h=c701d02ea2d30818d1df2e6b8e74e58f5ede041f it did.  Do you know what the actual case is?
[08:18] <zul> erp http://lkml.org/lkml/2007/10/12/9
[08:19] <Keybuk> just pray that doesn't need an ABI change :p
[08:19] <zul> heh i know
[08:42] <BenC> superm1: it's included in git, and will be uploaded soon
[08:43] <superm1> BenC, i was just worried that the version numbers were identical, so perhaps there was confusion
[08:43] <BenC> superm1: there was some mixup in the repo, but it's getting sorted out
[08:43] <superm1> okay cool thanks
[09:03] <ubuntu_demon> This bug I found might be important : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/151938 Is there anything else I can do ?
[09:03] <ubotu> Launchpad bug 151938 in linux-source-2.6.22 "gutsy kernel is causing data-loss.somehow related to SATA (media-error)" [Undecided,New]  
[09:30] <BenC> ubuntu_demon: I'd have to say it looks more like a hw error
[09:30] <BenC> ubuntu_demon: media errors can sometimes be exposed on large upgrades (e.g. from feisty to gutsy) because it will start accessing an area of the drive that has never been touched before
[09:30] <BenC> upgrades are very disk intensive
[09:37] <ubuntu_demon> Hey
[09:38] <ubuntu_demon> BenC : how would you explain 2 months without any problems ?
[09:38] <BenC> ubuntu_demon: not touching the same spot on the drive? :)
[09:38] <ubuntu_demon> BenC: the problems were also on my /home partition
[09:39] <ubuntu_demon> /sda1 Gutsy /sda2 Feisty /sda3 home ... all three partitions experienced media errors in Feisty around july 30th
[09:40] <BenC> ubuntu_demon: I must have misread something, I thought you were saying that they experienced errors on gutsy
[09:41] <ubuntu_demon> I have seen the the media errors in Feisty. (I can't remember whether I have also seen them in Gutsy). The result of these media errors was that fsck was reporting problems
[09:42] <ubuntu_demon> and files were ending up in lost+found
[09:43] <ubuntu_demon> My guess about what's happening : Gutsy interacts in some different way with SATA drives (I heard something about a new SATA subsystem). Gutsy puts my SATA drive in some "mode" which works fine for Gutsy but is remembered through soft-resets of the machine. Feisty can't handle this "mode" and causes the filesystem to corrupt.
[09:44] <BenC> ubuntu_demon: feisty and gutsy both use libata (sata and pata)
[09:44] <BenC> and that wouldn't cause this
[09:45] <ubuntu_demon> Are there any (potentially relevant) differences in libata between Feisty and Gutsy ?
[09:45] <BenC> nope, unless you hit gutsy while HPA wasn't enabled by default
[09:46] <ubuntu_demon> But that's just a guess maybe something else is happening ofcourse. I personally still think it's a bug somewhere somehow. 
[09:46] <ubuntu_demon> I installed Gutsy Beta last week on /dev/sda1 ... yesterday I saw a media error in Feisty again
[09:47] <BenC> check the media size in dmesg
[09:47] <BenC> make sure that feisty and gutsy see the drives at the same size
[09:48] <JanC> ubuntu_demon: FYI exchanging the HDD shouldn't void your warranty (at least, when this is a personal laptop and not a company one)
[09:48] <ubuntu_demon> BenC : can I grep for something to find these media sizes ?
[09:49] <BenC> dmesg | grep "hardware sectors"
[09:49] <ubuntu_demon> JanC : I'm not sure there are paper seals on the screws talking about warranty. Besides I still don't have access to any 2.5" drive to replace it with.
[09:50] <ubuntu_demon> dmesg | grep "hardware sectors" ... results in nothing
[09:50] <ubuntu_demon> dmesg | grep hardware | grep sectors  ... results in nothing
[09:51] <BenC> [    6.116000]  sd 0:0:0:0: [sda]  312581808 512-byte hardware sectors (160042 MB)
[09:51] <BenC> lines like that, shouldn't be hard to find
[09:51] <BenC> dmesg | less
[09:51] <BenC> and scroll through
[09:51] <JanC> maybe it scrolled out of the buffer already?
[09:52] <ubuntu_demon> I can't find anything like that in Feisty dmesg or dmesg.0
[09:53] <BenC> well, you'll definitely want to do this on a fresh boot
[09:53] <BenC> doesn't have to look like that
[09:53] <BenC> somewhere in there (read it to find it) there is a drive detecting and it will show the physical size of the drive
[09:53] <ubuntu_demon> On my mounted Gutsy partition (from feisty): [    6.216000]  sd 0:0:0:0: [sda]  156368016 512-byte hardware sectors (80060 MB)
[09:53] <ubuntu_demon> [    6.216000]  sd 0:0:0:0: [sda]  156368016 512-byte hardware sectors (80060 MB)
[09:54] <ubuntu_demon> Feisty : [    4.028000]  ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[09:54] <ubuntu_demon> [    4.028000]  ata1.00: 156368016 sectors, multi 16: LBA48 NCQ (depth 0/32)
[09:54] <ubuntu_demon> [    4.036000]  ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[09:54] <ubuntu_demon> [    4.524000]  SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
[09:54] <ubuntu_demon> [    4.524000]  SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
[09:55] <ubuntu_demon> /sda1 seems to have the same size from Feisty and Gutsy dmesg's
[09:55] <ubuntu_demon> Should I reboot to Gutsy, read-only mount sda2 and sda3 and compare those too ?
[09:57] <ubuntu_demon> ow wait 80060 MB is the entire harddrive. So these sizes are equal .. that's good :)
[09:59] <ubuntu_demon> What else can I do to find the problem ?
[10:07] <ubuntu_demon> What's HPA ? I can find hpa mentioned in my Feisty dmesg but not in my gutsy dmesg. Maybe that's the problem.
[10:11] <ubuntu_demon> Gutsy should have hpa enabled according to your own email. But if this is somehow not enabled that might be causing my problem right ?
[10:11] <ubuntu_demon> or at least it might be somehow related to the problem right ?
[10:12] <BenC> ubuntu_demon: no, if that was the problem, you'd see two different sizes
[10:13] <ubuntu_demon> In Feisty dmesg I see things like : [    4.028000]  ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[10:13] <ubuntu_demon> [    4.036000]  ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[10:13] <ubuntu_demon> I Gutsy I don't see these lines. Should that be the case ?
[10:13] <BenC> ubuntu_demon: just a missing printk in gutsy's stock hpa patch
[10:13] <ubuntu_demon> I = in
[10:13] <BenC> feisty kernel had the original hpa patch as written by kyle
[10:14] <ubuntu_demon> What is hpa ?
[10:14] <BenC> hpa isn't your problem
[10:14] <BenC> hpa == host protected area
[10:14] <ubuntu_demon> okay
[10:14] <BenC> which you don't have
[10:14] <ubuntu_demon> Is there anything else I can do to (help) find this problem ?
[10:18] <ubuntu_demon> IMHO 2 months without any problems when not dual booting with Gutsy and smartctl saying that my harddisk health is okay sounds like it's not my harddrive which is dying. Also the laptop is about 1 year old.
[10:30] <clever`rev> !anti-virus
[10:30] <ubotu> Sorry, I don't know anything about anti-virus - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[11:36] <ubuntu_demon> Bye