Problem with external firewire disk and new firewire stack in Kubuntu 11.04 and 11.10 beta2

[cIdde]

When I connect my firewire harddisk and switch it on, Kubuntu 11.04 does not recognize it. /var/log/syslog shows these error messages:

[ 2605.289475] firewire_ohci: node ID not valid, new bus reset in progress
[ 2614.797413] firewire_core: skipped bus generations, destroying all nodes
[ 2614.797434] firewire_core: Parent port inconsistency for node 0: parent_count=1
[ 2614.797440] firewire_core: topology build failed

When I then reboot the computer with a live CD of Kubuntu 10.04, the drive works as expected. (Is detected on connection and can be mounted and used via KDE device manager.)

When I then reboot the computer again and boot into the installed Kubuntu 11.04 again, the drive then is also recognized here, too and can be mounted and used normally. Seems to me to be some hardware initialization issue. (When the hardware is initialized correctly by the old firewire stack in Kubuntu 10.04 then it also works in 11.04 afterwards).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: volker 2127 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1371 at 0xd800, irq 16'
   Mixer name : 'SigmaTel STAC9721,23'
   Components : 'AC97a:83847609'
   Controls : 36
   Simple ctrls : 23
Date: Fri Oct 7 21:33:01 2011
HibernationDevice: RESUME=UUID=106d425c-20e1-48e7-97eb-736ac545720f
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
Lsusb:
 Bus 003 Device 002: ID 0c45:613c Microdia PC Camera (SN9C120)
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: American Megatrends Inc. Uknown
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=27a7f421-48d4-4729-999c-acccb7ead2f6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.52
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 Oct 7 21:17:12 freyr kernel: [ 2605.289475] firewire_ohci: node ID not valid, new bus reset in progress
 Oct 7 21:17:22 freyr kernel: [ 2614.797413] firewire_core: skipped bus generations, destroying all nodes
 Oct 7 21:17:22 freyr kernel: [ 2614.797434] firewire_core: Parent port inconsistency for node 0: parent_count=1
 Oct 7 21:17:22 freyr kernel: [ 2614.797440] firewire_core: topology build failed
dmi.bios.date: 10/07/2003
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: K7S8X
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd10/07/2003:svnAmericanMegatrendsInc.:pnUknown:pvr1.0:rvn:rnK7S8X:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: Uknown
dmi.product.version: 1.0
dmi.sys.vendor: American Megatrends Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[cIdde (schiwed)]

Ok, will test upstream kernel. No time for that, now. Will do tomorrow. Thanks so far!

[cIdde (schiwed)]

Ok, now tested with upstream (mainline) kernel: 2.6.38-02063808-generic
Exact same behavior. Drive not recognized in 11.04 with upstream kernel after cold-boot. Reboot into Kubuntu 10.04, drive recognized on connection. Reboot to 11.04 with upstream kernel and drive is now recognized on connection.
Messeges from /var/log/syslog in 11.04 with upstream kernel when drive is recognized after last reboot:

Oct 8 09:58:57 freyr kernel: [ 98.159610] firewire_ohci: node ID not valid, new bus reset in progress
Oct 8 09:59:05 freyr kernel: [ 106.618107] firewire_core: skipped bus generations, destroying all nodes
Oct 8 09:59:06 freyr kernel: [ 107.116070] firewire_core: rediscovered device fw0
Oct 8 09:59:06 freyr kernel: [ 107.116132] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
Oct 8 09:59:09 freyr kernel: [ 110.121390] firewire_core: created device fw1: GUID 0001db000b0012cd, S400, 1 config ROM retries
Oct 8 09:59:09 freyr kernel: [ 110.159455] scsi2 : SBP-2 IEEE-1394
Oct 8 09:59:09 freyr kernel: [ 110.373952] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
Oct 8 09:59:09 freyr kernel: [ 110.375111] scsi 2:0:0:0: Direct-Access SAMSUNG HD204UI PQ: 0 ANSI: 4
Oct 8 09:59:09 freyr kernel: [ 110.375503] sd 2:0:0:0: Attached scsi generic sg4 type 0
Oct 8 09:59:09 freyr kernel: [ 110.390942] sd 2:0:0:0: [sdc] 3907029152 512-byte logical blocks: (2.00 TB/1.81 TiB)
Oct 8 09:59:09 freyr kernel: [ 110.405886] sd 2:0:0:0: [sdc] Write Protect is off
Oct 8 09:59:09 freyr kernel: [ 110.405898] sd 2:0:0:0: [sdc] Mode Sense: 10 00 00 00
Oct 8 09:59:09 freyr kernel: [ 110.435669] sd 2:0:0:0: [sdc] Got wrong page
Oct 8 09:59:09 freyr kernel: [ 110.435681] sd 2:0:0:0: [sdc] Assuming drive cache: write through
Oct 8 09:59:09 freyr kernel: [ 110.495835] sd 2:0:0:0: [sdc] Got wrong page
Oct 8 09:59:09 freyr kernel: [ 110.495846] sd 2:0:0:0: [sdc] Assuming drive cache: write through
Oct 8 09:59:09 freyr kernel: [ 110.524454] sdc: sdc1
Oct 8 09:59:09 freyr kernel: [ 110.584840] sd 2:0:0:0: [sdc] Got wrong page
Oct 8 09:59:09 freyr kernel: [ 110.584853] sd 2:0:0:0: [sdc] Assuming drive cache: write through
Oct 8 09:59:09 freyr kernel: [ 110.584859] sd 2:0:0:0: [sdc] Attached SCSI disk
Oct 8 09:59:15 freyr kernel: [ 116.465601] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)

[Jochen Blacha (jochen-blacha)]

Same bug is valid for the Natty back-port kernel in 10.04 ...

A external firewire hard drive is NOT being recognized if the system is booted with 2.6.38.12.22 (latest "lts-backport-natty" available at the time of writing).

Booting the system with stock 2.6.32 resolves the problem.

Comparing the dmesg logs of 2.6.32 past 2.6.38 reveals that 2.6.38 is entirely missing the "ohci1394" and subsequent "ieee1394" outputs.

Here's the proof that the back-port kernel is compiled properly:

$ ls -R /lib/modules/2.6.32-35-generic/ | grep ohci
firewire-ohci.ko
ohci1394.ko
$ ls -R /lib/modules/2.6.38-12-generic/ | grep ohci
firewire-ohci.ko

^-- Where's ohci1394.ko?

How about finally implementing a quality assurance check before releasing packages?

[Jochen Blacha (jochen-blacha)]

Sorry, typo ...

The line ...
"Here's the proof that the back-port kernel is compiled properly:"

... should read ...
Here's the proof that the back-port kernel is NOT compiled properly:

Sorry for the double-post.

[penalvch (penalvch)]

cldde, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[cIdde (schiwed)]

Hi,

thanks for your intereste in the bug. Have been using the drive via USB all
the time in the past, so I don't have any recent experience with the firewire
behavior. But I will test ist again and let you know the results. Might take a
few days, though.

Cheers,

   Volker

Thursday, Nov. 21st, 2013, "Christopher M. Penalver"
<email address hidden> wrote:
> cldde, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available (not the
> daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It
> will allow additional upstream developers to examine the issue. Once you've
> tested the upstream kernel, please comment on which kernel version
> specifically you tested. If this bug is fixed in the mainline kernel,
> please add the following tags: kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example: kernel-fixed-upstream-v3.12
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag: needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Tags added: bios-outdated-2.60 needs-upstream-testing regression-
> potential
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]