Opened 4 years ago

Last modified 6 weeks ago

#12448 assigned bug

Firewire-0 cause troubles (GetBuffer: IDs mismatch, SetHeader)

Reported by: vidrep Owned by: nobody
Priority: normal Milestone: R1
Component: Servers/media_addon_server Version: R1/Development
Keywords: Cc: ttcoder
Blocked By: Blocking: #9804, #11243, #12477, #12488, #12700, #13988, #14854, #14877
Has a Patch: no Platform: All

Description (last modified by Barrett)

hrev49758 x86_gcc2 Media Add-on Server crash after deskop appears Debug report attached

--

When Firewire-0 is present there's a memory corruction supposedly caused by the driver. This is the master ticket.

Attachments (2)

Change History (26)

comment:1 Changed 4 years ago by Barrett

Does the crash happened just after an upgrade? Or is it persistent?

comment:2 Changed 4 years ago by vidrep

Did a fresh install of hrev49833 x86_gcc2 on my second test PC pkgman full-sync to 49852 x86_gcc2 reboot media_add-on server debug report appeared on desktop after the reboot Was this automatically generated? I did not see any debugger dialog, nor did I input a command. debug report attached

comment:3 Changed 4 years ago by Barrett

Blocking: 12477 added

comment:4 Changed 4 years ago by Barrett

Milestone: UnscheduledR1
Status: newassigned

I think the common factor between all bug reports that I've seen is that the FireWire-0 control is there. This might be cause of some buffers mismatch or area offsets overflow since those threads live in the same team (the media_addon_server).

A test that might be useful is if you disable firewire from bios or blacklist the right drivers so that we can see if the problem is still happening.

comment:5 Changed 4 years ago by vidrep

I'm not so sure this issue is persistent enough to easily track down. I saw it happen only twice during a week in which I was at home on a work break, doing a lot of testing for Haiku. Prior to the first report, I had not seen a media_addon_server crash for quite some length of time. Of course, I'm always willing to assist however I can, to help Haiku progress toward a stable Beta release. I'll try your suggestion should the problem become reproducible.

Last edited 4 years ago by vidrep (previous) (diff)

comment:6 Changed 4 years ago by Barrett

I fixed different occurrences of this bug, only one of them was replicable on my system and it happened at very high load of the system (such as 20 videos played at the same time). I don't see this bug on my pc since then, and also I don't have a firewire. So if we could confirm that disabling it the bug doesn't occur, it will be helpful to finally fix the source.

comment:7 Changed 4 years ago by bruno

Did a fresh install of hrev 49857 x86_gcc2 on my PC...

pkgman full-sync

reboot

media_add-on server wont crash anymore... Maybe fixed?! Strange...

comment:8 Changed 3 years ago by Barrett

Description: modified (diff)
Summary: Media Add-on Server crashFirewire-0/SetHeader cause troubles

comment:9 Changed 3 years ago by Barrett

Blocking: 12700 added

(In #12700) Yes exactly, the better way you can solve it is to disable your firewire card. I'm closing duplicate tickets of the SetHeader/Firewire-0 bug, please continue to follow #12448.

comment:10 Changed 3 years ago by Barrett

Blocking: 9804 added

(In #9804) Another Firewire-0 problem variant.

comment:11 Changed 3 years ago by Barrett

Blocking: 12488 added

(In #12488) Firewire-0 duplicate, please refer to #12448.

comment:12 Changed 3 years ago by Barrett

Summary: Firewire-0/SetHeader cause troublesFirewire-0 cause troubles (GetBuffer: IDs mismatch, SetHeader)

For reference to anyone experiencing this bug, to fix the problem you should blacklist the fw_raw driver from the bootloader.

comment:13 Changed 3 years ago by Barrett

Blocking: 11243 added

(In #11243) This is another variant of #12448, follow the instructions there to temporarily fix it.

comment:14 Changed 15 months ago by korli

Blocking: 13988 added

comment:15 Changed 5 months ago by vidrep

I have not seen this issue in a long time. Fixed???

comment:16 Changed 5 months ago by waddlesplash

Resolution: not reproducible
Status: assignedclosed

comment:17 Changed 5 months ago by ttcoder

Cc: ttcoder added

comment:18 Changed 5 months ago by Barrett

Resolution: not reproducible
Status: closedreopened

comment:19 Changed 4 months ago by diver

Blocking: 14877 added

comment:20 Changed 3 months ago by diver

Blocking: 14854 added

comment:21 Changed 2 months ago by lpereira

Just to confirm that blacklisting fw_raw works around the issue for me. Upgraded to 52979 today and media_addon_server was crashing. Rebooting did not help. My machine is a ThinkPad X60, which has a Firewire port; I'll keep it blacklisted as I don't have any Firewire devices. I've saved the crash report if that helps debugging the issue.

comment:22 Changed 6 weeks ago by cocobean

@vidrep - Issue still exists for R1B1 (up to -129 revision) and hrev53051.

NOTE: Firewire-0 control
/boot/system/add-ons/media/firewire_dv.media_addon

Seems best to disable/blacklist it officially in the nightlies and future releases - until fixed.

The other thing I did was restart/quit the media server process - which should show media_server and media_addon_server when restarted. This gives a click sound in the speakers if it works OK - and no crash condition. Check that both app services are running.

Last edited 6 weeks ago by cocobean (previous) (diff)

comment:23 Changed 6 weeks ago by Barrett

I agree it should be disabled. I think I proposed it somewhere but there was someone which didn't agree and then for lack of motivation I postponed the thing.

However the patch is rather trivial, grep in the build directory for "fw_raw" and you will find what you need.

Sorry guys, not being formally an Haiku developer anymore I can't help more than that. Hope that helps!

comment:24 Changed 6 weeks ago by korli

Owner: changed from Barrett to nobody
Status: reopenedassigned
Note: See TracTickets for help on using tickets.