Bug 393351

Summary:	Hauppauge PVR-350 card makes system crash frequently
Product:	[Fedora] Fedora	Reporter:	Nikos Charonitakis <nikosx>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8	CC:	chris.brown
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-13 23:27:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikos Charonitakis 2007-11-20 22:40:11 UTC

Description of problem:
I have installed Hauppauge PVR-350 in my system which is based on amd 690G chipset
I have tried both pci slots available. When present this card, my system
completely crashs ( some minutes later or immediately after x login) and needs
hard reset in order to reboot.
Some times failed even to reboot (fails the udev part of boot procedure) so i
turn off power supply and then the system can start again.
So is there any log messages for these crashs? Where i can find them in order to
debug this problem.

Additional info:
i use fglrx Χ driver.

Comment 1 Christopher Brown 2008-02-13 23:27:21 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

(In reply to comment #0)

> Additional info:
> i use fglrx Χ driver.

Unfortunately this is a closed source driver so we cannot debug this issue.
Please use the radeon driver and re-open if this issue still exists for you.
Closing NOTABUG...

Comment 2 Nikos Charonitakis 2008-02-13 23:54:27 UTC

I had in mind to close it. It looks that a bios update or maybe latest kernel
update took away these problems. I didnt full investigate this issue though...