Red Hat Bugzilla – Bug 139825
VIA 6306 Firewire/IEEE1394 controller needs workaround in ohci1394.c
Last modified: 2015-01-04 17:12:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
Rev. 46 and below of the VIA 6306 Firewire/IEEE1394 controller
incorrectly reports its maximum packet size as 2, causing the kernel
to fall back to 512 as a default. It should use 2048 for best
performance. These controllers are very common and cheap enough to be
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Check kernel source
2. Observe missing VT6306 workaround
Actual Results: After pulling myself together, I resigned myself to
having to rebuild the ohci1394 module locally.
Expected Results: The ohci1394 module detected I had a flawed
controller, and worked around it.
Created attachment 107516 [details]
vt6306 patch ready for 2.6.9-1.681_FC3 kernel
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This patch still isn't in 2.6.12-1.1372_FC3:
Jul 12 07:40:22 xxx kernel: ohci1394: $Rev: 1223 $ Ben Collins <email@example.com>
Jul 12 07:40:22 xxx kernel: ieee1394: warning: Invalid max packet size of 2,
setting to 512
Jul 12 07:40:22 xxx kernel: ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=
MMIO=[e3004000-e30047ff] Max Packet=
Can you please talk to upstream about including this patch? If a patch wasn't
included in upstream kernels from 2.6.9 through 2.6.12, maybe there is a good
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.