In-Reply-To: <[email protected]>
On Mon, 01 May 2006 10:14:23 -0700, Martin Bligh wrote:
> >>Code: e8 4c ba d8 ff 65 48 8b 34 25 00 00 00 00 4c 8b 46 08 f0 41
> >>RIP <ffffffff8047c8b8>{__sched_text_start+1856} RSP <0000000000000000>
> >> -- 0:conmux-control -- time-stamp -- May/01/06 3:54:37 --
> >
> >
> > I was not able to reproduce this on the 4-way EMT64 machine. Am a bit stuck.
>
> OK, is there anything we could run this with that'd dump more info?
> (eg debug patches or something). There's bugger all of use that I
> can see in that stack (and why does __sched_text_start come up anyway,
> is that an x86_64-ism ?).
Look at your System.map and see if another symbol has the same address
as __sched_text_start.
I have:
ffffffff8042eb30 T io_schedule_timeout
ffffffff8042eb30 T __sched_text_start
--
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
