Re: Firefox Hangs w/ PPC64

[Gustavo Luiz Duarte]

You are probably hitting this bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=813095

It was fixed in xulrunner-12.0-7.fc17, however, the patch was dropped 
(probably during the update to xulrunner-13) and then added back to 
xulrunner-15.0.1-3.fc17.

There seems to be no f17 build for ppc of xulrunner > 15.0.1-2, so you 
either go back to 12.0-7 or wait for a new xulrunner build to come up.


Gustavo

On 11/24/2012 07:13 PM, Stephen Harker wrote:
> > We've had hit and miss success with FF due to a number of
> problems -- not
> > warranted to go into it here.  But what would be helpful is if you told us
> > which version you are using, which xulrunner, and which Fedora version.
>
>  Although not the original poster I have the same problem.  I am using
>  Fedora 17 ppc64
>
>  [~] uname -a
>  Linux howitt.home 3.6.2-4.fc17.ppc64 #1 SMP Thu Nov 1 19:45:13 MST
>  2012 ppc64 ppc64 ppc64 GNU/Linux
>
>  [~] rpm -qa | grep firefox
>  firefox-15.0.1-1.fc17.ppc64
>  [~] rpm -qa | grep xulrunner
>  xulrunner-15.0.1-1.fc17.ppc64
>
>  This is running on an old powermac G5:
>
>  [~] cat /proc/cpuinfo
>  processor       : 0
>  cpu             : PPC970MP, altivec supported
>  clock           : 2000.000000MHz
>  revision        : 1.1 (pvr 0044 0101)
>
>  processor       : 1
>  cpu             : PPC970MP, altivec supported
>  clock           : 2000.000000MHz
>  revision        : 1.1 (pvr 0044 0101)
>
>  timebase        : 33333333
>  platform        : PowerMac
>  model           : PowerMac11,2
>  machine         : PowerMac11,2
>  motherboard     : PowerMac11,2 MacRISC4 Power Macintosh
>  detected as     : 337 (PowerMac G5 Dual Core)
>  pmac flags      : 00000000
>  L2 cache        : 1024K unified
>  pmac-generation : NewWorld
>
>  In my case what happens is that if I run firefox it starts then within
>  a minute whether I open another window or not it locks up.
>  Essentially it starts using 100% of cpu time and stops reacting to the
>  keyboard.  It can be stopped using `kill -9' as the OP remarks.
>
>  Tasks: 134 total,   1 running, 133 sleeping,   0 stopped,   0 zombie
>  Cpu(s): 19.1%us, 31.3%sy,  0.0%ni, 49.1%id,  0.5%wa,  0.0%hi,  0.0%si,  0.0%st
>  Mem:  12271232k total,  1834816k used, 10436416k free,   195456k buffers
>  Swap: 16383936k total,        0k used, 16383936k free,   910080k cached
>
>     PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>    2333 sjh       20   0  726m 220m  95m S 99.7  1.8   2:14.62 firefox
>
>  By the way, another peculiarity I have noticed on fc17, and fc16
>  before it, was that it would fail on my firewire drives where Mac OSX,
>  debian and YDL worked with them without problems:
>
>  fc17:
>  [    2.863334] firewire_ohci 0001:03:0e.0: enabling device (0000 -> 0002)
>  [    2.918981] firewire_ohci 0001:03:0e.0: added OHCI v1.0 device as card 0, 8 IR + 8 IT
> contexts, quirks 0x0
>  [    3.419352] firewire_core 0001:03:0e.0: created device fw0: GUID 001451fffe1d4ff4,
> S800
>  [   55.528273] firewire_core 0001:03:0e.0: giving up on node ffc0: reading config rom
> failed: timeout
>
>  Debian:
>  [    2.670593] firewire_ohci 0001:03:0e.0: enabling device (0000 -> 0002)
>  [    2.875671] firewire_ohci: Added fw-ohci device 0001:03:0e.0, OHCI version 1.0
>  [    3.383820] firewire_core: created device fw0: GUID 001451fffe1d4ff4, S800
>  [    3.412079] firewire_core: created device fw1: GUID 0001d202e01c0720, S800
>  [    3.972948] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
>