lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo4x8pb7J8MnokXiFTE=01-TffCk6CKC0VS7CEf3X1bSBw@mail.gmail.com>
Date:	Wed, 6 Mar 2013 16:45:43 -0700
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Chris Clayton <chris2553@...glemail.com>
Cc:	Martin Mokrejs <mmokrejs@...d.natur.cuni.cz>,
	Yijing Wang <wangyijing@...wei.com>,
	Yijing Wang <wangyijing0307@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org
Subject: Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

On Thu, Jan 31, 2013 at 5:09 AM, Chris Clayton <chris2553@...glemail.com> wrote:

> My usb3 expresscard device has arrived and I get an oops with that too, if I
> remove it without unloading the driver first. I guess it shouldn't be a
> surprise that the driver isn't expecting the device to disappear.
>
> As I mentioned, I have some trouble with the WinTV-HVR-1400 card, which
> sometimes pops out again, if I push it into the slot too hard (but I'm
> geeting better at that with practice). So what I've done (with the usb3 card
> too) to avoid the oopsen is blacklist the driver in
> /etc/modprobe.d/blacklist.conf and then load them when I'm sure the card is
> properly inserted. Not exactly hotplug, but at least I don't have to reboot
> because of an oops- and it's not something I'm doing several times an hour.

Hi Chris,

What's the current state of this?  It sounds to me like it still
doesn't work out of the box.  Having to blacklist the driver and load
it manually is a completely unacceptable user experience.  If you have
to manually choose acpiphp over pciehp, that is also unacceptable.

So if you're still limping along with hacky workarounds like this, I'd
like to pursue this more and see if we can't figure out a better
solution.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ