odd phenomenon.
Something strange I've noticed on all recent 2.4 and 2.5 kernels.
If I start galeon whilst I've got a bk pull in operation, the galeon process starts, opens its window, and then dies instantly. Starting it a second time works.
Its not OOM, as theres plenty of free RAM, and half gig of free (unused) swap.
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related..
Ideas ?
Dave
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 9 lines · Dave Jones
Something strange I've noticed on all recent 2.4 and 2.5 kernels. If I start galeon whilst I've got a bk pull in operation, the galeon process starts, opens its window, and then dies instantly. Starting it a second time works.
Its not OOM, as theres plenty of free RAM, and half gig of free (unused) swap. It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related..
Ideas ?
Dave
(1) strace?
(2) kgdb breakpoint on exit(), conditional on current->comm?
(3) exit code?
Thanks,
Bill
Quoted 10 lines · Dave Jones
Something strange I've noticed on all recent 2.4 and 2.5 kernels.
If I start galeon whilst I've got a bk pull in operation, the galeon process starts, opens its window, and then dies instantly. Starting it a second time works.
Its not OOM, as theres plenty of free RAM, and half gig of free (unused) swap.
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related..
I used to have a small system with 96M RAM and no swap, only OpenSSH and bash and some kernel threads were running, when I got a big BK pull, it would catch sig 11 and die. Maybe this is unrelated. Indeed, at first I had only 64M RAM installed, only after some sig 11, had I got more RAM installed. But this probably has nothing to do with your situation.
Quoted 4 lines · William Lee Irwin III
Quoted 3 lines
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related.. Ideas ?
(1) strace?
That was my first thought. Everything works as expected though when you try to strace it.
Dave
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 3 lines · Dave Jones
Quoted 3 lines
Quoted 3 lines
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related.. Ideas ?
Quoted 1 line · William Lee Irwin III
Quoted 1 line
(1) strace?
Quoted 2 lines · Dave Jones
That was my first thought. Everything works as expected though when you try to strace it.
Highly unusual. In-kernel tracing seems to be in order. Can you describe a more complete "reproduction suite" (esp. app/lib versions)?
Thanks,
Bill
Quoted 3 lines · William Lee Irwin III
Quoted 2 lines
That was my first thought. Everything works as expected though when you try to strace it.
Highly unusual.
Indeed.
Quoted 2 lines
In-kernel tracing seems to be in order. Can you
describe a more complete "reproduction suite" (esp. app/lib versions)?
Galeon 1.2.7, Bitkeeper 3.0 20021011025136
I had until today thought that this was a 2.5 only bug, but this box rebooted back into a 2.4 kernel yesterday for the first time in ages. (Running 2.4.20-rc4 currently)
Dave
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 5 lines · Dave Jones
Galeon 1.2.7, Bitkeeper 3.0 20021011025136
I had until today thought that this was a 2.5 only bug, but this box rebooted back into a 2.4 kernel yesterday for the first time in ages. (Running 2.4.20-rc4 currently)
Galeon 1.3.1 CVS here, so maybe its a bit different, but zero problems on 2.5 - and I use Galeon constantly :)
Anything I can do to try to better reproduce it?
Robert Love
Quoted 10 lines · Dave Jones
Something strange I've noticed on all recent 2.4 and 2.5 kernels.
If I start galeon whilst I've got a bk pull in operation, the galeon process starts, opens its window, and then dies instantly. Starting it a second time works.
Its not OOM, as theres plenty of free RAM, and half gig of free (unused) swap.
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related..
Happens all the time here too (ppc32), and did so for ages, with 2.4 (didn't specifically notice it with 2.5 yet, but I rarely use galeon when testing 2.5 ;)
Typically happens with any kind of intense disk activity slowing down galeon's launch process. (Not only bk, but also for example updatedb running in the background).
I'm currently running galeon 1.2.6 (happened with all earlier versions at least).
Ben.
Quoted 6 lines · Benjamin Herrenschmidt
Quoted 2 lines
It's almost 100% reproducable here. Only seen it do it on this box though which is a P4 with HT, so it could be SMP related..
Happens all the time here too (ppc32), and did so for ages, with 2.4 (didn't specifically notice it with 2.5 yet, but I rarely use galeon when testing 2.5 ;)
Ha! Conclusive proof I'm not losing my marbles.
Quoted 3 lines
Typically happens with any kind of intense disk activity slowing down galeon's launch process. (Not only bk, but also for example updatedb running in the background).
Maybe, but bk was the only disk-thrashing type app I regularly have running when I've tried to reproduce this.
Is your PPC32 box SMP ? I'm wondering why I don't see it on my athlon/P3 boxes, just on my dual P4.
Dave
Signature · 1 line
| Dave Jones. http://www.codemonkey.org.uk
Quoted 5 lines · Dave Jones
Maybe, but bk was the only disk-thrashing type app I regularly have running when I've tried to reproduce this.
Is your PPC32 box SMP ? I'm wondering why I don't see it on my athlon/P3 boxes, just on my dual P4.
No, it happens on my UP laptop as well. Hadess suggested it could be yet-another gconf race in gnome
Ben.