Oops in 2.6.19.1
In-Reply-To: <[email protected]>
Quoted 4 lines · Alistair John Strachan
I've eliminated 2.6.19.1 as the culprit, and also tried toggling "optimize for size", various debug options. 2.6.19 compiled with GCC 4.1.1 on an Via Nehemiah C3-2 seems to crash in
pipe_pollreliably, within approximately 12 hours.
Which CPU are you compiling for? You should try different options.
Can you post disassembly of pipe_poll() for both the one that crashes and the one that doesn't? Use 'objdump -D -r fs/pipe.o' so we get the relocation info and post just the one function from each for now.
Signature · 1 line
MBTI: IXTP
Quoted 9 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 4 lines · Alistair John Strachan
I've eliminated 2.6.19.1 as the culprit, and also tried toggling "optimize for size", various debug options. 2.6.19 compiled with GCC 4.1.1 on an Via Nehemiah C3-2 seems to crash in
pipe_pollreliably, within approximately 12 hours.Which CPU are you compiling for? You should try different options.
I should, I haven't thought of that. Currently it's compiling for CONFIG_MVIAC3_2, but I could try i686 for example.
Quoted 3 lines
Can you post disassembly of
pipe_poll()for both the one that crashes and the one that doesn't? Use 'objdump -D -rfs/pipe.o' so we get the relocation info and post just the one function from each for now.
Sure, no problem:
http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
Both use identical configs, neither are optimised for size. The config is available from the same location.
Signature · 5 lines
Cheers, Alistair. Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 18 lines · Alistair John Strachan
Quoted 9 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 4 lines · Alistair John Strachan
I've eliminated 2.6.19.1 as the culprit, and also tried toggling "optimize for size", various debug options. 2.6.19 compiled with GCC 4.1.1 on an Via Nehemiah C3-2 seems to crash in
pipe_pollreliably, within approximately 12 hours.Which CPU are you compiling for? You should try different options.
I should, I haven't thought of that. Currently it's compiling for
CONFIG_MVIAC3_2, but I could try i686 for example.Quoted 3 lines
Can you post disassembly of
pipe_poll()for both the one that crashes and the one that doesn't? Use 'objdump -D -rfs/pipe.o' so we get the relocation info and post just the one function from each for now.
Quoted 6 lines
Sure, no problem:
http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
Both use identical configs, neither are optimised for size. The config is available from the same location.
Can you try enabling as many debug options as possible?
Quoted 2 lines
Cheers,
Alistair.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 19 lines · Adrian Bunk
Quoted 18 lines · Alistair John Strachan
Quoted 9 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 4 lines · Alistair John Strachan
I've eliminated 2.6.19.1 as the culprit, and also tried toggling "optimize for size", various debug options. 2.6.19 compiled with GCC 4.1.1 on an Via Nehemiah C3-2 seems to crash in
pipe_pollreliably, within approximately 12 hours.Which CPU are you compiling for? You should try different options.
I should, I haven't thought of that. Currently it's compiling for
CONFIG_MVIAC3_2, but I could try i686 for example.Quoted 3 lines
Can you post disassembly of
pipe_poll()for both the one that crashes and the one that doesn't? Use 'objdump -D -rfs/pipe.o' so we get the relocation info and post just the one function from each for now.
Quoted 8 lines
Quoted 6 lines
Sure, no problem:
http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
Both use identical configs, neither are optimised for size. The config is available from the same location.
Can you try enabling as many debug options as possible?
Specifically what? I've already had:
CONFIG_DETECT_SOFTLOCKUPCONFIG_FRAME_POINTERCONFIG_UNWIND_INFO
Enabled. CONFIG_4KSTACKS is disabled. Are there any debugging features actually pertinent to this bug?
Signature · 5 lines
Cheers, Alistair. Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 29 lines · Alistair John Strachan
Quoted 19 lines · Adrian Bunk
Quoted 18 lines · Alistair John Strachan
Quoted 9 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 4 lines · Alistair John Strachan
I've eliminated 2.6.19.1 as the culprit, and also tried toggling "optimize for size", various debug options. 2.6.19 compiled with GCC 4.1.1 on an Via Nehemiah C3-2 seems to crash in
pipe_pollreliably, within approximately 12 hours.Which CPU are you compiling for? You should try different options.
I should, I haven't thought of that. Currently it's compiling for
CONFIG_MVIAC3_2, but I could try i686 for example.Quoted 3 lines
Can you post disassembly of
pipe_poll()for both the one that crashes and the one that doesn't? Use 'objdump -D -rfs/pipe.o' so we get the relocation info and post just the one function from each for now.Quoted 8 lines
Quoted 6 lines
Sure, no problem:
http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
Both use identical configs, neither are optimised for size. The config is available from the same location.
Can you try enabling as many debug options as possible?
Quoted 8 lines
Specifically what? I've already had:
CONFIG_DETECT_SOFTLOCKUPCONFIG_FRAME_POINTERCONFIG_UNWIND_INFOEnabled.
CONFIG_4KSTACKSis disabled. Are there any debugging features actually pertinent to this bug?
No, that's only an "enable as much as possible and hope one helps" shot in the dark.
Quoted 2 lines
Cheers,
Alistair.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed