Bug#273106: marked as done (cmd64x driver doesn't load properly on ia64)
Your message dated Mon, 18 Oct 2004 12:49:49 +0900
with message-id <20041018034948.GC16260@wildopensource.com>
and subject line Bug#273106: cmd64x driver doesn't load properly on ia64
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Sep 2004 23:12:02 +0000
>From lieb@wildopensource.com Thu Sep 23 16:12:02 2004
Return-path: <lieb@wildopensource.com>
Received: from ottawa.wildopensource.com [192.139.46.141]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CAcks-0002nf-00; Thu, 23 Sep 2004 16:12:02 -0700
Received: from projects.wildopensource.com (dsl081-061-247.sfo1.dsl.speakeasy.net [64.81.61.247])
by ottawa.wildopensource.com (Postfix) with ESMTP id 80FB432822F;
Thu, 23 Sep 2004 19:12:00 -0400 (EDT)
Received: from dh3.suntan.fremont.ca.us (unknown [192.168.2.23])
by projects.wildopensource.com (Postfix) with ESMTP
id 40EB22C2A49; Thu, 23 Sep 2004 19:20:28 -0400 (EDT)
From: Jim Lieb <lieb@wildopensource.com>
Organization: Wild Open Source Inc.
To: submit@bugs.debian.org
Subject: cmd64x driver doesn't load properly on ia64
Date: Thu, 23 Sep 2004 16:11:47 -0700
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200409231611.47508.lieb@wildopensource.com>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: kernel-source-2.4.27
This bug appears in the kernel-image-2.4.27-1-itanium_2.4.27-3_ia64.deb
package although the .udeb derived from this package does work.
The CDROM drive, using cmd64x does not properly install. I have traced
the problem on an HP rx2600 dual Itanium server to the following:
1. ide-cd installs followed by ide-detect. This causes ide_scan_pcidev
to start its scan. The CMD649 device (0x1095:0x649) is noted in
the scan but the cmd64x probe function (cmd64x_init_one) is not
called.
2. cmd64x is loaded and its init function is called which does call
the probe function (pre_init == 0). The console reports the IDE
controller at PCI slot ... thru the ide0 and ide1 lines with the
dma and BIOS settings (hd[a-d]:pio). There are no messages
reporting the CDROM drive itself.
/proc/modules shows all of the modules loaded but /proc/ide only
has the files drivers and cmd64x. The subdirs ide[01] and the
symlinks hd[a-d] are not present. Access of the device (like mount)
returns a "not a valid device" error.
The udeb works on the install kernel because the cmd64x driver
seems to get loaded first. I also reproduced this in a running
system by loading re-compiled modules (with added printk's...) in that
order. Others have reported correct loading on their running
systems as well. Once I rebooted my system the same error
behavior I saw in the stage 2 booted kernel appeared.
In looking at the changelog for kernel-source, I note that patch
070_ide_scan_pcibus.diff was a missing patch on an earlier
rev. Might there be more to this patch? Given the two slightly
different paths to and thru the init_one function, this seems to be
an issue in the pci layer somewhere although it may be triggered
by the cmd64x.
Note that this is not a problem with either the 2.4.25 or 2.6.8-1
kernels. Also, although I could unload all of the ide modules in
the earlier (-1) kernel, I can't unload cmd64x (busy) and ide-core
(also busy because of cmd64x).
I've looked at stock kernels for 2.4.27 and 2.4.28 and don't see these
patches so I don't know their origin.
Regards,
Jim
--
*************
Jim Lieb Wild Open Source Inc.
lieb@wildopensource.com Cell: 831.295.9317
Office: 831.421.0883 Fax: 831.421.0885
---------------------------------------
Received: (at 273106-done) by bugs.debian.org; 18 Oct 2004 05:47:17 +0000
>From horms@koto.vergenet.net Sun Oct 17 22:47:17 2004
Return-path: <horms@koto.vergenet.net>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CJQMW-0004YN-00; Sun, 17 Oct 2004 22:47:17 -0700
Received: (qmail 8216 invoked by uid 7100); 18 Oct 2004 05:34:15 -0000
Resent-From: horms@verge.net.au
Resent-Date: Mon, 18 Oct 2004 13:00:00 +0900
Resent-Message-ID: <20041018040000.GD16260@verge.net.au>
Resent-To: lieb@wildopensource.com, 273106-done@bugs.debian.org, dannf@hp.com,
tfheen@debian.org
Date: Mon, 18 Oct 2004 12:49:49 +0900
From: Horms <horms@debian.org>
To: Jim Lieb <lieb@wildopensource.com>, 273106-done@bugs.debian.org
Cc: dann frazier <dannf@hp.com>, tfheen@debian.org
Subject: Re: Bug#273106: cmd64x driver doesn't load properly on ia64
Message-ID: <20041018034948.GC16260@wildopensource.com>
References: <[🔎] 200410161138.17969.lieb@wildopensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 200410161138.17969.lieb@wildopensource.com>
X-Cluestick: seven
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 273106-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
On Sat, Oct 16, 2004 at 11:38:17AM -0700, Jim Lieb wrote:
[snip]
> Note: although the bug was filed against the kernel-source-2.4.27
> package, the fix itself is to prebaseconfig.
>
> The patch has been committed in r23155. Close this bug.
Done :)
--
Horms
Reply to: