Bug 393351 - Hauppauge PVR-350 card makes system crash frequently
Hauppauge PVR-350 card makes system crash frequently
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-20 17:40 EST by Nikos Charonitakis
Modified: 2008-02-13 18:54 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-13 18:27:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nikos Charonitakis 2007-11-20 17:40:11 EST
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 18:27:21 EST

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


(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 18:54:27 EST
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...

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