From: Michael Cree <mcree@orcon.net.nz>
To: linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Oops seen in dvb_usb_dib0700 when running 2.6.36-rc3
Date: Mon, 30 Aug 2010 21:47:39 +1200 [thread overview]
Message-ID: <4C7B7E3B.2060205@orcon.net.nz> (raw)
Just got up the courage to try the 2.6.36 series (indeed 2.6.36-rc3) and
saw an oops from the dvb_usb_dib0700 module on startup. This is a
Hauppauge Nova-T 500 card in a Compaq Alpha. Have never seen this when
running 2.6.35 series or prior kernels.
[ 29.259750] dib0700: loaded with support for 15 different device-types
[ 29.261703] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
warm state.
[ 29.261703] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 29.263656] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[ 29.290024] PCI: Setting latency timer of device 0000:01:00.1 to 64
[ 29.374008] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)...
[ 29.416000] MT2060: successfully identified (IF1 = 1217)
[ 29.898422] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 29.899398] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[ 29.910140] DVB: registering adapter 1 frontend 0 (DiBcom 3000MC/P)...
[ 29.916000] MT2060: successfully identified (IF1 = 1226)
[ 30.107406] ieee1394: Host added: ID:BUS[0-00:1023]
GUID[0000303c0009c6d0]
[ 30.423812] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
initialized and connected.
[ 30.423812] Unable to handle kernel paging request at virtual address
0000000000000138
[ 30.423812] modprobe(617): Oops 1
[ 30.423812] pc = [<fffffffc00976d70>] ra = [<fffffffc00976d34>] ps
= 0000 Not tainted
[ 30.423812] pc is at dib0700_probe+0xf0/0x150 [dvb_usb_dib0700]
[ 30.423812] ra is at dib0700_probe+0xb4/0x150 [dvb_usb_dib0700]
[ 30.423812] v0 = 0000000000000010 t0 = 0000000000000000 t1 =
00000000000001f4
[ 30.423812] t2 = 0000000000000000 t3 = 0000000000000000 t4 =
000000000000a9ba
[ 30.423812] t5 = 0000000000000000 t6 = 0000000000000000 t7 =
fffffc003e260000
[ 30.424789] s0 = fffffc003e1ee340 s1 = fffffffc0098a27c s2 =
fffffc003f592000
[ 30.424789] s3 = fffffffc0097c430 s4 = fffffc003e263d38 s5 =
fffffffc0097d368
[ 30.424789] s6 = 0000000120022080
[ 30.424789] a0 = 0000000000000000 a1 = fffffc00010c87a8 a2 =
fffffc003e047a60
[ 30.424789] a3 = fffffffc0031902c a4 = fffffc003e10c068 a5 =
0000000000000000
[ 30.424789] t8 = ffffffffffffffff t9 = 0000000000000000 t10=
0000000000000010
[ 30.424789] t11= 0000000000000000 pv = fffffc00003a3e90 at =
0000000000000003
[ 30.424789] gp = fffffffc00982d42 sp = fffffc003e263ce8
[ 30.424789] Disabling lock debugging due to kernel taint
[ 30.424789] Trace:
[ 30.424789] [<fffffc0000513534>] driver_probe_device+0xa4/0x220
[ 30.425765] [<fffffc00005137ac>] __driver_attach+0xfc/0x100
[ 30.425765] [<fffffc00005125e8>] bus_for_each_dev+0x78/0xd0
[ 30.425765] [<fffffc00005136b0>] __driver_attach+0x0/0x100
[ 30.425765] [<fffffc00005132dc>] driver_attach+0x2c/0x40
[ 30.425765] [<fffffc00005129c8>] bus_add_driver+0xe8/0x350
[ 30.425765] [<fffffc00004783b0>] kobj_bcast_filter+0x0/0xa0
[ 30.426742] [<fffffc0000513bd8>] driver_register+0x78/0x1b0
[ 30.426742] [<fffffc00004783b0>] kobj_bcast_filter+0x0/0xa0
[ 30.426742] [<fffffc0000310088>] do_one_initcall+0x38/0x200
[ 30.426742] [<fffffc000035efdc>] SyS_init_module+0xfc/0x2b0
[ 30.426742] [<fffffc0000310c24>] entSys+0xa4/0xc0
[ 30.426742]
[ 30.427718] Code: a43e0050 205f0001 384101c0 a43e0050 205f01f4
a4211c58 <b0410138> a61e0050
Cheers
Michael.
reply other threads:[~2010-08-30 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C7B7E3B.2060205@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®