I second that - what was/is the bug, and where can I obtain the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346691
Title:
2.6.28-11 causes massive data corruption on 64 bit installations
--
Other words - in which stock Ubuntu kernel was it fixed?
--
Dmitry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346691
Title:
2.6.28-11 causes massive data corruption on 64 bit installations
--
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346691
Title:
2.6.28-11 causes massive data corruption on 64 bit installations
Pete, what was the actual bug, and where is the fix released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346691
Title:
2.6.28-11 causes massive data corruption on 64 bit installations
--
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2007-4573
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2007-4573
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification
The bug was fixed in later versions of kernel, but it seems it appears
again in 2.6.35-19 (in maverick beta) :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/636430
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this
** Tags added: cherry-pick
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I installed the new kernel, 2.6.32, and still have the same problem with
the greeter, synaptic, firefox, and thunderbird getting segmentation
faults. The gdb traceback for synaptic hints that the problem is in
libc. The top of the traceback follows. It looks to my (partially-
trained eyes) that
I upgraded from Karmic to Lucid on my x86_64 box. I tried upgrading.
When that didn't work, I resorted to formatting the drive and installing
from scratch. The initial system works, but (a) doesn't have enough of
the packages installed that I need for work, and (b) normal apt-get
upgrade or
It seems this bug is related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/346691, which seems
to randomly affect different 64bit kernel releases and not others. This
would explain why the error report on the Ubuntu forums about this dated
back to 2008 and such. If the developers looked
Disregard the above post, except for the points about looking at patch
patterns in the affected kernels and that 2.6.32-21 did not have the
issue for me and GUmeR who posted in this bug report which seems to
cover the same issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/515937
Cheers.
These are the bugs fixed in 2.6.32-22 according to the update-manager
along with https://lists.ubuntu.com/archives/lucid-
changes/2010-April/011181.html
[ Andy Whitcroft ]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/526354
[ Tim Gardner ]
I have the problem in 2.6.32.21.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems that could possibly be unrelated at this point, but
https://bugzilla.kernel.org/show_bug.cgi?id=16006 seems to have an
answer. It is my error, but reading some of the comments here makes me
think this bug report might not be the same as 515937, but could be
causing some of the issues
manoj: are you still working on this?
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was able to set the drive to AHCI mode by setting OS compatibility in
the (Phoenix?) BIOS to Vista (instead of Other), which unlocked an
IDE vs. AHCI switch.
I was unable to reliably reproduce the bug while running in IDE mode
(across several wipe-and-installs), but did not encounter it at all
I wiped my Intrepid box and installed Karmic... and hit the bug.
2.6.31-14 still causes superblock corruption on my amd64 machine. Here
are my specs:
Clevo M762T
http://www.clevo.com.tw/en/products/prodinfo_2.asp?productid=88 with
250 GB SATA Fujitsu MJA2250BH G2 drive. Intel Corporation
I managed to grab a part of the long long output (this is just a fraction of
the whole dump).
See attachment.
** Attachment added: INODES.TXT
http://launchpadlibrarian.net/39933385/INODES.TXT
--
2.6.28-11 causes massive data corruption on 64 bit installations
Hi there,
I am afraid I have the same problem - the EXT4 file system getting corrupted
over time.
I've built a NAS from Ubuntu 9.10 Server amd64. The system+temp is on an SSD
drive, while the data is on a RAID6 array using an Adaptec 51645 card and 8
identical 1.5TB disks.
I use use SSH/PUTTY
This sounds similar:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/528981
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The first you said. On my machine, every kernel, both mainline and
custom, just works. Apart from this very annoying problem, I'm not
having kernel panics since... 6 years?
However, I also never got a data loss, maybe because I'm quite used to
recognise the symptoms and hard stop the computer
Shot, finally I had some time for testing with other kernels and these are my
results.
Versions are expressed as shown in the Installed version column of Synaptic.
Ubuntu-specific kernels
2.6.31-20.57 - Doesn't work
2.6.31-19.56 - Doesn't work
2.6.31-18.55 - Doesn't work
2.6.31-17.54 - Doesn't
Marco: By „doesn’t work” do you mean that the bug manifests itself, or
that the given kernel doesn’t work at all?
I’m asking because on my 64-bit Jaunty mainline 2.6.32 don’t even boot
properly (haven’t tried 2.6.31, went with mainline 2.6.30.10 which works
very well).
The custom 2.6.28
Marco: In my case (64-bit Jaunty on a ThinkPad X301 + a 128 GB Samsung
MMCQE28G SSD) the issue went away as soon as I switched to a vanilla
(mainline) kernel: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
Can you try to reproduce your issue with one of these kernels? (I’ve
been happily using
Hi everybody. I'm coming here after a lot of searches about fs
corruptions in Ubuntu. Description from the original poster seems to
apply very well to my situation.
Suddenly, already running apps start to seg fault, while new started
ones usually report some error with shared objects (missing,
Marco, there is a known hardware data-corruption issue in certain
revisions of Via VT82C586A/B/VT82C686/A/B/VT823x/A/C disk controllers;
this is most likely the issue you're hitting.
I'm not aware of what workarounds exist. To confirm the issue is with
this disk controller, mount the internal 2.5
Daniel, it seems quite strange because I've been running Linux on this
laptop since I bought it, in 2003, and never got this kind of problem.
It only showed up since a few weeks and always following the same
pattern. However, I'm going to confirm the issue following your
suggestions as soon as
i can confirm this bug with an 2.6.31-9-rt kernel
my dmesg:
[27216.779223] EXT4-fs error (device sda3): ext4_add_entry: bad entry in
directory #859924: directory entry across blocks - offset=0, inode=3633236108,
rec_len=180364, name_len=142
[27216.779231] Aborting journal on device sda3:8.
@raketeman, please post this, along with system details to linux-
ker...@vger.kernel.org; here isn't going to help
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
attached the lshw associated with the 2.6.31-9-rt kernel
** Attachment added: lshw.txt
http://launchpadlibrarian.net/37919245/lshw.txt
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are
thanks Daniel for this hint - mail is on the road!
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I withdraw from this list. As I forcasted 5 month ago (post 162) this
bug is still uncorrected and now Karmic is out. So I'm not waiting
anymore for a correction of this bug, and skip directly to Karmic 64
which is an awesome version.
Keep up the good job !..
--
2.6.28-11 causes massive data
So, none of the kernel updates of Jaunty did not fix it? Scary.. I moved to
mainline kernel, since I was not able to work on my new laptop because of
that bug. And I'm still on mainline, now it is 2.6.31-02063107-generic. I do
not see a way to test other kernels, because it would possibly trash my
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu)
Status: In Progress = Confirmed
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a
Thanks for the detailed testing, SecuGuru. Can you try with 2.6.30 mainline
kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30.5/
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you
SecuGuru: can you try to reproduce the problem, booting separately with
'iommu=soft', 'iommu=off', 'mem=2G' please?
Each time, it's worthwhile catching the IOMMU settings with 'dmesg |
grep -i iommu' after bootup.
--
2.6.28-11 causes massive data corruption on 64 bit installations
This bug still exists in the 2.6.28-14 amd64 kernel...interestingly, it
didn't manifest in my system until I upgraded my RAM from 2GB to 4GB.
My system was down for mobo RMA (bad voltage reg) for the last 3 weeks.
Was running fine since Jaunty first went live when I disassembled for
RMA, root
Addendum to previous comment's System Specs:
512MB nVidia 9800GT graphics card
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installed 2.6.29 kernel per workaround suggestion
(http://ubuntuforums.org/showpost.php?p=7382178postcount=29) to no
avail.
Data corruption appears to manifest only in files 8MB or larger.
Attempting to update package ia32-libs via update manager results in
failed download (hash mismatch). Using
The bug is fixed in Karmic Koala alpha 4 (kernel 2.26.31 RC5) and the
2.6.30 familiy is also bug-free to this respect.
Paradoxically, Koala seems faster and less bloated than Jackalope ;-)
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
I have successfully applied the fix in #122 as well. I have an ASUS
N80Vb laptop. Everything seems to be working, and I have had no crashes
or fs corruption after several reboots.
Fingers crossed...
--
2.6.28-11 causes massive data corruption on 64 bit installations
Could we please get an update on the prospects for fixing this bug?
It's been about two weeks since the above post.
Is it fixed in the *-14 kernel?
This thing is reaking havoc on a lot of our older systems, and possibly
a couple of our newer ones. Not only is it destroying data, it's
destroying
Just two things for what it's worth:
Fact: I've been using the 2.6.29-04 kernel with up to date 64-bit Jaunty
on ext3 for a couple of months now with no problems at all.
Opinion: I am still horrified, appalled, perplexed, and angry that there
are neither any warnings on LiveCD iso downloads for
I came across this issue and found that the solution proposed by Lorant
Nemeth on comment #122 worked, though with a slight twist. I was unable
to install a fresh copy of intrepid because the liveCD could not mount
the swap (too lazy to investigate after dealing with this mess),
therefore I just
Note that the bug has already been fixed in later kernel versions, it's just
the ISO that hasn't been updated. Even though it really should be updated,
the bug will not persist 'til Karmic.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
@Manoj (2009-07-09): I believe this bug is still present in
2.6.28-13.44, the latest released kernel. Is there any reason to expect
it is fixed in 2.6.28-14.46 (in jaunty proposed)? Do you have a specific
patch in mind?
A colleague had these symptoms on a Dell E6500 (has ICH10 and Nvidia
This bug is really a show-stopper.
I can't believe the Ubuntu team wants to close this report even if the bug is
still there (see 5 posts above)
This has stopped me from upgrading to Jaunty, and I bet this bug will stay
uncorrected up to Karmic, where it will (hopefully) disappear with the .30
If you add up the amount of time lost by people having lost data due to
file corruption with this bug, it will probably outweigh the effort
needed to fix this.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug
I have not dared trying the 2.6.28-14 kernel with the ata_piix driver
because I did not see any related changes in the changelog aswell.
However, after switching my HP/Compaq 8510w (through the BIOS) to AHCI
mode (or native mode as HP calls it) I did upgrade to 2.28-14 and have
not noticed any
Is this stilll an issue with Jaunty? iirc this bug was opened early in
the dev stage of jaunty, Jaunty proposed is at 2.6.28-14.46. Can someone
verify that this is fixed in Jaunty so that I can close this bug as fix-
released ?
Thanks a ton
--
2.6.28-11 causes massive data corruption on 64 bit
Probably the bug is still there as long as there are no ata-piix related
changes in the changelog. Other than that it appears data corruption bugs and
system stability aren't very high priority with the Ubuntu devs :S
Even with my controller in AHCI mode, I've experienced several different types
It may not be the ata_piix driver -- I set my controller to AHCI mode
before I even installed Jaunty, yet I experienced filesystem corruption.
My corruption could have been caused by an unrelated bug, however.
I haven't had any problems since I upgraded to a backported Karmic
kernel. If anyone
@giorgio130: Ok.. there is ext3, reiserfs, etc, problems but for
now, there are fixes/patches created by lead developer of ext4 due to
tested data corruption problems, available to fix current 2.6.28 kernel
at jaunty, and directly applied to 2.6.29 and 2.6.30 kernels.
So. there is a
@feanorknd: These patches may all be valid, but this is unrelated to
this bug. This bug is about data corruption that occurs on ext3,
reiserfs and other non-ext4 filesystems. Anyone with ext4 problems
should not post here if they cannot reproduce this with ext3. Do a
proper search for the
What we know:
*) Bug it is NOT FS related: we have reports so far for jfs, xfs, reiserfs,
ext3 and ext4
*) Apart from a dubitable case, is x86_64 related, but concurrency is not the
issue (even going UP it persists).
*) Is FOR SURE hardware related, ata_piix driver being the most probable
2.6.28-13.44 (amd64, core i7, AHCI mode) does NOT work for me -- I also
experienced filesystem corruption.
Theodore Ts'o (lead ext4 developer) has some patches in the 'for-
stable-2.6.28' branch of his git repository (see
http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=shortlog;h
@a7x: this is not related only to ext4. Corruption comes with ext3,
reiserfs as well.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Linux inf16 2.6.28-13-generic #44-Ubuntu SMP Tue Jun 2 07:55:09 UTC 2009 x86_64
GNU/Linux
In AHCI mode system works correctly.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member
on ubuntu 9.04 with 2.6.28-02062809-generic kernel on x86_64 i do not have any
problems with fs. I am using:
product: ICH9M/M-E 2 port SATA IDE Controller
configuration: driver=ata_piix latency=0
Is it possible to switch IDE mode to AHCI without reinstalling a system (i
tried with windows and i
Switching shouldn't bring any problems to installed systems. The kernel
will automaticly use the correct driver. At least it worked fine for me
(also with my already installed system) :)
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You were right - it works in this mode. I will try new kernel.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Anyone has tried the above solution? I'd try it but this is my only
machine, I'd like to preserve it from such corruption... :) Moreover, is
this supposed to work with a Compal jhl90?
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You
A new kernel, 2.26.28-13 is available from the update repositories. Now
I guess that when someone installs Ubuntu from the CD image, the kernel
will be updated from 2.26.28-9 (which is known to be free from this bug)
to 2.26.28-13 (which I hope will be bug-free as well). So, practically
speaking,
2.6.28-13 is not likely to be bugfree. I checked the changelog and there
is no change since the 2.6.28-11 kernel which seems to be related to
this problem.
giorgio130, I suspect it will work on your system, I have a jhl91 myself
which appears to be very similar. In any case I would suggest you to
@Julius:
Well, it worked and even quite painlessly. I'll try the buggy kernel as soon as
I've the time to make a decent backup. However, I don't think I'll switch back
to 2.6.28.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You
This is just to second (and third and fourth and fifteenth!) the
comments by mirix and Tim McCormack above.
It is essential that Ubuntu's processes for software release are able to
prevent such appalling disasters in the future. It is a measure of how
much goodwill Ubuntu has in the community
The important question here is not How do we fix this bug? but How do
we prevent this sort of bug from occurring again? Please take the time
to read this excellent article about how software is written for NASA's
shuttles, paying close attention to the part about The Process:
Let's not go to deep in this NASA thingy... They are in a much easier
situation from HW platform point of view. I doubt there are too many
kind of space-shuttles they have to support :) On the other hand I agree
that these kind of problems should be discovered earlier, maybe
gathering and
While I agree that that discussion needs to take place, I really don't
think that this is the place for that discussion. Maybe a forum topic
would be more appropriate. Just my opinion.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You
It seems i have found a solution which should work for at least Compal
notebooks. I found this based on information I found in one of the
duplicate bugs. It seems at least the ICH9 controllers have two modes of
operation. One is called IDE compatible or no-AHCI mode and is enabled
by default. This
It was just what Daniel asked to be tested in order to identify the
problem. Never mind, though, installed the headers and everything works
perfectly. No FS issues, and graphics are fine. Hope that helps.
--
2.6.28-11 causes massive data corruption on 64 bit installations
This bug bit me on a Dell Latitude D830 laptop (64-bit Core2 Duo CPU,
ICH8 SATA controller).
Laptop had been very stable while running Intrepid for months.
Installed the Jaunty CD (9.04, from April 2009), which has the now-
infamous 2.6.28-11 kernel. Got lots of silent filesystem corruption
notebook asus f6a
Linux 2.6.28-11
DISTRIB_DESCRIPTION=Ubuntu 9.04
Intel(R) Core(TM)2 Duo CPU P8400
ICH9M/M-E 2 port SATA IDE Controller
i tried many configurations of filesystems.
i have lost whole lvm volumes (root xfs on logical volume). i tried to use ext4
on raw partition with same resul
after lastest upadates on
notebook asus f6a
Linux 2.6.27-14-generic x86_64
DISTRIB_DESCRIPTION=Ubuntu 8.10
Intel(R) Core(TM)2 Duo CPU P8400
ICH9M/M-E 2 port SATA IDE Controller
i have same problem as above. Maybe this information can by useful - on both
versions of ubuntu i have big problems on
02062809 Z seems to work for me. It's not usable in my case because
the nVidia driver won't work, but that applies to any replacement
kernels. Still, no filesystem errors here.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received
2009/6/18 Bobby robert.rankin...@gmail.com:
02062809 Z seems to work for me. It's not usable in my case because
the nVidia driver won't work, but that applies to any replacement
kernels. Still, no filesystem errors here.
Not sure what that kernel Z is but I'm using one of the vainilla
kernels
I saw my data corruption issues on kernels:
ubuntu kernel 2.6.28-11-server
mainline kernel 2.6.29-02062904-generic
mainline kernel 2.6.30-020630-generic
i've seen issue on both SATA and USB attached disks. also, doing MD5sum
checks of the install cd fails on that machine ... but same disk does
Am installing Kernel Z right now, will report back in the morning
after leaving it run all night. Also, if there's still any doubt, it is
a 64bit only issue. I install 32bit ubuntu on the same computer and it
works perfectly.
--
2.6.28-11 causes massive data corruption on 64 bit installations
This is the worst ubuntu bug i have ever struck - i just discovered my
backup of my root part was no good due to being made from a usb boot of
9.04, and now my real root partition is gone too. this bites big time. I
have requested some update to the release notes...
I feel pretty stuffed here now
If this truly is a software bug, our best shot at addressing this bug is
via bisection, from lack of specific knowledge.
There are enough reports the we consider the ubuntu kernel
2.6.28-9(.31?) good and we know (at least) ubuntu kernel 2.6.28-11.42 is
bad. We can rebuild intermediate kernels
fwiw, since I moved to kernel 2.6.29.02062904 (which is a bit later than
either A or Z?) I haven't had any problems. No crashes, no
instability, even after repeated suspends.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received
I cannot believe this bug is still open.
To all the people doing hardware diagnostics: This is not a hardware
issue. As far as I can tell, it affects exclusively to the Unbuntu
kernel 2.6.28-11. Any other kernel/distro I have tried (older or newer)
works perfectly. I am running 2.6.30 from
Well, I'm still seeing my large file data corruption issue on mainline
kernel 2.6.30-020630-generic
md1 : active raid5 sdc1[0] sdf1[3] sdd1[1] sdg1[4] sde1[2]
1953535744 blocks level 5, 64k chunk, algorithm 2 [5/5] [U]
md0 : active raid1 sda1[0] sdb1[1]
78123968 blocks [2/2] [UU]
Richard Huddleston, do you have a Intel Corporation 82801HBM/HEM
(ICH8M/ICH8M-E) SATA IDE Controller (or another controller that uses
the ata_piix kernel module)? If not, this bug is probably not the cause
of your problems.
--
2.6.28-11 causes massive data corruption on 64 bit installations
I'm using the Intel board DQ45CB which has the Q45 Chipset with the
82801JO I/O Controller Hub, the information is available in my lspci
from my first post.I don't know the differences between the 82801JO
and the 82801HBM/HEM controllers.
--
2.6.28-11 causes massive data corruption on 64 bit
It seem like you've got a SATA controller using the ata_piix kernel
module which which I believe common to all people suffering from this
bug. My personal experience (and other people are reporting similar
observations in earlier commens to this bug) is that upgrading to a
mainline kernel of later
I thought a short howto would be good for some people, about how to get
Jaunty running on the effected systems. This is for paranoid people like
me, who don't trust a system installed with an installer running the
buggy kernel or booted up with it once (and have no intention to
create/wait for a
The first question above in my case is not applicable: my laptop was rock solid
with Ubuntu 8.10 and is rock solid with development karmic. Cannot report about
windows, and IMHO it shouldn' even be asked such a question. No settings have
been modified/altered, and BIOS is vendor default.
ACH SO Use this, I was normal user.
** Attachment added: lspci.txt
http://launchpadlibrarian.net/27727402/lspci.txt
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member
The issue is on 64bit kernels 2.6.29-02062904-generic AND kernel
2.6.28-11-server.
I believe I'm seeing the same issue on ICH10 AND SiI 3132 ... separate
software raid (raid1 and raid5) on both controllers are suffering.
Everything was OK until a couple of days ago, issue only came up when I
To build a better understanding of the mechanism, it's worthwhile finding out:
- is there sufficient cooling for the southbridge and northbridge?
- are you running the latest BIOS?
- are you running the vendor's validated BIOS defaults?
- is the powersupply of reasonable quality/spec
- for
This is my first report, so I apologise if it's incorrect, and for my
lack of technical knowledge.
I upgraded my desktop from Hardy to Jaunty, and after a week, the
problems described above began - random system freezes, followed by X
server error and running fsck, which reported various inode
@Lesley:
I think your report is important. Until now, it happened always on x86_64
installations... attach the output of your lshw.
--
2.6.28-11 causes massive data corruption on 64 bit installations
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a
Attached as requested. I'm going to have to do a complete reinstall (of
8.10) to get the system up and running again; is there anything else you
need before I overwrite the disk?
** Attachment added: lshw_060609
http://launchpadlibrarian.net/27583080/lshw_060609
--
2.6.28-11 causes massive
I think this is enough... Anyway, as stated before, if you want to keep
using 9.04 you can always use a more recent kernel, or, as you said you
came from hardy, the old one that shipped with it, which should be still
selectable in grub.
--
2.6.28-11 causes massive data corruption on 64 bit
The filesystem corruption I was experiencing with the stock Jaunty
kernel (2.6.28-11-server) on an x86-64 system was down to the nVidia
CK804 PCIe chipset corrupting data on PCIe read completions from the
SATA controller's DMA engine. I have observed this with a PCIe bus
analyser.
On a system
I previously experienced massive ext4 inode bitmap corruption on an
x86-64 Opteron w/ a CK804 chipset, while performing a large rsync, the
ext4 corruption issue is *not specific* to ICH8/9.
A number of the reports (including duplicate) mention ext4 and the
original report in this LP entry
This bug also occurs with ext3 and other filesystems. If someone
experiences ext4 filesystem corruption on i386, it is not related to
this problem. Maybe some bug reports were over merged.
This bug is specifically about the corruption that occurs on mainly
Compal notebooks with the AMD64 version
@Daniel J. Blueman: Thanks! I'll try that out today.
My system specs, btw, are: Core 2 Duo P8400 2.26GHz, 4GB RAM, Intel GMA
X4500 graphics, 64-bit Jaunty and Intrepid dual boot, and ext3
filesystem. The laptop is an MSI 1223 (i.e. no-name brand, I guess.)
--
2.6.28-11 causes massive data
99 matches
Mail list logo
