[Bug 199812] ACPI: Unable to turn cooling device [ffff81007ffa6810] 'on' is spewed repeatedly on the console
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=199812
--- Comment #21 from John Guthrie <guthrie(a)counterexample.org> 2009-04-17 16:09:07 EDT ---
It's baaack....
leibniz_1001% rpm -q kernel
kernel-2.6.27.5-117.fc10.i686
kernel-2.6.27.21-170.2.56.fc10.i686
leibniz_1002% uname -a
Linux leibniz 2.6.27.21-170.2.56.fc10.i686.PAE #1 SMP Mon Mar 23 23:24:26 EDT
2009 i686 athlon i386 GNU/Linux
leibniz_1003% dmesg | tail -20
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
This seems to be the latest F10 kernel, 2.6.27.21-170.2.56.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 1 month
[Bug 213882] Not calculating space for partitions properly when reusing existing partitions
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=213882
Orion Poplawski <orion(a)cora.nwra.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |RAWHIDE
Flag|needinfo?(orion(a)cora.nwra.c |
|om) |
--- Comment #11 from Orion Poplawski <orion(a)cora.nwra.com> 2009-04-17 16:08:49 EDT ---
Tested with:
part /boot --onpart=sda2 --noformat
part / --fstype ext4 --size=9000 --grow
part /var --fstype ext4 --size=512
part swap --onpart=sda6
part /export --onpart=sda3 --noformat
and space at end of disk. Worked. I'm going to call this fixed.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 1 month
[Bug 207470] Need ability to handle duplicate VG names for Xen
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=207470
--- Comment #16 from Ask Bjørn Hansen <ask(a)develooper.com> 2009-04-17 04:44:18 EDT ---
For the "my xen image is fubar'ed and I need to mess with the data to make it
boot" situation I just realized an obvious-ish work-around: Run a new box with
the rescue image.
Something like
virt-install -n box1b -r 1024 -f /xen/disks/brokendisk -p -l
http://mirrors/5/os/x86_64/ -d --vnc --vcpus=1 -x rescue
...
Anyway, it just saved me a re-install. (Of course the one box that isn't
managed completely by puppet etc was the one to go kaboom).
- ask
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 1 month
[Bug 207470] Need ability to handle duplicate VG names for Xen
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=207470
--- Comment #15 from Ask Bjørn Hansen <ask(a)develooper.com> 2009-04-17 04:13:36 EDT ---
"One potential option that is relatively easy and gets us a little further is
this. Modify vgrename to have a "--force" option on it and allow renames into
duplicate VG names."
Just wanted to second how useful that would be. As others have mentioned,
getting proper "duplicate VG name" handling seems, well, more of a long term
solution.
Just being able to force rename a vg would make it possible to save otherwise
unbootable images without having to copy the image over to a box with a
different vg name...
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 1 month