BUG: unable to handle kernel NULL pointer dereference at 00000008
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
karmic always crash when channel scan with leadtek dtv dongle h (every dvb player , like me tv , kaffeine etc.)
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x96400000 irq 22'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 22
Simple ctrls : 13
Date: Sun Nov 1 20:01:59 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: TOSHIBA Satellite A300
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel NULL pointer dereference at 00000008
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 11/24/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.70
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Satellite A300
dmi.product.
dmi.sys.vendor: TOSHIBA
summary: |
- leadtek dtv dongle channel scan + BUG: unable to handle kernel NULL pointer dereference at 00000008 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 429662, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.