Re: [Bug 371191] Re: Corrupted file system ext3 after Jaunty 64 upgrade
Hi John, That might be it... my output of lspci shows I 'm using the same driver. However,I only have problems once and a while when waking up the laptop from a suspend, I turned auto-suspend off and it 's running ok for a week now. I 'm not a real linux expert, what is your advice ? Should I also switch to another driver ? If so, how is that done ? thanks in advance, Wim 00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Dell Device 024f Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19 I/O ports at 6e70 [size=8] I/O ports at 6e78 [size=4] I/O ports at 6e80 [size=8] I/O ports at 6e88 [size=4] I/O ports at 6ea0 [size=16] I/O ports at 6e90 [size=16] Capabilities: [70] Power Management version 3 Capabilities: [b0] PCIe advanced features ? Kernel driver in use: ata_piix John Prather wrote: Here's some info which may (or may not?) help track this down. In the past 6 days, I've installed ubuntu jaunty 9.04 64bit on a new T500 laptop no less than 6 times. As others here report, I would start doing updates/upgrades, and shortly afterward would run into various issues which appear to all be symptoms of corrupted filesystem: * Faulty tree errors doing apt-get update * Errors about /var/lib/dpkg/status content * Errors about /var/lib/dpkg/info/something.list having blank lines Then, at some point, dmesg would indicate that there was some ext3-fs or ext4-fs issue, and that journaling is aborted, and that the filesystem is remounted read-only, which would of course then cause all variety of desktop app misbehavior. A coworker with another T500 that was shipped with mine, is experiencing the same issue on his hardware. Another coworker with a T500, who got theirs in a different order, had been running Jaunty 64bit for a month now with no such problems, so we started to compare lspci output to see what chips might differ in the two T500's that would have one work solidly for a month while the other can't go 36 hours without corrupting its fs. The only glaring difference we could see was that his laptop, which wasn't experiencing any problems, had a disk controller with device 20f8, using ahci driver, while mine was using the same model controller, but was listed with a device id 20f7, and which was controlled by ata_piix driver. Working: 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) (prog-if 01) Subsystem: Lenovo Device 20f8 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 2298 I/O ports at 1c40 [size=8] I/O ports at 1834 [size=4] I/O ports at 1838 [size=8] I/O ports at 1830 [size=4] I/O ports at 1c20 [size=32] Memory at fc226000 (32-bit, non-prefetchable) [size=2K] Capabilities: access denied Kernel driver in use: ahci Failing: 00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Lenovo Device 20f7 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at 1c20 [size=16] I/O ports at 1830 [size=16] Capabilities: [70] Power Management version 3 Capabilities: [b0] PCIe advanced features ? Kernel driver in use: ata_piix I discovered that I could switch my disk controller device from 20f7 to 20f8, and use the ahci driver instead of ata_piix driver by going into my Bios settings, and under Config for the SATA controller, set it to AHCI instead of compatible. I'd suggest that compatible mode might have had issues, except from the amount of complaints here, it's just as likely that ata_piix is buggy when used on this hardware. It'll be a couple days before I'm 100% comfortable that the issue is resolved for me, but I'm pretty sure switching the disk controller/behavior to match what has been working for other coworkers should account for the only difference between their hardware setup which hasn't run into this issue, and mine, which hadn't been able to escape it. -- Corrupted file system ext3 after Jaunty 64 upgrade https://bugs.launchpad.net/bugs/371191 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 371191] Re: Corrupted file system ext3 after Jaunty 64 upgrade
Hi John, Thanks for your answer ! I was celebrating too soon... Just recovered from another crash without going into suspend mode. Very annoying since this is my work machine. by switching to ahci, you probably mean switching in the bios ? Currently I have no rights doing so, but I think I have a good reason for the switch. regards, Wim John Prather wrote: Wim, I'm not very familiar with ubuntu, so am probably not the best source for advice. Your controller device appears to be some dell which differs slightly from the one I have, although they both were using ata_piix. It's possible that the driver doesn't have such big issues with some controllers as it does with others. If your system really seems stable and isn't experiencing regular filesystem corruption, then my advice might be if it ain't broke, don't fix it. There's no reason to go looking for a solution if you don't have a problem. On the other hand, if you would like to be able to use suspend/standby, and you have the patience, you may wish to see if switching from compatibility to ahci helps let you use the suspend feature again without causing you the corruption headaches. My filesystem corruption had been happening all the time, sometimes while doing apt-get update or dist-upgrade, other times while i was away from the keyboard with the screen locked, it definitely wasn't as limited to a specific action as appears to be the case with your controller. Good luck! -john -- Corrupted file system ext3 after Jaunty 64 upgrade https://bugs.launchpad.net/bugs/371191 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371191] Re: Corrupted file system ext3 after Jaunty 64 upgrade
I am also getting that problem on my dell E6500. Currently running live ubuntu and fsck... fingers crossed. I didn 't have the problem in 8.10, but I don 't remember if I used auto-suspend at that time. I strongly suspect that the suspend function is the culprit, so I will turn it of (if I 'm able to boot anyway) I really hope this can be pinpointed and solved, since I use this machine for work and loosing data is not an option. -- Corrupted file system ext3 after Jaunty 64 upgrade https://bugs.launchpad.net/bugs/371191 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253786] Re: /dev/.static/dev is mounted ro in intrepid
hi folks, After upgrading to 8.10 my mythtv setup stopped working. running sudo dpkg-reconfure mythtv-backend I notice lots of these errors: udev active, devices will be created in /dev/.static/dev/ rm: cannot remove `video0-': Read-only file system mknod: `video0-': Read-only file system makedev video0 c 81 0 root video 0660: failed rm: cannot remove `video0-': Read-only file system After googling for a while, I found other packages suffering the same problem: lm-sensors: #289372 mdadm: #270043 #496287 dvb-utils:#292974 xawtv:#283007 I don 't find a way to report properly that all these depend on this bug. Can someone help me you ? -- /dev/.static/dev is mounted ro in intrepid https://bugs.launchpad.net/bugs/253786 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218624] Re: copy broken in glipper (requires 2x Ctrl+C to work) (Hardy)
I can confirm this too. Glipper in Gutsy worked, but fails to copy the correct values in Hardy. I also use glipper the most with eclipse but I suspect it to fail in other apps as well. Sometimes it works, sometimes it doesn 't. Pretty annoying bug, since I really got used to the clipboard manager. Did anyone found a workaround yet? -- copy broken in glipper (requires 2x Ctrl+C to work) (Hardy) https://bugs.launchpad.net/bugs/218624 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87271] openoffice - fglrx problem
Hi, I have the same problem as described by Alvin. I encountered this Unknown error forking main binary / abnormal early exit in edgy after having installed fglrx drivers for my radeon x300se. But even after the upgrade to fiesty, the problem remains. If I change to ati drivers (which are xorg's I assume) Openoffice is ok, but 3d accelleration is missing. I tried different versions of the fgrlx drivers, even the ones from the ati site. Every time with the same outcome. At the moment, I have openoffice 2.1 installed which is slightly different, it just wont start, I even don 't get the splash screen or a warning any more. Again, changing to ati in xorg.conf is a working solution. Please let me know if I can help, I'm eager to test things or give any information about this. thanks, -- openoffice crash with fglrx on macbook pro 15 https://launchpad.net/bugs/87271 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43961] Re: Power down after shutdown does not work...
I have a problem here, when I shut down without splash, the last two lines are - will now halt - [.xx] power down. where the x's are digits. as for now, I shut down the pc manually by pressing the shutdown button for more than 6 secs (but I often forget, resulting in a pc running overnight :( ) specs: Edgy Eft 2.6.17-10-386 (upgraded from Dapper) asus p5gd2 premium mobo Note: when I installed Dapper, I had to specify ACPI=off as a kernel parameter in order to be able to boot. The acpi=force and lapic parameters don 't work, then the system hangs at boot. I attached the logs that were asked in one of the first posts. I 'm very eager to test new suggestions out, as this problem has kept me busy for the past weeks... thanks in advance ! ** Attachment added: my logs http://librarian.launchpad.net/5652348/wimm.tar.gz -- Power down after shutdown does not work... https://launchpad.net/bugs/43961 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
