> A disassembly of the calling function, i.e.:
>
> [] ? run_timer_softirq+0x150/0x165
>
> ... would be a good idea, at least.
Here you go. Note that the machine isn't doing anything of interest,
so after a quick search for residual personal data I could give you a
root login on it. (Just
On 07/19/2013 02:00 PM, George Spelvin wrote:
>>> EIP is at 0xc143a091
>>> EAX: c143a090 EBX: 0100 ECX: f315 EDX: c143a090
>>> ESI: c143a090 EDI: c143a090 EBP: c143a090 ESP: f3151eec
>>> DS: 007b ES: 007b FS: GS: 0033 SS: 0068
>>> CR0: 80050033 CR2: a090c143 CR3: 331c6000 CR4:
>> EIP is at 0xc143a091
>> EAX: c143a090 EBX: 0100 ECX: f315 EDX: c143a090
>> ESI: c143a090 EDI: c143a090 EBP: c143a090 ESP: f3151eec
>> DS: 007b ES: 007b FS: GS: 0033 SS: 0068
>> CR0: 80050033 CR2: a090c143 CR3: 331c6000 CR4: 07d0
>> DR0: DR1: DR2:
On 07/17/2013 11:13 PM, George Spelvin wrote:
> I ressurected an old Athlon XP box for fun, and was stress-testing it
> with mprime. (It had been stable before retirement.) After 34 hours
> of successful torture test (suggesting a stable memory syatem), I found
> this on the screen
On Thu, 18 Jul 2013, Borislav Petkov wrote:
> On Thu, Jul 18, 2013 at 02:13:47AM -0400, George Spelvin wrote:
> > I ressurected an old Athlon XP box for fun, and was stress-testing it
> > with mprime. (It had been stable before retirement.) After 34 hours
> > of successful torture test
On Thu, 18 Jul 2013, Borislav Petkov wrote:
On Thu, Jul 18, 2013 at 02:13:47AM -0400, George Spelvin wrote:
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a
On 07/17/2013 11:13 PM, George Spelvin wrote:
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a stable memory syatem), I found
this on the screen
EIP is at 0xc143a091
EAX: c143a090 EBX: 0100 ECX: f315 EDX: c143a090
ESI: c143a090 EDI: c143a090 EBP: c143a090 ESP: f3151eec
DS: 007b ES: 007b FS: GS: 0033 SS: 0068
CR0: 80050033 CR2: a090c143 CR3: 331c6000 CR4: 07d0
DR0: DR1: DR2: DR3:
On 07/19/2013 02:00 PM, George Spelvin wrote:
EIP is at 0xc143a091
EAX: c143a090 EBX: 0100 ECX: f315 EDX: c143a090
ESI: c143a090 EDI: c143a090 EBP: c143a090 ESP: f3151eec
DS: 007b ES: 007b FS: GS: 0033 SS: 0068
CR0: 80050033 CR2: a090c143 CR3: 331c6000 CR4: 07d0
DR0:
A disassembly of the calling function, i.e.:
[c1024524] ? run_timer_softirq+0x150/0x165
... would be a good idea, at least.
Here you go. Note that the machine isn't doing anything of interest,
so after a quick search for residual personal data I could give you a
root login on it. (Just
On Thu, Jul 18, 2013 at 02:13:47AM -0400, George Spelvin wrote:
> I ressurected an old Athlon XP box for fun, and was stress-testing it
> with mprime. (It had been stable before retirement.) After 34 hours
> of successful torture test (suggesting a stable memory syatem), I found
> this on the
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a stable memory syatem), I found
this on the screen (hand-transcribed, top scrolled off):
h_rpcgss oid_registry
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a stable memory syatem), I found
this on the screen (hand-transcribed, top scrolled off):
h_rpcgss oid_registry
On Thu, Jul 18, 2013 at 02:13:47AM -0400, George Spelvin wrote:
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a stable memory syatem), I found
this on the screen
14 matches
Mail list logo
