From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner
Date: Thu, 24 Jan 2013 20:21:21 +0100 [thread overview]
Message-ID: <510189B1.606@fold.natur.cuni.cz> (raw)
In-Reply-To: <51016937.1020202@googlemail.com>
Hi Chris,
try to include in kernel only acpiphp and omit pciehp. Don't use modules but include
them statically. And try, in addition, check whether "pcie_aspm=off" in grub.conf helped.
The best would if you subscribe to linux-pci, and read my recent threads
about similar issues I had with express cards with Dell Vostro 3550. Further, there is
a lot of changes to PCI hotplug done by Yingahi Liu and Rafael Wysockij, just browse the
archives of linux-pci and see the pacthes and the discussion.
Martin
Chris Clayton wrote:
> Hi,
>
> I've today taken delivery of a WinTV-HVR-1400 expresscard TV Tuner and got an Oops when I removed from the expresscard slot in my laptop. I will quite understand if the response to this report is "don't do that!", but in that case, how should one remove one of these cards?
>
> I have attached three files:
>
> 1. the dmesg output from when I rebooted the machine after the oops. I have turned debugging on in the dib700p and cx23885 modules via modules options in /etc/modprobe.d/hvr1400.conf;
>
> 2. the .config file for the kernel that oopsed.
>
> 3. the text of the oops message. I've typed this up from a photograph of the screen because the laptop was locked up and there was nothing in the log files. Apologies for any typos, but I have tried to be careful.
>
> Assuming the answer isn't don't do that, let me know if I can provide any additional diagnostics, test any patches, etc. Please, however, cc me as I'm not subscribed.
>
> Chris
next prev parent reply other threads:[~2013-01-24 19:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 17:02 Chris Clayton
2013-01-24 19:21 ` Martin Mokrejs [this message]
2013-01-26 20:54 ` Chris Clayton
2013-01-26 21:14 ` Martin Mokrejs
2013-01-27 9:57 ` Chris Clayton
2013-01-27 2:45 ` Yijing Wang
2013-01-27 11:19 ` Chris Clayton
2013-01-27 12:18 ` Yijing Wang
2013-01-27 13:37 ` Chris Clayton
2013-01-27 14:26 ` Martin Mokrejs
2013-01-27 15:34 ` Chris Clayton
2013-01-27 16:41 ` Martin Mokrejs
2013-01-27 22:53 ` Chris Clayton
2013-01-27 23:21 ` Martin Mokrejs
2013-01-28 2:40 ` Yijing Wang
2013-01-28 10:12 ` Chris Clayton
2013-01-28 10:56 ` Martin Mokrejs
2013-01-28 11:01 ` Chris Clayton
2013-01-28 11:15 ` Yijing Wang
2013-01-28 10:58 ` Yijing Wang
2013-01-28 11:23 ` Chris Clayton
2013-01-28 12:12 ` Martin Mokrejs
2013-01-28 12:26 ` Yijing Wang
2013-01-28 19:11 ` Chris Clayton
2013-01-28 21:02 ` Martin Mokrejs
2013-01-31 12:09 ` Chris Clayton
2013-01-31 13:05 ` Martin Mokrejs
2013-03-06 23:45 ` Bjorn Helgaas
2013-03-07 16:28 ` Chris Clayton
2013-03-07 17:30 ` Bjorn Helgaas
2013-03-07 20:21 ` Chris Clayton
2013-03-08 0:39 ` Bjorn Helgaas
2013-03-08 10:44 ` Chris Clayton
2013-03-08 22:57 ` Bjorn Helgaas
2013-03-09 9:20 ` Chris Clayton
2013-03-12 22:20 ` Bjorn Helgaas
2013-03-15 22:48 ` Bjorn Helgaas
2013-03-19 15:46 ` Chris Clayton
2013-04-01 17:28 ` Bjorn Helgaas
2013-07-09 9:35 ` Chris Clayton
2013-07-09 20:19 ` Bjorn Helgaas
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=510189B1.606@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.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®