Re: Any way to make the stack shown on an OOPS longer than the default?

From: Manfred Spraul (manfreds@colorfullife.com)
Date: Mon Apr 17 2000 - 02:14:05 EST

Next message: Jamie Lokier: "Re: [q] chdir/chroot by dentry and not by name."
Previous message: Linda Walsh: "[Fwd: Proposal "LUID"]"
In reply to: Miles Lane: "Any way to make the stack shown on an OOPS longer than the default?"
Next in thread: Mike Galbraith: "Re: Any way to make the stack shown on an OOPS longer than the default?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Miles Lane wrote:
>
> I am hitting an OOPS in 2.3.99-pre6-3 in usb-ohci.
> That module's primary developer has asked that I
> obtain as longer stack trace in the OOPS message.
> The reason this is necessary is that when this
> particular OOPS occurs, my system completely locks
> and I'm unable to get more info than what is on the
> screen.
>
SMP or UP?
Most hard lock-ups on SMP disappear if you compile for UP, but some bugs
disappear as well ;)

which cpu? for i386, modify

linux/arch/i386/kernel/traps.c, ~line 141

int kstack_depth_to_print = 128;

-- Manfred

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Jamie Lokier: "Re: [q] chdir/chroot by dentry and not by name."
Previous message: Linda Walsh: "[Fwd: Proposal "LUID"]"
In reply to: Miles Lane: "Any way to make the stack shown on an OOPS longer than the default?"
Next in thread: Mike Galbraith: "Re: Any way to make the stack shown on an OOPS longer than the default?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:10 EST