Public bug reported:
Updated 8.04 base to latest today, have been running it for a while and
enabled compiz fusion. Once I launch KVM with my Windows XP VM and then
start using heavy I/O it will crash X11. I dont even have to be moving
the mouse or any windows, effects, etc it will just crash
Disabling Compiz Fusion entirely through Ubuntu - Appearance set to none
fixes the problem obviously but it would be nice to use an accelerated
desktop.
KVM run options:
kvm -localtime -net nic,macaddr=DE:AD:BE:EF:10:27 -net tap -smp 2 -m 1024 -usb
/var/kvm/windows-xp.img
--
FGLRX with compiz
*** This bug is a duplicate of bug 172715 ***
https://bugs.launchpad.net/bugs/172715
Possible dupe of 172715
** This bug has been marked a duplicate of bug 172715
[hardy] Xorg crash
--
FGLRX with compiz fusion and KVM XP crashes X11
https://bugs.launchpad.net/bugs/221162
You received
ogc, we both have (II) AIGLX: Suspending AIGLX clients for VT switch in our
xorg log output at the end.. interesting?
attached mine
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/13841131/Xorg.0.log.old
--
[hardy] Xorg crash
https://bugs.launchpad.net/bugs/172715
You
please see my possible duplicate report, may be helpful in repro:
https://bugs.launchpad.net/ubuntu/+bug/221162
--
[hardy] Xorg crash
https://bugs.launchpad.net/bugs/172715
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hardy Alpha 5 (fresh install cd + online update) + xen + fglrx fails with the
same errors above. sources 2.6.24 xen
I re installed with Gutsy (fresh install cd) + xen + fglrx and I get the same..
** shrugs..
--
[Gutsy] binary graphics drivers don't load with linux-image-2.6.22-14-xen
I should experiment with my 4 disk raid 5 array disconnected. It's the
one that has half SATA and half PATA drives as well. We have pretty much
the same setup, and I mean I just formatted my drive and installed Gutsy
so it's probably not just us.
--
Boot with Software Raid most times causes
*** This bug is a duplicate of bug 139802 ***
https://bugs.launchpad.net/bugs/139802
I just tried the solution in the dup bug
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/139802
It looks like /usr/share/mdadm/mkconf /etc/mdadm/mdadm.conf is
detecting an array I dont have from
I think I figured out why we both have this bug, please read
https://bugs.launchpad.net/ubuntu/+bug/140854
--
long bootup, dmesg full of md: array md1 already has disks!
https://bugs.launchpad.net/bugs/139802
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 139802 ***
https://bugs.launchpad.net/bugs/139802
I can confirm this fixed it, but I think it's still a bug in the mdadm
tool or udev that handles it poorly
1. Use mdadm -E /dev/sdX1 and mdadm -E /dev/sdX device to examine the UUIDs of
the raid array. One
Public bug reported:
Since Feisty when I implemented this raid configuration mdadm does not
always boot correctly even though it seems setup perfectly. I just did a
format and install of fresh Gutsy and it still is doing it. Right during
early boot the status bar will start to load and gets about
I just noticed the mdadm.conf I posted doesnt match my drive
configuration and I dont think it's using it since all the UUIDs are on
the partition tables. In feisty I had this file setup correctly and it
made no difference. (this is what gutsy setup for me)
My drive ids as mapped to the above cat
** sighs (one more correction)
The second UUID set are all the same (poor copy n paste):
[EMAIL PROTECTED]:~$ sudo mdadm -E /dev/sdh1 | grep UUID
UUID : 9c2534ac:1de3420b:e368bf24:bd0fce41
[EMAIL PROTECTED]:~$ sudo mdadm -E /dev/sdd1 | grep UUID
UUID :
Public bug reported:
On boot the kernels device mapper contiously floods output:
[35923.922369] device-mapper: table: 254:5: striped: Couldn't parse stripe
destination
[35923.922420] device-mapper: ioctl: error adding target to table
[35924.034654] device-mapper: table: 254:5: striped: Couldn't
14 matches
Mail list logo
