Bug 470215 - [Regression] Oops: comm: ipolldevd Not tainted
Summary: [Regression] Oops: comm: ipolldevd Not tainted
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
: 473346 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2008-11-06 10:08 UTC by Mamoru TASAKA
Modified: 2009-11-28 10:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-11-28 10:22:57 UTC
Type: ---

Attachments (Terms of Use)
dmesg (36.34 KB, text/plain)
2008-11-06 10:08 UTC, Mamoru TASAKA
no flags Details
dmesg of -109.fc10 (36.72 KB, text/plain)
2008-11-16 13:23 UTC, Mamoru TASAKA
no flags Details

System ID Private Priority Status Summary Last Updated
Linux Kernel 12047 0 None None None Never

Description Mamoru TASAKA 2008-11-06 10:08:15 UTC
Created attachment 322685 [details]

Description of problem:
On Toshiba TX/3516LDSW laptop I see the oops attached
(on init 3)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. reboot with init 3 (no rhgb)
Actual results:
See attached

Additional info:
I don't know if this is related to this, however
with init 5 X window is completely black and after that
I cannot even shut down cleanly.

Comment 1 Mamoru TASAKA 2008-11-06 16:11:56 UTC
(X issue does not related here)

This seems a regression by the fix for bug 437091.
The patch on 
seems to work for me. I don't know if this patch is already merged into
git tree.

Comment 2 Mamoru TASAKA 2008-11-16 13:23:11 UTC
Created attachment 323718 [details]
dmesg of -109.fc10

dmesg of, still oops happens.

Comment 3 Mamoru TASAKA 2008-11-18 07:59:06 UTC
By the way patch is:

Comment 4 Bug Zapper 2008-11-26 04:52:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:

Comment 6 Mamoru TASAKA 2009-01-28 19:03:33 UTC
If 2.6.27 support on F-10 gets longer, I appreciate it if
the two patches in my comment 5 are applied to Fedora kernel.

Actually this issue was caused by bug 437091
(i.e. Patch2012: linux-2.6-toshiba-acpi-update.patch ) and
the above patches are already in 2.6.28.

Comment 7 Chuck Ebbert 2009-01-31 02:10:40 UTC
Fixed in

Comment 8 Mamoru TASAKA 2009-02-11 15:34:08 UTC
Rebooted with and seems fine,
thank you!

Comment 9 Chuck Ebbert 2009-02-16 22:49:42 UTC
Release candidate kernel is in updates.testing now.

Comment 10 Chuck Ebbert 2009-02-16 22:50:30 UTC
*** Bug 473346 has been marked as a duplicate of this bug. ***

Comment 11 Bug Zapper 2009-11-18 07:47:16 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 12 Mamoru TASAKA 2009-11-28 10:22:57 UTC

Note You need to log in before you can comment on or make changes to this bug.