I too just ran into this bug this morning! My system did not require a
reboot, though I did restart my myth TV backend as a precaution.
(System still up and running now, for what it's worth.)
uname -a:
Linux Mythtery 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC
2009 x86_64 GNU/Linux
I will attach the dmesg log and lspci logs as requested.
~$ sudo mdadm --query --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Thu Mar 26 12:16:36 2009
Raid Level : raid1
Array Size : 14651136 (13.97 GiB 15.00 GB)
Used Dev Size : 14651136 (13.97 GiB 15.00 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Apr 6 10:42:47 2009
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
UUID : 30e55caa:7b37846c:2f942441:c20bfe15
Events : 0.121
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 17 1 active sync /dev/sdb1
2 8 1 2 active sync /dev/sda1
3 8 49 3 active sync /dev/sdd1
~$ sudo mdadm --query --detail /dev/md1
/dev/md1:
Version : 00.90
Creation Time : Thu Mar 26 12:19:24 2009
Raid Level : raid5
Array Size : 2883386112 (2749.81 GiB 2952.59 GB)
Used Dev Size : 961128704 (916.60 GiB 984.20 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Apr 6 09:02:59 2009
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 40b52493:7870492f:792c47d7:3ad308e9
Events : 0.48
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
~$ sudo blkid
/dev/sda1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid"
/dev/sda2: TYPE="swap" UUID="1bb03a5b-012d-43cf-a23b-1bcc191f1210"
/dev/sda3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid"
/dev/sdb1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid"
/dev/sdb2: TYPE="swap" UUID="54be76a6-fdfa-4534-a57b-a011320797d2"
/dev/sdb3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid"
/dev/sdc1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid"
/dev/sdc2: TYPE="swap" UUID="8e18c25c-8b70-4621-9886-faf06e947c07"
/dev/sdc3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid"
/dev/sdd1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid"
/dev/sdd2: TYPE="swap" UUID="af25dc05-12af-429d-91bd-5f1058ddf92f"
/dev/sdd3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid"
/dev/md0: UUID="5c27feed-09cc-4233-9d27-282f5d6b787c" TYPE="ext3"
/dev/md1: UUID="07a45363-1129-49df-a054-b34a44f50695" TYPE="jfs"
There was hard drive activity when this happened, but not a TON going
on. (Just watching TV.) I've pounded these disks a LOT harder when
transcoding, for example.
If there is anything else you guys need/want, feel free to let me know!
(Especially since the system has NOT been rebooted!)
** Attachment added: "Dmesg output"
http://launchpadlibrarian.net/24876455/dmesg.log
--
BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948]
https://bugs.launchpad.net/bugs/348218
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
