From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932442AbbCIU5G (ORCPT ); Mon, 9 Mar 2015 16:57:06 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:36569 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932258AbbCIU5D (ORCPT ); Mon, 9 Mar 2015 16:57:03 -0400 Date: Mon, 9 Mar 2015 21:57:01 +0100 From: Pavel Machek To: One Thousand Gnomes Cc: kernel list , linux-pcmcia@lists.infradead.org, axboe@kernel.dk Subject: Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot Message-ID: <20150309205701.GA11115@amd> References: <20150227230852.GA21721@amd> <20150302115725.53baae2f@lxorguk.ukuu.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150302115725.53baae2f@lxorguk.ukuu.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote: > On Sat, 28 Feb 2015 00:08:52 +0100 > Pavel Machek wrote: > > > Hi! > > > > It seems that pcmcia was unhappy even before, but eject definitely > > oopsed it. I meant "the dmesg indicated 'interesting stuff'". > > Any ideas? > > Probably a PCMCIA not a block layer change - well I guess could be > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for > pure PCI boxes so it didn't do various bad things. Unfortunately, it happened just once :-(. I'll scream if it happens again. > Do you have any other I/O port based PCMCIA device you can insert/eject > in that machine ? I should have cf bluetooth somewhere, but I doubt I can find it... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html