This must be something about my particular hardware/software
configuration or more people would be reporting it.
I will try to nail down the problem, but as soon as the SBP2 driver in
2.5.(recent) sees my firewire drive, either during kernel boot or later
if I turn on / plug in the drive, the system crashes and dumps a
seemingly endless stack trace. It doesn't make it to the system log, so
I don't have much more than that yet.
Many more details available on request. And more information coming
regardless.
Unfortunately for me, 2.4 is extremely flaky for sbp2 as well. (sigh).
Red Hat kernels oops a few seconds after the drive is plugged in, but
the system keeps running so I have some decoded oops for those at
least. I'll try to get one from a stock 2.4.recent...
--
Torrey Hoffman <[email protected]>
Torrey Hoffman wrote:
>
> as soon as the SBP2 driver in
> 2.5.(recent) sees my firewire drive, either during kernel boot or later
> if I turn on / plug in the drive, the system crashes and dumps a
> seemingly endless stack trace.
Please apply the below patch, which should prevent the info
from scrolling away. Then send a full report to
[email protected]
diff -puN arch/i386/kernel/traps.c~stop-trace arch/i386/kernel/traps.c
--- 25/arch/i386/kernel/traps.c~stop-trace Wed Jun 4 16:48:41 2003
+++ 25-akpm/arch/i386/kernel/traps.c Wed Jun 4 16:50:13 2003
@@ -96,6 +96,7 @@ void show_trace(unsigned long * stack)
{
int i;
unsigned long addr;
+ int count = 0;
if (!stack)
stack = (unsigned long*)&stack;
@@ -111,6 +112,8 @@ void show_trace(unsigned long * stack)
printk(" [<%08lx>] ", addr);
print_symbol("%s\n", addr);
}
+ if (count++ > 12)
+ break;
}
printk("\n");
}
@@ -146,6 +149,8 @@ void show_stack(unsigned long * esp)
}
printk("\n");
show_trace(esp);
+ for ( ; ; )
+ ;
}
/*
_
On Thu, 2003-06-05 at 01:48, Torrey Hoffman wrote:
> This must be something about my particular hardware/software
> configuration or more people would be reporting it.
>
> I will try to nail down the problem, but as soon as the SBP2 driver in
> 2.5.(recent) sees my firewire drive, either during kernel boot or later
> if I turn on / plug in the drive, the system crashes and dumps a
> seemingly endless stack trace. It doesn't make it to the system log, so
> I don't have much more than that yet.
>
> Many more details available on request. And more information coming
> regardless.
>
> Unfortunately for me, 2.4 is extremely flaky for sbp2 as well. (sigh).
> Red Hat kernels oops a few seconds after the drive is plugged in, but
> the system keeps running so I have some decoded oops for those at
> least. I'll try to get one from a stock 2.4.recent...
>From experience, sbp2 with a recent ieee1394 linux_2_4 SVN branch
snapshot works quite well. I updated the one in my tree about
3 weeks ago and have been successfull playing with an iPod, burning
CDs, etc...
Ben.