On Thu, Aug 29, 2013 at 04:45:44PM -0300, Fernando de Oliveira wrote:
> {{
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.826533] task: f60a32a0 ti: f60c4000 task.ti:
> f60c4000
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.813856] Call Trace:
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.812209] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G
> O 3.10.7 #1
>
You had a kernel oops.
And this is not much more than two and a half minutes after
starting the guest, I think.
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.812909] task: c18dc154 ti: c18d0000 task.ti:
> c18d0000
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.814198] Code: f2 ff 13 83 c3 08 83 3b 00 eb ed
> e8 30 51 07 00 5b 5e 5f 5d c3 55 b8 01 00 00 00 89 e5 64 8b 15 10 b0 9b
> c1 e8 af ff ff ff fb f4 <83> c8 ff 64 8b 15 10 b0 9b c1 e8 9e ff ff ff
> 5d c3 55 89 e5 50
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.826782] Call Trace:
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.813473] Stack:
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.812498] Hardware name: VMware, Inc. VMware
> Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2012
>
The oops was in the guest kernel
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.826232] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G
> O 3.10.7 #1
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:32 2013 ...
> VMWLFS74 kernel: [ 159.828885] task: f60a2d90 ti: f60c2000 task.ti:
> f60c2000
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.826352] Hardware name: VMware, Inc. VMware
> Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2012
>
> Message from syslogd@VMWLFS74 at Thu Aug 29 15:38:31 2013 ...
> VMWLFS74 kernel: [ 159.826912] Code: 89 c3 31 c0 f3 ab f0 0f ab 1a 5b
> 5f 5d c3 55 b8 98 5a 5d c1 89 e5 5d c3 90 8b 0d 44 3a 8e c1 55 89 e5 8d
> 84 08 00 b0 ff ff 89 10 <5d> c3 55 89 e5 53 89 d3 8d 48 01 ba 08 00 00
> 00 89 d8 e8 bf 89
>
Not enough info (it probably scrolled away before what you captured
here anyway).
>
> Machine was not responding well, too slow. Decided to "make install"
> (only, as already had built glibc before).
>
You're lucky it responded at all after an oops ;-)
> First impressions is it back to normal, no error messages, javac gives
> me the version.
>
Great javac result.
But if the kernel oopsed then there could be damage elsewhere in
the kernel's data structures. I haven't been paying close attention
to the details of what you are doing, but if you were rebuilding
glibc in the guest then it might just be an example of our general
"don't try this at home!" recommendation about upgrading a running
glibc.
>
> LFS test branch is still building:
>
> []s,
> Fernando
--
das eine Mal als Tragödie, dieses Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
