On Wed, Sep 01, 2004 at 11:36:09PM +0200, Christoph Hellwig wrote:
On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
I don't think placing a strategic printk() qualifies as a fix though :-)
Maybe GCC is to blame here. I'm using gcc 3.3.4-6sarge1.0.1 (current from
reassign 261893 gcc-3.3
thanks
* Jan-Jaap van der Heijden wrote:
On Wed, Sep 01, 2004 at 11:36:09PM +0200, Christoph Hellwig wrote:
On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
I don't think placing a strategic printk() qualifies as a fix though :-)
Maybe GCC
On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
I don't think placing a strategic printk() qualifies as a fix though :-)
Maybe GCC is to blame here. I'm using gcc 3.3.4-6sarge1.0.1 (current from
testing)
This indeed smells like a compiler bug
Is it safe to use GCC
Some additional information:
I can make the problem disappear (!) by placing a printk() in the ext3
module init function, like this:
--- super.c.orig 2004-09-01 21:21:08.0 +0200
+++ super.c 2004-09-01 22:30:54.0 +0200
@@ -2337,6 +2337,7 @@
static int __init init_ext3_fs(void)
{
I think the problem is in the ext3fs module.
The oops disappears if I hack my initrd to not attempt to mount the rootfs
as ext3.
This is done by removing ext3 from FSTYPES in /etc/linuxrc.conf inside the
initrd.
Unfortunately, if ext2 is in /proc/filesystems, then mkinitrd will try to
mount as
On Mon, Aug 30, 2004 at 07:22:54PM +0200, Jan-Jaap van der Heijden wrote:
http://people.debian.org/~nobse/kernel/kernel-image-2.6.8-alpha/
They are currently sitting in incoming, and will be moved into the
regular archive in a few hours.
I tried again with 2.6.8-3 from this URL. The
http://people.debian.org/~nobse/kernel/kernel-image-2.6.8-alpha/
They are currently sitting in incoming, and will be moved into the
regular archive in a few hours.
I tried again with 2.6.8-3 from this URL. The problem persists, and I can't
say the backtrace improved either...
dmesg | ksymoops:
* Jan-Jaap van der Heijden wrote:
With a stock 2.6.6-1-generic kernel it crashes as soon as it
initilizes the SCSI controller.
Can you please try the 2.6.7 packages, and report if they fix your
problem (I suppose so)?
http://people.debian.org/~nobse/kernel-image-2.6.7-alpha/
2.6.7 doesn't lock up
* Jan-Jaap van der Heijden wrote:
With a stock 2.6.6-1-generic kernel it crashes as soon as it
initilizes the SCSI controller.
Can you please try the 2.6.7 packages, and report if they fix your
problem (I suppose so)?
http://people.debian.org/~nobse/kernel-image-2.6.7-alpha/
Norbert
On Thu, Jul 29, 2004 at 10:50:11PM +0200, Jan-Jaap van der Heijden wrote:
hmm, we should enable CONFIG_KALLSYMS to get useful backtraces on alpha,
I'd love to see where this oops comes from.
Could you enlighten me? CONFIG_KALLSYMS is set in the kernel config.
/sbin/kallsyms is able to
10 matches
Mail list logo
