[EMAIL PROTECTED] said:
> I've gotten to the bottom of this problem, and you are correct that
> klog is trashing the messages file for the oops.
Oh dear. That's quite a serious bug in klogd. It should never destroy the
original information, _especially_ if the System.map it's looking at
blatant
On Mon, Apr 23, 2001 at 11:47:27PM +0100, David Woodhouse wrote:
David/LKML,
I've gotten to the bottom of this problem, and you are correct that klog
is trashing the messages file for the oops. As for the oops, it was related
to the use of ll_rw_blk() instead of submit_bh() in 2.4.3 which was
On Mon, Apr 23, 2001 at 11:03:48PM +0100, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > Are you sure the trace is decoded correctly?
>
> > > CPU:0
> > > EIP:0010:[sys_mremap+31/884]
>
> Probably not. It looks like it was munged by klogd. Some distributions are
> still shipp
[EMAIL PROTECTED] said:
> Are you sure the trace is decoded correctly?
> > CPU:0
> > EIP:0010:[sys_mremap+31/884]
Probably not. It looks like it was munged by klogd. Some distributions are
still shipping with klogd configured to destroy the original information on
the way to the lo
On Mon, Apr 23, 2001 at 10:24:55PM +0200, Manfred Spraul wrote:
> Are you sure the trace is decoded correctly?
>
> > CPU:0
> > EIP:0010:[sys_mremap+31/884]
> > EFLAGS: 00010206
>
> > Code: ac ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 75 d9
> ac ae is
> lodsb
> scasb
>
> Could
Are you sure the trace is decoded correctly?
> CPU:0
> EIP:0010:[sys_mremap+31/884]
> EFLAGS: 00010206
> Code: ac ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 75 d9
ac ae is
lodsb
scasb
Could you run
#objdump --disassemble-all --reloc linux/mm/mremap.o | less
and check that the
6 matches
Mail list logo
