Bug 213745 - kernel bug
Summary: kernel bug
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 6
Hardware: i386 Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-02 20:29 UTC by Stefan Soderberg
Modified: 2008-01-08 00:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-08 00:29:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
message from syslogd (6.75 KB, text/plain)
2006-11-02 20:29 UTC, Stefan Soderberg 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Stefan Soderberg 2006-11-02 20:29:34 UTC 
Description of problem:

Message from syslogd, error message from kernel - see attachment.

System does not crash but I'm about to use Fedora 6 on a PC with an ASUS P5B
motherboard (Intel P965 chipset) and an Intel Duo processor for running
applications for my customers => pretty urgent issue for me.

cheers
Stefan
Comment 1 Stefan Soderberg 2006-11-02 20:29:35 UTC 
Created attachment 140179 [details]
message from syslogd
Comment 2 Jon Stanley 2007-12-31 21:50:27 UTC 
Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!
Comment 3 Jon Stanley 2008-01-08 00:29:35 UTC 
Closing per previous comment.  If you can provide the requested information,
please feel free to re-open this bug.
Note You need to log in before you can comment on or make changes to this bug.