Bug 54961
| Summary: | cx23885_sram_channel_dump oops when removing HVR-1400 ExpressCard | ||
|---|---|---|---|
| Product: | v4l-dvb | Reporter: | Bjorn Helgaas (bjorn) |
| Component: | cx88 | Assignee: | v4l-dvb_cx88 |
| Status: | RESOLVED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | chris2553, szg00000 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://lkml.kernel.org/r/51016937.1020202@googlemail.com | ||
| Kernel Version: | 3.8.0-rc4+ | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | manual transcription of oops from photo | ||
Please try this bug with latest kernel image. On 09/11/16 19:36, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=54961 > > Szőgyényi Gábor <szg0000@freemail.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |szg0000@freemail.hu > > --- Comment #1 from Szőgyényi Gábor <szg0000@freemail.hu> --- > Please try this bug with latest kernel image. > Sorry, I no longer have the hardware to test this. I'm closing this as "insufficient data" because I don't think we have enough information to make progress. Please reopen if you can help debug this. |
Created attachment 94841 [details] manual transcription of oops from photo Chris Clayton reported (see URL above) an oops when removing a WinTV-HVR-1400 ExpressCard. His complete transcription of the oops is attached; here's the part that seems most important: BUG: unable to handle kernel NULL pointer dereference at 00000058 IP:[<f8e52365>] cx23885_video_wakeup+0x25/0x130 [cx23885] Call Trace: [<f8e547eb>] ? cx23885_sram_channel_dump+0x20b/0c220 [cx23885] [<f8e52d13>] ? cx23885_video_irq+0xf3/0x1c0 [cx23885] [<f8e575db>] ? cx23885_irq+0x39b/0x7e0 [cx23885] [<c12b90a4>] ? ahci_interrupt+0x1b4.0x650 [<c104ddbc>] ? hrtimer_forward+0x9c/0x190 [<c108425e>] ? handle_irq_event_percpu+0x2e/0x140 [<c106f9f5>] ? clockevents_program_event+0xa5/0x160 [<c10843a5>] ? handle_irq_event+0x34/0x60 [<c1086d46>] ? handle_fasteoi_irq+0x46/0xd0 [<c100489f>] ? handle_irq+0x8f/0xa0 [<c100449a>] ? do_IRQ+0x3d/0xc0 [<c1036524>] ? irq_exit+0x54/0x90 [<c1020828>] ? smp_apic_timer_interrupt+0x58/0x90 [<c140c66c>] ? common_interrupt+0x2c/0x31 I suspect this oops could be avoided by unbinding the driver before removing the ExpressCard, but that's really just a workaround. We shouldn't crash or hang the box even if the user removes an ExpressCard without shutting it down.