Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Aug 2003 20:19:06 +0000
From:      Bosko Milekic <bmilekic@technokratis.com>
To:        Kevin Oberman <oberman@es.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: 5.1, Data Corruption, Intel, Oh my! [patch]
Message-ID:  <20030811201906.GB2234@technokratis.com>
In-Reply-To: <20030812001414.6914B5D07@ptavv.es.net>
References:  <bmilekic@technokratis.com> <20030811100549.GA33392@technokratis.com> <20030812001414.6914B5D07@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help


Since some people have gotten back to me telling me that they have
apparently been able to boot with the patch, I have a suspicion that it
could be something in your config files.  The other submitter already
sent me his, so can you please send me yours (along with a 'dmesg' when
you boot with a clean -current, without the patch) so that I can try
building something similar here to hopefully track this down?

(send them off-list, please)

If anyone else is seeing something similar, also please send me your
kernel config files with stock -current 'dmesg' output off-list.

Thanks,
Bosko

On Mon, Aug 11, 2003 at 05:14:14PM -0700, Kevin Oberman wrote:
> Bosko,
> 
> I am seeing a very similar thing on my CURRENT system after applying
> your patch It's also when probing APM. I suspect it's not an issue with
> ACPI.
> 
> It is also at least very similar to the crash I see when I add
> DISABLE_PSE to my kernel.
> 
> Here is mine, as transcribed by hand from my IBM T30 with P4-M
> uniprocessor:
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x1c
> fault code              = supervisor write, page not present
> instruction pointer     = 0x8:0xc06492a0
> stack pointer           = 0x10:0xc0c219a2
> frame pointer           = 0x10:0xc0c21b0e
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> kernel: type 12 trap, code=0
> Stopped at      vm_fault+0x240: cmpxchgl	#edx,0x1c(%ecx)
> db> trace
> vm_fault(c102f000,c0000000,2,0,c07470a0) at vm_fault+240
> trap_pfault(c0c21b9e,0,c00004d8,100000,c00004d8) at trap_pfault+0x1e3
> trap(1bc40018,10,6fe40060,1c,0) at trap+0x2cd
> calltrap() at calltrap+0x5
> --- trap 0xc, eip = 0x58de, esp = 0xc0c21bde, epb = 0xc0c21be4 ---
> (null)(1bf80058,0,530e0102,80202,5059f6) at 0x58de
> db>
> 
> The kernel was cvsuped this afternoon and patched only with your
> patch. I had to panic twice to get a core dump and I have doubts about
> its validity.
> -- 
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman@es.net			Phone: +1 510 486-8634

-- 
Bosko Milekic  *  bmilekic@technokratis.com  *  bmilekic@FreeBSD.org
TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030811201906.GB2234>