Hi Brad,
As you say, apport-collect will not run because the entire root
filesystem is mounted read-only. I manually typed out the output of a
few key commands to provide more information, and can do it again if
necessary -- but since I can't cat anything to a file I am having to
hand write all this out.
These two were from inside the unity environment in a terminal.
$cat /proc/mounts
rootfs / rootfs rw 0 0
...
/dev/mapper/ubuntu-root / ext4
ro,noatime,nodiratime,discard,errors=remount-ro,data=ordered 0 0
...
I only put the two lines I think were relevant because autocorrect was
really making this very tedious to copy. It seems to say that root is
ro, unsurprisingly.
$sudo mount -o remount,rw -t ext4 /dev/mapper/ubuntu-root /
[sudo] password for neltnerb:
sudo: unable to open /var/lib/sudo/neltnerb/0: Read-only file system
mount: cannot remount block device /dev/mapper/ubuntu-root read-write, is write
protected
This was my attempt to remount the root filesystem as read-write, which
as best I can tell either failed because sudo couldn't run on a read-
only filesystem, or because of an underlying hardware level issue
preventing the drive from remounting read-write.
Then when I powered off, I saw this in the dmesg area:
EXT4-fs (dm-1): previous I/O error to superblock detected
Buffer I/O error on device dm-1, logical block 0
EXT4-fs error (device dm-1): ext4_find_entry:1209: inode #23593228: comm sh:
reading directory lblock 0
with timestamps before each line, of course. This makes me think
something really messy is going on. I don't know if it's an issue with
my SSD (brand new INTEL SSDSC2CW480A3 (400i) as reported by the disks
utility). SMART tests indicate no problems, although I haven't tried
doing a more rigorous test of the drive. The fact that this error only
shows up on resume from suspend is particularly strange.
My best guess is that there is some hardware interaction between the
SSD, hardware controller, kernel, and mount option setup that is failing
miserably. I would also note that during the time that I was writing
down these errors, I could not log in to a VTTY. My suspicion is
therefore that there is a time delay involved somewhere. I managed to
log in to unity from my locked screen from resume fast enough and open a
terminal quickly enough that it was still sort of working, but by the
time I got to the point of doing stuff even the login command was
broken.
I see nothing odd in /var/log for dmesg, pm-suspend, etc, but I might
not know exactly what file might show bad behavior. I am skeptical that
it would show much anyway given that the filestystem seems to have been
set to read only at a level lower than the userspace mount command...
In any case, I will mark as "confirmed" as instructed and hope that this
amount of information is sufficient to explain the issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092928
Title:
asus ul30a resume broken very badly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092928/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
