Re: Page fault trap on IBM x336

2011-01-18 Thread Marcos Laufer 
Hello Patrick,

Do you think this could work for 4.8?
How could you compile kernel and ramdisk kernel with the old 1.72 pci.c, 
using another box that boots 4.7?

Regards,
Marcos

Patrick Coleman wrote:
 On Wed, Jun 9, 2010 at 10:47 AM, patrick keshishian pkesh...@gmail.com 
 wrote:
   
 you realize obsd4.5 isn't supported any longer since 4.7 was released.
 

 Fair enough. I've managed to get 4.7 working by reverting
 /sys/dev/pci/pci.c to 1.72, as suggested in that thread, so I guess
 I'll try that.

 Cheers,

 Patrick

Re: Page fault trap on IBM x336

2010-06-10 Thread Patrick Coleman 
On Wed, Jun 9, 2010 at 10:47 AM, patrick keshishian pkesh...@gmail.com wrote:

 you realize obsd4.5 isn't supported any longer since 4.7 was released.

Fair enough. I've managed to get 4.7 working by reverting
/sys/dev/pci/pci.c to 1.72, as suggested in that thread, so I guess
I'll try that.

Cheers,

Patrick

-- 
http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting

Re: Page fault trap on IBM x336

2010-06-08 Thread patrick keshishian 
On Sun, May 30, 2010 at 8:53 PM, Patrick Coleman blin...@gmail.com wrote:
 Hi,

 Let me know if I should be posting this elsewhere.

 I'm running OpenBSD 4.5 i386 on an IBM x336 server, as newer versions
 don't work with the Broadcom network interfaces [1]. I installed it
 about a week ago, and everything was working great until I got the
 following on the console (retyped). I ran a trace as per the FAQ:

you realize obsd4.5 isn't supported any longer since 4.7 was released.

regardless you if you are planning on running obsd4.5, you should at
the very lease apply currently published patches under errata4.5:

http://www.openbsd.org/errata45.html

I wonder whether errata 002 is relavent in your case, but I am not sure.

--patrick


 [lots of vlan: lines; probably me adding the interfaces a few days ago]
 vlan80: initialized with non-standard mtu 1496 (parent trunk0)
 vlan85: initialized with non-standard mtu 1496 (parent trunk0)
 vlan61: initialized with non-standard mtu 1496 (parent trunk0)
 vlan1: initialized with non-standard mtu 1496 (parent trunk0)
 uvm_fault(0xd080d9e0, 0x0, 0, 1) - e
 kernel: page fault trap, code=0
 Stopped at arp_rtrequest+0xfb: movb 0x64(%eax),%al
 ddb pckbc_start: command error

 ddb trace
 arp_rtrequest(b,d8382048,de164df0,0) at arp_rtrequest+0xfb
 rtrequest1(b,de164df0,38,de164dec,0,d2ac0400,d0202de9,60) at
rtrequest1+0x1f2
 rtalloc1(d081a508,1,0,d839a68c) at rtalloc1+0xb6
 rtalloc_mpath(d081a504,d869881c,0,d839a68c,0) at rtalloc_mpath+0x2f
 ip_forward(d861fa00,0,de164f10,0,204) at ip_forward+0xd8
 ipv4_input(d861fa00,d2a73640,d08c2b54,d8a312b8) at ipv4_input+0x26e
 ipintr(d0350058,d08c0010,d06f0010,de160010,d8a312b8) at ipintr+0x64
 Bad frame pointer: 0xde164f28
 ddb

 dmesg output is below [2]. Is this a known problem that's fixed in 4.7?

 Cheers,

 Patrick


 1. http://kerneltrap.org/mailarchive/openbsd-misc/2010/3/12/6350403/thread
 2.
 patr...@ceti-a:~[0]$ dmesg
 OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
[...]