Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-17 Thread Ralf Hildebrandt
* Randy.Dunlap <[EMAIL PROTECTED]>: > >Is it normal that the kernel with debugging enabled is not larger than > >the normal kernel? > >- > > No, it should be much larger. Recheck the .config file > for CONFIG_DEBUG_INFO=y. Maybe you need to do 'make clean' > first. CONFIG_DEBUG_KERNEL=y CONFIG

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-17 Thread Randy.Dunlap
Ralf Hildebrandt wrote: * Ralf Hildebrandt <[EMAIL PROTECTED]>: The best way to do that is to ensure that the kernel was built with CONFIG_DEBUG_INFO, note the offending EIP value, then do # gdb vmlinux (gdb) l *0xc0 I'm rebuilding the ac12 kernel which crashed on me after just one day and will re

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-17 Thread Ralf Hildebrandt
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > > The best way to do that is to ensure that the kernel was built with > > CONFIG_DEBUG_INFO, note the offending EIP value, then do > > > > # gdb vmlinux > > (gdb) l *0xc0 > > I'm rebuilding the ac12 kernel which crashed on me after just one day > and wil

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-17 Thread Ralf Hildebrandt
* Andrew Morton <[EMAIL PROTECTED]>: > There have been a handful of reports - there's surely a race in there. > > Unfortunately I've yet to see a report from which we can identify the > offending line in the very large journal_commit_transaction() function. :( > > The best way to do that is to

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-16 Thread Andrew Morton
Dale Blount <[EMAIL PROTECTED]> wrote: > > This looks very similar (at least to me) to an OOPS I posted with 2.6.9 > on 12/03/2004. > http://marc.theaimsgroup.com/?l=linux-kernel&m=110210705504716&w=2 There have been a handful of reports - there's surely a race in there. Unfortunately I've yet to

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-16 Thread Ralf Hildebrandt
* Dale Blount <[EMAIL PROTECTED]>: > This looks very similar (at least to me) to an OOPS I posted with 2.6.9 > on 12/03/2004. > http://marc.theaimsgroup.com/?l=linux-kernel&m=110210705504716&w=2 Could be. > My system is also a dual Xeon using SMP and Hyperthreading > (/proc/cpuinfo shows 4 cpus)

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-16 Thread Dale Blount
On Wed, 2005-02-16 at 21:04 +0100, Ralf Hildebrandt wrote: > * Jan Kara <[EMAIL PROTECTED]>: > > > I guess the system is SMP... > > Indeed it is. Dual Xeon with SMP. > This looks very similar (at least to me) to an OOPS I posted with 2.6.9 on 12/03/2004. http://marc.theaimsgroup.com/?l=linux-

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-16 Thread Ralf Hildebrandt
* Jan Kara <[EMAIL PROTECTED]>: > I guess the system is SMP... Indeed it is. Dual Xeon with SMP. > Sadly a few lines in the beginning of the > report are missing (probably scrolled off the screen) Yes, this sucks. I rebooted with vesafb active, no I do have 50 lines :) > but it seems simil

Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-16 Thread Jan Kara
Hello, > Today our mailserver froze after just one day of uptime. I was able to > capture the Oops on the screen using my digital camera: > > http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ > > Keywords: EIP is at journal_commit_transaction, process kjournald I guess the system is SMP... Sa

Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)

2005-02-15 Thread Ralf Hildebrandt
Today our mailserver froze after just one day of uptime. I was able to capture the Oops on the screen using my digital camera: http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ Keywords: EIP is at journal_commit_transaction, process kjournald # mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=re