Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261822AbVCYVtE (ORCPT ); Fri, 25 Mar 2005 16:49:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261823AbVCYVtE (ORCPT ); Fri, 25 Mar 2005 16:49:04 -0500 Received: from fire.osdl.org ([65.172.181.4]:62887 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261822AbVCYVs5 (ORCPT ); Fri, 25 Mar 2005 16:48:57 -0500 Date: Fri, 25 Mar 2005 13:49:03 -0800 From: Andrew Morton To: Steven Cole Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK) Message-Id: <20050325134903.6862718f.akpm@osdl.org> In-Reply-To: <4244812C.3070402@mesatop.com> References: <20050325002154.335c6b0b.akpm@osdl.org> <42446B86.7080403@mesatop.com> <424471CB.3060006@mesatop.com> <20050325122433.12469909.akpm@osdl.org> <4244812C.3070402@mesatop.com> X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 38 Steven Cole wrote: > > >> > >> I found a few more minutes to test two more kernels. The problem > >> first occured with 2.6.12-rc1-mm2: > >> > >> 2.6.12-rc1 reads the cd-rom OK as reported earlier > >> 2.6.12-rc1-mm1 also reads the cd-rom OK > >> 2.6.12-rc1-mm2 broken same as -mm3 described as above > >> 2.6.12-rc1-mm3 broken as reported earlier > > > > > > Are you really really sure about that? -mm3 included both the bk-ide-dev > > tree and the isofs changes. 2.6.12-rc1-mm2 had neither. > > > > Just to be really really sure, I repeated the tests. I even checked > that the image/label combination in /etc/lilo.conf was what I intended, > but the uname -r should show what's what. > > Same results, -mm2 broken, and -mm1 reads the disk. I even tried > other CD's just to make sure I didn't have something weird. Same results. OK, thanks. It would be interesting to copy a CD to hard disk (under -mm1) and see if it works OK with the loopback driver. Also, boot into -mm2 and do a `cmp' of the cdrom with the image which is on hard-disk. This should help us work out whether it's isofs, the driver, the VFS or whatever. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/