sysfs reports invalid vendor id for firewire device

Bug #601161 reported by Marc Tardif on 2010-07-02
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Low
Seth Forshee

Bug Description

I'm running the latest update of Maverick on a Toshiba Tecra A10 laptop and I'm noticing the following entry in the lspci -vvnn output:

05:0b.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04) (prog-if 10)
        Subsystem: Toshiba America Info Systems Device [1179:0001]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (500ns min, 1000ns max), Cache Line Size: 32 bytes
        Interrupt: pin B routed to IRQ 23
        Region 0: Memory at c8001000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: <access denied>
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire-ohci, ohci1394

The problem is that the vendor reported here does not seem to be the same as reported in the sysfs:

$ cat /sys//devices/pci0000:00/0000:00:1e.0/0000:05:0b.1/fw0/vendor
0xd00d1e

I would expect sysfs to report the same information as lspci.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-6-generic 2.6.35-6.9
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1405 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xca100000 irq 47'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,11790602,00100003 HDA:11c11040,11790001,00100200'
   Controls : 13
   Simple ctrls : 8
Date: Fri Jul 2 14:22:31 2010
HibernationDevice: RESUME=UUID=1dc40473-5291-49a3-b23f-c697220b3a56
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100702)
MachineType: TOSHIBA TECRA A10
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic root=UUID=decc3bae-46c8-4995-bf9c-c671a7d393e7 ro rootdelay=60 quiet splash initcall_debug
ProcEnviron:
 LC_CTYPE=en_CA.UTF-8
 LANG=en_US
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.37
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 08/08/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.50
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.50:bd08/08/2008:svnTOSHIBA:pnTECRAA10:pvrPTSB0C-00Q00S:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A10
dmi.product.version: PTSB0C-00Q00S
dmi.sys.vendor: TOSHIBA

Marc Tardif (cr3) wrote :

Confirmed; this device would usually show up as 0832:1180:0001:1179, Vendor "Ricoh Co Ltd", Product "R5C832 IEEE 1394 Controller".

However, I am not certain it belongs to kernel, however I am not sure where else it would be. It certainly doesn't seem to have to do with udev, AFAICT.

Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
tags: added: needs-reassignment
tags: added: pcert

This seems to be related to the addition of the "firewire" type of bus recently; the device would usually just be reported as a device on "pci" bus.

Seth Forshee (sforshee) wrote :

This report is against an early alpha kernel. Does the bug still exist in the latest kernel?

Changed in linux (Ubuntu):
assignee: nobody → Seth Forshee (sforshee)
status: Confirmed → Incomplete

This behaviour still exists in the latest kernel.

However, the IDs reported on the FireWire bus are not PCI IDs but FireWire IDs, which are 24-bit IEEE OUIs.
0xd00d1e is the correct vendor ID for Linux.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers