I recently performed a clean install of Fedora 12 on my Sager 8890.
I backed up my /home dir beforehand using rsync without any problems to an external 320G USB drive.
With F12 installed, I proceeded to restore my /home dir using rsync again.
The script works fine--it's been tested through previous installs without issue.
The symptom:
Hello everyone, it seem like a good idea to leave the computer along when it is updating. Because if for some reason I still using the computer, it might interrupt the updating process.(e.g. update manager freeze, or corrupt some file) I remember I run into this problem quite a few times back in FC6, but did not have problem on F10 and F11(merging from preview?) until the day before yesterday.
Code:
Dec 12 17:01:04 editheraven-T-Systems-PC-P5LD2-VM kernel: [ 6048.992065] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 12 17:01:04 editheraven-T-Systems-PC-P5LD2-VM kernel: [ 6048.992075] sr 0:0:0:0: [sr0] CDB: Write(10): 2a 00 00 00 00 d9 00 00 1f 00
Dec 12 17:01:04 editheraven-T-Systems-PC-P5LD2-VM kernel: [ 6048.992094] ata1.00: cmd a0/01:00:00:00:f8/00:00:00:0
I've installed CentOS 5.3 in a new machine....but i got these errors when kernel is loadingata1.00 exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0ata1.00 BMDMA s... [by fercho_aml]
I have found that my server's filesystem is continuously entering read-only mode. There have been some issues with the raid1 array, but I have removed the bad disk from the array. However, it is still physically plugged into the system because I haven't had a chance to go over to the datacentre, I suspect udev and the system kernel is still picking up the bad disk and throwing errors.
Hello,
For a while now (at least since 11.10, I think) I was troubled by long boot times in Ubuntu.
A few seconds in, the boot process just hangs for ~30s before continuing normally.
With dmesg I could pinpoint the hang to this lines:
Code:
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: failed command: IDENTIFY PACKET DEVICE
Finally I found out what's the cause:
Here's a stripped copy of my kernel.log (where the TV card initializes and renders the system unusable).Aug 19 03:02:05 localhost kernel: [ 3.158828] Linux video capture interface: v2.00
Aug 19 03:02:05 localhost kernel: [ 3.199174] nvidia: module license 'NVIDIA' taints kernel.
Aug 19 03:02:05 localhost kernel: [ 3.199178] Disabling lock debugging due to kernel taint
Aug 1
Hi,I have a new Thinkpad 420 with 80GB Intel SSD 310. I installed arch on this SSD.
I have noticed some error during the Linux boot. They seem to continue to occur after the boot adding lines to the log every few seconds. Once booted this normally does not appear to be causing any problems. However, around 1 in 10 boots results in a kernel panic and the computer has on two or three occasions suddenly rebooted after being powered on for a number of hours.