[Bug 239756] fsck.hfsplus segfaults
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=239756
Joe Bayes <jbayes(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbayes(a)gmail.com
--- Comment #11 from Joe Bayes <jbayes(a)gmail.com> 2009-08-10 02:44:22 EDT ---
I can also still reproduce this with Fedora 10. Could somebody please reopen
it?
--
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.
14 years, 1 month
[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
faith <faithinfamilies(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |faithinfamilies(a)yahoo.com
--- Comment #37 from faith <faithinfamilies(a)yahoo.com> 2009-08-08 05:27:05 EDT ---
my Compaq Presario s6500nx has been stuck at 'loading' fc11 for a month now
(soon after upgrade) with just the heavy white line across the bottom. been
using dell d600 meanwhile, but really need to get this one working again.
linux newbie here, just figured out to hit 'esc' and I see now it appears
'hung' with perpetual ...
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
(never stops this; won't boot)
h-e-l-p-!! please say how/where to edit what, remember I'm green - thanks much
--
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.
14 years, 1 month
[Bug 346271] halt initscript does not properly handle apcupsd shutdowns
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=346271
--- Comment #23 from Michal Hlavinka <mhlavink(a)redhat.com> 2009-08-07 01:54:09 EDT ---
(In reply to comment #22)
> The apcupsd team is pretty responsive, has anyone tried to open a ticket there?
unfortunately I have different experience :(
> Perhaps a better solution is an additional program to apccontrol, say
> /sbin/apckillpower, which has solely this kill function in it and none of the
> snmp or lm_sensors dependencies. Might be pretty simple to whip up such a new
> program (lots of cutting & pasting).
I'll try to ask them if it'd work and if they are willing to do this
--
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.
14 years, 1 month
[Bug 217038] yaboot partition should be added to fstab during installation
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=217038
Alex Kanavin <ak(a)sensi.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |Reopened
Status|CLOSED |ASSIGNED
Version|6 |11
Resolution|RAWHIDE |
--- Comment #8 from Alex Kanavin <ak(a)sensi.org> 2009-08-06 09:50:38 EDT ---
After some peaceful period, the problem has re-appeared in F11 - yaboot
partition gets mounted if it's on an external drive, which leads to desktop
clutter and kernel update failures. Shouldn't happen.
--
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.
14 years, 1 month
[Bug 346271] halt initscript does not properly handle apcupsd shutdowns
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=346271
Trevor Cordes <trevor(a)tecnopolis.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trevor(a)tecnopolis.ca
--- Comment #22 from Trevor Cordes <trevor(a)tecnopolis.ca> 2009-08-06 00:54:19 EDT ---
"Me too". I've been using similar halt script patches as suggested in apcupsd
docs to make mine work and it *seemed* to work the other day when I had an
extended outage. Of course, the final killpower may have been the UPS actually
hitting its hard battery limit and killing, vs software killing. There was at
least 1-2 mins between when the screen said "will now power off the UPS" and
when it actually shut off (SUA1500). Hmm, this may explain why some (remote)
boxes I administer sometimes don't seem to kick back on after an outage.
Without killpower working you have that pathological case where the power comes
back right when the killpower would have executed.
The apcupsd team is pretty responsive, has anyone tried to open a ticket there?
Perhaps a better solution is an additional program to apccontrol, say
/sbin/apckillpower, which has solely this kill function in it and none of the
snmp or lm_sensors dependencies. Might be pretty simple to whip up such a new
program (lots of cutting & pasting).
Comment #8 (Matt), your extra step to "ensure the machine halts but stays
running until the UPS cuts power" is unnecessary if your BIOS has a "power
after power fail" "always on" option. Your step is only required if your BIOS
only has the "last state" option. In general with UPSs you *always* want the
"always on" option.
--
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.
14 years, 1 month