[haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- From: Andreas Färber <andreas.faerber@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 20 Apr 2008 19:40:52 +0200
Hi Michael,
Am 20.04.2008 um 12:46 schrieb Michael Lotz:
Hi Andreas
I think I have pinpointed this to my on-board Firewire ... if I
disable it in BIOS I get uptime of > 20 min for both your r25000
image
as well as my patched r25032. Could this be, or is it pure
coincidence?
That's good to hear. And as I replied to Rene, it is possible. If the
firewire driver overwrites memory it does not really own (because it
freed it already) then this can easily lead to such problems with
inconsistent crashes. If you reenable and just remove the firewire
driver you should get the same result in that case.
On first try, it does work for > 20 min with firewire bus_manager
moved away!
In case it matters, listdev says:
device Serial bus controller (FireWire (IEEE 1394), OHCI) [c|0|10]
vendor 1106: VIA Technologies, Inc.
device 3044: IEEE 1394 Host Controller
Thanks,
Andreas
- References:
- [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- From: Michael Lotz
Other related posts:
- » [haiku-development] Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- » [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
Hi Andreas
I think I have pinpointed this to my on-board Firewire ... if I disable it in BIOS I get uptime of > 20 min for both your r25000 image as well as my patched r25032. Could this be, or is it pure coincidence?
That's good to hear. And as I replied to Rene, it is possible. If the firewire driver overwrites memory it does not really own (because it freed it already) then this can easily lead to such problems with inconsistent crashes. If you reenable and just remove the firewire driver you should get the same result in that case.
- [haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- From: Michael Lotz