Most recent kernel where this bug did not occur: None - tried with gentoo-sources 2.6.14 2.6.15-r1/r7 and 2.6.16-r1 Also tested with kernel.org 2.6.16 All have the same problem Distribution: Gentoo Linux Hardware Environment: HP nc4200 laptop - BIOS rev F.08 02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller Subsystem: Hewlett-Packard Company Unknown device 0938 Flags: bus master, medium devsel, latency 168, IRQ 18 Software Environment: Gentoo Linux 2.6.14/15/16 Kernel Problem Description: An incorrect PCI device ID is reported for any Cardbus card inserted into the cardbus slot. Cisco wifi card - Atheros chipset lspci -v reports (on HP nc4200) 03:00.0 Ethernet controller: Unknown device 068c:0013 (rev 01) for comparison purposes on a Dell Latitude D600 lspci -vn reports device ID of 168c:0013 as designed similar result with a Zyxel Wifi card (prism54) on HP nc4200, lspci -v reports 03:00.0 Network controller: Unknown device 0260:3890 (rev 01) on Dell D600, reports 1260:3890 as designed Steps to reproduce: Get an HP nc4200 ;-) compile kernel with yenta + cardbus support (modules or inbuilt) insert cardbus card lspci -vn
Created attachment 7681 [details] dmesg output
Created attachment 7682 [details] lspci output
Reply-To: matthew@wil.cx On Sun, Mar 26, 2006 at 02:35:34PM -0800, bugme-daemon@bugzilla.kernel.org wrote: > Problem Description: > > An incorrect PCI device ID is reported for any Cardbus card inserted into the > cardbus slot. > > Cisco wifi card - Atheros chipset > > lspci -v reports (on HP nc4200) > > 03:00.0 Ethernet controller: Unknown device 068c:0013 (rev 01) > > for comparison purposes on a Dell Latitude D600 lspci -vn reports device ID of > 168c:0013 as designed > > similar result with a Zyxel Wifi card (prism54) > > on HP nc4200, lspci -v reports > > 03:00.0 Network controller: Unknown device 0260:3890 (rev 01) > > on Dell D600, reports 1260:3890 as designed To be honest, this looks like a hardware problem -- a line shorted to 0. Can you test with, er, an entirely different OS? Maybe one of the BSDs if you can't stomach a M$ OS.
Created attachment 7683 [details] Kernel .config
I'd be suspecting you have a busted machine - bad connector, broken pin, blown IO buffer, etc.
You're right... I checked with a bootable windows CD (Bart PE), the PCI vendor/device ID was reported wrong there too. Hardware problem, please close the bug report - my apologies. James