I think this bug deserves a "Critical" flag. It's not only causing
instability, but it causes data loss too.
--
jaunty kernel 2.6.28-11 kernel update makes the system unusable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, whic
2.6.28-12-generic #43-Ubuntu did it again. but this time it took significantly
longer...
the filesystem crashed and I had to recover it using live cd
narf.
so no bug fix for me yet, except installing 2.6.29 kernel using ppa...
--
jaunty kernel 2.6.28-11 kernel update renders the system un-
I did some testing and to me it seems to be working. My partitions are not in
ro mode and none of my apps are segfaulting.
If it continues to work without a hassle I think it's time for a 9.04.2!
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/
2.6.28-12-generic #43-Ubuntu is out there, and maybe this one finally
fixes the bug. I'm already testing it as I write these lines.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a m
maxcpus=1 does not help.
I just reinstalled my laptop from minicd. I booted the installer with
maxcpus=1 and double checked that even after the install the kernel
would boot with that option. I installed a few packages, installed
nvidia restricted driver. rebooted and /sbin/init was gone, so next
As a workaround to avoid silent data corruption, boot with 'maxcpus=1'
until the kernel is patched.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The official installation media has to be updated as well. I wouldn't
trust a system which was installed with a kernel that includes such a
problem. (I'm surprised no one faced any installation problems so
far)
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bu
We need it to be made as an official upgrade, is what. For a user to
have to go through "hmm, all my programs just spontaneously crash", go
search for ubuntu bugs, and read through 40 comments, just to get a
fix is asking too much, especially considering a large group of users
barely know how to do
This bug has been open for two months, and was fixed upstream some time
ago, but not in Ubuntu.
As a consequence, 2.6.28-11-generic and 2.6.28-11-server - the
production release media kernels deliver silent and show-stopping data
corruption, to the extent that the kernel kills user processes acces
lshw of my system. Affected with x64 and not affected with x32.
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/26883219/lshw.txt
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification bec
This is my lshw.
2.6.30rc5 (vanilla) don't seem to be affected.
I've downloaded it from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/26724966/lshw.txt
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
after instaling system just
sudo dpkg -i generic.deb all.deb image.deb
and there wont be any other errors trust me ;-)
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this b
I used the ubuntu repo System was stable enough with buggy kernel to
upgrade to the newer one. After that I ran fsck in case there were any
errors. So far no problems with the newer kernel.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346
Those who have upgraded to 2.6.29: did you use vanilla kernel, or you
used some ubuntu repo
My only problem with the kernel upgrade is, that first you'd need to
install ubuntu from the CD with the same buggy kernel, and only after
that you can install the new kernel. This means that by the end of
Confirming that I too have an ICH8M/M-E and had the problem. I upgraded
to 2.6.29 and it's not gotten any worse, but I need to fsck.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a
I've same problem with Ext4, Jaunty 9.04 x64 and kernel 2.6.28-11).
Sometime, without blackout or crash, the applications on Jaunty diseappear or
become not visible.
Last time I've started GParted and don't found ntfsprogs but is installed!
Sometime diseappear the icon on gnome menu of some applic
I have not tested 2.6.28-12, but the changelog does not mention this bug
being closed.
Changelog is at
https://launchpad.net/ubuntu/jaunty/+source/linux/2.6.28-12.43
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this b
anyone has tested 2.6.28-12? it is in the "proposed" repository.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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-bu
Hi,
I have ICH8 as well:
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
SATA IDE Controller (rev 03)
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member
if its controller driver error , why on my foxconn x38 ich9r there are
no errors?
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
My failing system also contains a 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE
Controller
Just for your information.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs
Here is the whole changelog:
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_2.6.28-11.42/changelog
It seems there have been one or two changes to ata_piix. Maybe the
problem could be related to some of the libata changes.
--
jaunty kernel 2.6.28-11 kernel update renders the sys
If it is an error in the drivers (e.g. software), why should it show up in a
hardware test?
>From what information I've got it looks like something was broken in the
>ata_piix kernel module between versions 2.6.28-9 and 2.6.28-11 and then
>subsequently fixed (it could also be an error somewhere
wired if its controler error why, smart doesn't show any errors on ich9
? :P
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I've got an ICH9M/M-E here, so it seems both 8 & 9 are affected.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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-bu
I can confirm that on affected system is "82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE
Controller".
On another computer without mentioned IDE Controller is 2.6.28-11 running fine.
** Attachment added: "lshw output from affected system"
http://launchpadlibrarian.net/26532186/lshw.txt
--
jaunty kerne
Were there any changes in the ata_piix driver (the driver used by
82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller which 5 of the people
suffering from this bug have in their machines according to posted
output from lshw) between 2.6.28.9 and 2.6.28.11?
--
jaunty kernel 2.6.28-11 kernel update re
Also I forgot to mention all partitions were ext3 formatted during
installation.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I was also a victim of this bug, in which I experienced the following:
1. My applications started receiving segfaults. I tried to strace them and
found that the segfaults were mostly due to problems with files (corrupted
files)
2. Then my administrative applications started segfaulting and after
Just for developers of karmic, bug is no more present in Ubuntu
2.6.30-2.3-generic.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Good morning,
my FSC-notebook has the same problems described above. IT was upgraded
to jaunty (stable) from Ibex. After 2 days it didn't boot anymore. A
trial to save data only had partial success - lots of data are missing
:-(
Did some reinstalls with several FS-types (reiser, ext4, ext3) with
Hi, I ran memtest and it reported no error. The very same laptop is
stable with no errors if booted from en external drive with intrepid.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you a
I C well over here, it's a 64 bit laptop AMD based... I'm
using ext3 partitions with a .28 kernel. It's stable. As a matter of
fact, now that I think about it why am I associated in this bug?
:-D Anyway.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://b
In my case there was no problem with memtest. I even checked it half an
hour without problems. Well, i have Jaunty on another notebook, and
there it does the job right. After all i installed the 2.6.29 kernel.
everything works fine. Too bad the 30rc4 won't install because it fails
to build the nvid
Yes. In my case has memtest reported errors in my RAM modules.
Edmundo wrote:
> Could a memtest run detect a problem with RAM then?
>
> On Tue, May 5, 2009 at 12:24 PM, chriz wrote:
>
>> I will note here that corrupted RAM modules also could result in
>> corrupted files and file system errors.
Not a memory problem here. System is rock solid with either 2.6.28-9 kernel OR
2.6.29 mainline. Definitively NOT a memory problem: it is just unusable with
2.6.28-11 which is jaunty final kernel.
I am now on karmic devel, using 2.6.29-02062902-generic and have NO problems on
same hardware.
--
Could a memtest run detect a problem with RAM then?
On Tue, May 5, 2009 at 12:24 PM, chriz wrote:
> I will note here that corrupted RAM modules also could result in
> corrupted files and file system errors. So in my case with Ubuntu 9.04
> x64 and ext4. Replacing the corrupted modules stopped get
I will note here that corrupted RAM modules also could result in
corrupted files and file system errors. So in my case with Ubuntu 9.04
x64 and ext4. Replacing the corrupted modules stopped getting more and
more file system errors. But nevertheless were some errors remaining
what is related to this
The saga continues:
- cp /var/lib/dpkg/status-old /var/lib/dpkg/status
- apt-get -f install runs fine
r...@kolibri:~# apt-get install wireshark tshark vim-full
compizconfig-settings-manager mc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The follo
Reinstall done:
- first boot ok
- install all upgrades
- reboot ok
- install nvidia 180 driver
- first reboot stuck before splash screen !?!
- second reboot successful
- apt-get install wireshark tshark vim-full compizconfig-settings-manager mc
> complains about corrupted /var/lib/dpkg/status
On my T61p I got all sort of filesystem problems just like Martin
Peterka (no io errors in dmesg). Applications were crashing with memory
corruption error and so on so I decided to reinstall the system from
scratch. Install went fine, but after the second reboot I got back
initrd prompt saying that
I had same problem.
System was running fine, until I updated to jaunty (64bit). After second reboot
auto fsck failed (on one of my ext3 partitions). So I`ve repaired it manually.
Some data was lost, so I buy an external usb harddisk and start back-up. System
freeze and didn`t boot anymore. I try
Indeed, Nvidia works in the current 2.6.29 perfectly. But VMWare Server
won't compile the modules needed, even though 2.6.29 headers are
installed and even though the gcc version it requests is installed...
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launc
2009/5/2 KJ :
> mainline kernel 2.6.29 indeed does not contain the bug anymore. but this
> is quite inconvenient for the regular user since the modules for
> proprietary drivers (nvidia) are missing...
They work perfectly here. If you install the new kernel using one of
the .deb's from kernel.ubun
mainline kernel 2.6.29 indeed does not contain the bug anymore. but this
is quite inconvenient for the regular user since the modules for
proprietary drivers (nvidia) are missing...
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You
2.6.29-02062901-generic
fsck found no error, works good for me.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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-bu
After you've installed kernel 2.6.29 or 2.6.28-9, run a fsck from a live
cd.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
But apt-get is not the only bug : many files could be corrupted... cf my
duplicate of this bug : bug 350268
How to be sure there is no problem after installing a new kernel which fixes
the problem?
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.ne
You can workaround the apt-get segfault with "sudo rm
/var/cache/apt/*.bin" and then install a different kernel.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bug
@ ®om: let's hope it's solved before karmic
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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
u
I agree this bug should be critical.
It seems to affect only jaunty 64 bits, but it makes the system totally
unusable.
Once resolved, a new .iso of Jaunty must be released (9.04.1), because
it is not possible to install the current final release (which doesn't
work) to apt-get upgrade (which segf
fuchur:
actually I first installed 8.10 and performed a dist upgrade. after the first
reboot I selected the old ubuntu 8.10 during the grub menu. once the system was
up and running again I downloaded 2.6.28-9 debs from packages.ubuntu.com and
installed it.
the strict ubuntu release cycle harm
I can tell you that I lost two days work with this "bug". Next time I
will not assume a final release is stable and wait before upgrading.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you
I agree that it is not acceptable to release a so called "stable"
version being aware of such a serious bug.
Fuchur:
I have compiled kernel 2.6.29.1 (2.6.29.2 is already available but I
have not tested it) a few weeks ago and I have not had any issues since
then.
You can download precompiled pac
I tell you why it isn't critical, my desktop c2q,x38+ich9r,4gb,3 hdd,
works great with it, my friend laptop with x2, and dekstop with x2 also
works. Its realy hard to say what when wrong but obviusly developers
should be test system on modern laptops, to avoid this kind of
problems...
I've install
I am amazed that this bug is not marked as Critical!
Obviously, this affects a great deal of users in a way that is extremely
destructive.
In my opinion, this bug alone renders Jaunty completely unfit for a
production environment! There's no getting around that data loss and
file system corruptio
i have same bug, on my jhl90 but downgrading kernel doesnt work :/
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/26055451/lshw.txt
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification
same problem here on a compal jhl90. I managed to install 2.6.29 and it
seems to run fine now.
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/26044354/lshw.txt
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You rec
Ok, as this seems the original bug report:
Until this is fixed, I am thinking about using a new kernel, but
a) which problems could this cause - there must be a reason that kernels
are never replaced during a release cycle
b) how would I do this - apt-get typically hangs after a few packages
Ok, as this seems the original bug report:
Until this is fixed, I am thinking about using a new kernel, but
a) which problems could this cause - there must be a reason that kernels
are never replaced during a release cycle
b) how would I do this - apt-get typically hangs after a few packages
as far as I see yes.
either the current 2.6.29 mainline kernel or 2.6.28-9 can help you out.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Seems like it's the same problem I have...
http://bloc.eurion.net/archives/2009/one-week-with-debian/
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Maybe related : bug 350268
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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
ubuntu-bugs@lists.ubun
Have seen the same problem here on my HP Compaq 8510w. While downloading
updates (using the update manager) the filesystem suddenly locked up
(switched to read-only mode). At that moment I had one virtual machine
(VirtualBox) running as well, but I do not think think that's related to
the problem.
AFAIK 24/04 is release date for jaunty and on my system the current
ubuntu kernel version (not the one I am running with, but the one linked
to the linux-image-generic) is 2.6.28-11.42. So the message from KJ
above,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/346691/comments/18
answers Y
Did anyone try if the final version of Jaunty still has this issue?
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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
I have gotten WAP2E to work by using wicd as my network manager. Sounds
like I have another bug to search for.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs,
Just to comment on my previous comment, it seems WPA2E still doesn't
work.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
IIRC Jaunty will definitively ship with a 2.6.28 kernel.
https://lists.ubuntu.com/archives/kernel-team/2009-February/004321.html
Can confirm bug is not present using mainline 2.6.29.1, but this will be of
some help with Karmic.
For people who do not know how to get mainline, here You can find "s
Oooh, I found something else interesting out. It's too bad it's this
close to release, but it seems the upgrade to the .29 kernel also fixed
a bug I(and others) seemed to have about network manager not connecting
to encrypted networks. So far, I am able to connect to my WEP wifi
hotspot which I cou
I found out after rebooting to try and install the new kernel that my
partition was too far gone to boot up anymore, so I had to reinstall. I
also want to add that I found out that when I reinstalled Kubuntu RC for
the fourth time that even if I don't upgrade to the latest kernel, it
still messes t
I just did a disk repair in order to boot up again. Because I'd rather
not lose anything else, I'm going to use the ppa for .29 kernel until
something better is shown here.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received
since this is such a showstopper for everyone with this hardware config I'd
really appreciate any dev comment.
is anybody working on the issue?
do you need more information?
what can be done to track down the error?
we're close to the official release. this could turn into a disaster for a lot
I forgot to say on the above that I installed with the RC.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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 mai
I am also getting the same things as people above. I am currently
running off live cd and found this bug here, which hits it right on the
mark for me. I have the exact system specs as the common list and only
seemed to have the problem after kernel upgrade. Hope there is a fix for
release.
Attache
the trouble continues with linux-image-2.6.28-11-generic (2.6.28-11.42)
filesystem access fails after a few minutes.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a member of Ubuntu
I'm experiencing the same problem on a Compal IFL90 (aka Sager NP2090).
Running Jaunty 64-bit.
No data loss on my side but I've experienced some random kernel and
process crashes. (Emacs works fine but a few hours later all executions
of emacs result in automatic segfaults!)
Downgrading to 2.6.2
I have exactly the same HW and I'm running the 64 bit Version of Jaunty.
And I experience also the same problems you all have.
I can't run 2.6.28-11 without severe data loss.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You receive
I'm also a bit concerned about the RC/final of Jaunty... Anyway, here's
a short summary of all lshw.txt attached to this bug an its duplicate:
Common to all machines:
- Intel Core 2 Duo
- 4 GB RAM
- 4965 AG(N) WiFi
- Intel 965 Memory Controller
- Nvidia Graphics Card: 8x00M
I'm not sure if everyo
Just to bump. Problem is still here. 2.6.28-9 is stable, 2.6.28-11 is
unusable on this hardware. As all hardware is currently working, I have
no problem in living with -9, but am worried about the problem.
Today I just tried again with 2.6.28-11.41 just to have program
segfaulting after a minute o
@god-mok:
when you install a beta version you take some risks. as far as I know,
the problem only happens when you upgrade the kernel. so if you stick to
the kernel provided by the installation CD (2.6.28-9) until the problem
is solved, you should be safe. I guess this is a problem specific to the
@mirix: too bad, if someone knows what he have to do, than it's no
problem, but i don't think thats the idea behind everything. As long as
there is no support it's not such a good idea, right?
Today I had another crash. I reinstalled again, and after reboot the bug
came at first boot, not as alway
Installing 9.04 beta (AMD) via the Live CD and then compiling the kernel
to 2.6.29.1 (before doing any other update via Aptitude/Synaptic)
renders a very stable and "performant" system.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
sorry, totaly forgotten. Here is my lshw file.
At the time i have no battery attached, but doesn't matter, 'cause it was the
same.
And yeah, our hardware seems very simmilar.
Only thing is i do not have the Bluetooth-Module. Everything else is veri
similar to my hardware.
Oh yeah, and another t
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Manoj Iyer (manjo)
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
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 patch mentioned above was suspected by me to cause lot of trouble,
but it NEEDS to be something related also to HW configuration.
Tried today again with 2.6.28-11 and got EXACTLY same behaviour as god-
mok. I was really lucky to recover filesystem and get back here. AGAIN:
No Problem with 2.6.
** Summary changed:
- jaunty kernel 2.6.28-11 kernel destroy system
+ jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
--
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you
87 matches
Mail list logo
