In addition I was playing a little bit more and got more useful
information.
First, CONFIG_PREEMPT should be enabled, because without, the oops
seems to be reported at the wrong position!! (no idea why ...)
Wrong, or just different? Preempt could matter just because
it changes the timing, w
Andreas Hirstius wrote:
Hi,
CONFIG_DEBUG_STACKOVERFLOW is enabled, but doesn't give any information.
I even increased STACK_WARN to see if it's just on the edge...
Basically all debug options are enabled, but none produces any useful
output...
OK -- that helps narrow things down, good.
In addi
Hi,
CONFIG_DEBUG_STACKOVERFLOW is enabled, but doesn't give any information.
I even increased STACK_WARN to see if it's just on the edge...
Basically all debug options are enabled, but none produces any useful
output...
In addition I was playing a little bit more and got more useful information
Andreas Hirstius wrote:
That shouldn't happen. Are you enabling CONFIG_4KSTACKS?
No, CONFIG_4KSTACKS is not enabled.
Does it repeat if you disable preempt? It'd be useful to
know what CONFIG_DEBUG_STACKOVERFLOW says, too.
That chunk of code was just dropping the lock, doing preempt
processing,
That shouldn't happen. Are you enabling CONFIG_4KSTACKS?
No, CONFIG_4KSTACKS is not enabled.
Andreas
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo te
Andreas Hirstius wrote:
Hi David,
Sorry for the confusion of deadlock and Oops. I'm not that familiar with
the terms...
No prob.
here is the disassemble output of gdb:
if you're sure this was from the same kernel that caused the oops ...
then this bit looks to be the operative part of spin_unlo
Hi David,
Sorry for the confusion of deadlock and Oops. I'm not that familiar with
the terms...
here is the disassemble output of gdb:
.
0x0f95 :lock addl $0x0,0x0(%esp,1)
0x0f9b :mov0x8(%esi),%ebx
0x0f9e :test %bl,%bl
0x0fa0 :js 0x1
Hi Andreas,
These aren't really examples of a "deadlock", they're just oopses.
Can you disassemble the qh_completions() code and find out what
it's trying to execute when it oopses? Either GDB or "objdump"
can be used.
This is a new one, but at least it looks like it's the same spot
in the code e
Hi,
I'm trying to use external USB HDD on Dual Xeon machines (Intels E7500
or Serverworks GC-LE Chipset).
OS: Fedora Core 1, Kernel 2.6.x
controller: Adaptec USB2Connect 5100 (NEC chipset)
disks: one Maxtor OneTouch 250GB
8 "old" IBM-DTLA in external cases with the Genesys chipset
