linux-kernel - Re: howto map HDT dumped addresses to AMD64 kernel virtual addresses.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 Sep 2006 12:33:47 -0700
From:	"Om Narasimhan" <om.turyx@...il.com>
To:	"Keith Mannthey" <kmannth@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: howto map HDT dumped addresses to AMD64 kernel virtual addresses.

On 9/5/06, Keith Mannthey <kmannth@...il.com> wrote:
> On 9/5/06, Om Narasimhan <om.turyx@...il.com> wrote:
> > Hi,
> > I am running a kernel (Suse Enterprise 9 with SP3) and it is hanging
> > somewhere in the kernel. By hooking up HDT from AMD, I got a the
> > assembly dump of the routine which causes the infinite loop. How
> > should I map the addresses dumped by HDT in the format SEG:Offset
> > (e.g,
> > 0033:00000000_00400C18   mov   esi,[loc_0000000000501a64h]
> > 0033:00000000_00400C1E   test   esi,esi
> > 0033:00000000_00400C20   jz   loc_0000000000400c30h
> > ...etc)
> > to kernel virtual address space?
>
> I don't know about your HDT (never used one) but have you already
> tried the regular debug paths (nmi watchdog/sysrq/crashdump/kdb) that
> SLES9 has?
No. Thanks. I would try Sysrq and kdb. HDT does not make much sense at
this stage without all those. Thanks for reminding that.
Regards,
Om.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/