Bug 161702

Summary:	[firewire] Firewire messages on DELL E6520 running 8.2 or 9.0-BETA3
Product:	Base System	Reporter:	Sebastian Chmielewski <chmiels>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	fbsdbugs4
Priority:	Normal
Version:	9.0-BETA3
Hardware:	Any
OS:	Any

Description Sebastian Chmielewski 2011-10-16 08:50:09 UTC

I'm running 8.2-STABLE on Dell E6520. The same symptoms are for 9.0-BETA3.

Dmesg is full of following messages when firewire port is enabled in BIOS,
I was also unable to get working dcons console from external machine using
firewire cable. Cable is for sure fine and other machine is also fine
(used to debug other configurations).

firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0)  (me) 
firewire0: bus manager 0 
fwohci0: too many cycles lost, no cycle master present?
fwohci0: fwohci_intr_core: BUS reset
fwohci0: phy int
fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=65, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0)  (me) 
firewire0: bus manager 0 
fwohci0: too many cycles lost, no cycle master present?

This laptop is using something called O2 Firewire + SD Card controller.
SD Card seems to be working correctly.

How-To-Repeat: Boot with firewire (1394) enabled in BIOS (default is of course enabled).

Comment 1 Mark Linimon freebsd_committer

2011-10-16 09:44:00 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-firewire

Over to maintainer(s).

Comment 2 Sebastian Chmielewski 2011-10-16 11:54:50 UTC

I have found following bug report from Ubuntu with (simple) patch.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/801719

-- 
Sebastian Chmielewski * jid:chmielsster@gmail.com * gg:3336919 * icq:224161389

Comment 3 Eitan Adler freebsd_committer

2017-12-31 08:00:11 UTC

For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped

Comment 4 Mark Linimon freebsd_committer

2024-11-17 03:45:05 UTC

^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of suppoprt.
Please re-open if it is still a problem on a supported version.