On 30 Nov, To: kostik...@gmail.com wrote:
On 30 Nov, Konstantin Belousov wrote:
On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote:
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
Peter, could you, please, try to reproduce the issue ? It does not look
like a
On 30 Nov, To: kostik...@gmail.com wrote:
On 30 Nov, Konstantin Belousov wrote:
On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote:
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
Peter, could you, please, try to reproduce the issue ? It does not look
like a
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 01:11:35PM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013
On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote:
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
Peter, could you, please, try to reproduce the issue ? It does not look
like a random hardware failure, since in all cases, it is curthread access
which is
On 30 Nov, Konstantin Belousov wrote:
On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote:
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
Peter, could you, please, try to reproduce the issue ? It does not look
like a random hardware failure, since in all cases,
On 28 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 01:11:35PM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis
On Thu, Nov 28, 2013 at 12:56:37AM -0800, Don Lewis wrote:
I haven't figured out how to find the currently installed BIOS version.
The motherboard is Abit, which is no more, but I found an archive of all
of their downloads. I'll also check into updates from the Linux world.
I reviewed the 0xF
On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 01:11:35PM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013
On 28 Nov, Konstantin Belousov wrote:
On Thu, Nov 28, 2013 at 12:56:37AM -0800, Don Lewis wrote:
I haven't figured out how to find the currently installed BIOS version.
The motherboard is Abit, which is no more, but I found an archive of all
of their downloads. I'll also check into updates
On 25 Nov, Konstantin Belousov wrote:
On Sat, Nov 23, 2013 at 11:43:30PM -0800, Don Lewis wrote:
I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic
that I stumbled across earlier. Now I got this when I started upgrading
ports:
Unread portion of the kernel message
On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote:
It took a while, but I just got another double fault, though this one is
somewhat different. This time it trapped in cpu_switch(), which
resulted in calls to
trap()-printf()-...-putchar()-msgbuf_addstr()-_mtx_lock_spin_flags()
where
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote:
It took a while, but I just got another double fault, though this one is
somewhat different. This time it trapped in cpu_switch(), which
resulted in calls to
On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote:
It took a while, but I just got another double fault, though this one is
somewhat different. This time it trapped in cpu_switch(),
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote:
It took a while, but I just got another double fault, though this one is
somewhat different.
On 27 Nov, I wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote:
It took a while, but I just got another double fault, though this one is
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote:
http://people.freebsd.org/~truckman/doublefault2.JPG
What is the instruction at cpu_switch+0x9b ?
pgpkUYYh0Npao.pgp
Description: PGP signature
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote:
http://people.freebsd.org/~truckman/doublefault2.JPG
What is the instruction at cpu_switch+0x9b ?
movl 0x8(%edx),%eax
This machine is running in i386 mode.
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote:
http://people.freebsd.org/~truckman/doublefault2.JPG
What is the instruction at cpu_switch+0x9b ?
movl 0x8(%edx),%eax
So it is
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote:
http://people.freebsd.org/~truckman/doublefault2.JPG
What is the instruction at
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis
On 27 Nov, Konstantin Belousov wrote:
And, as the last resort, I do understand that this sounds as giving up,
do you monitor the temperature of the CPUs ? BTW, which CPUs are that,
please show the cpu identification lines from the boot dmesg.
Idle temps:
hw.acpi.thermal.tz0.temperature:
On Wed, Nov 27, 2013 at 01:11:35PM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov wrote:
On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote:
On 27 Nov, Konstantin Belousov
On Sat, Nov 23, 2013 at 11:43:30PM -0800, Don Lewis wrote:
I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic
that I stumbled across earlier. Now I got this when I started upgrading
ports:
Unread portion of the kernel message buffer:
Fatal double fault:
eip =
On 25 Nov, Konstantin Belousov wrote:
On Sat, Nov 23, 2013 at 11:43:30PM -0800, Don Lewis wrote:
I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic
that I stumbled across earlier. Now I got this when I started upgrading
ports:
Unread portion of the kernel message
I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic
that I stumbled across earlier. Now I got this when I started upgrading
ports:
Unread portion of the kernel message buffer:
Fatal double fault:
eip = 0xc0b158e0
esp = 0xe4f62000
ebp = 0xe4f62010
cpuid = 0; apic id = 00
30 matches
Mail list logo
