On Fri, 2 Mar 2007, Paul Pruett wrote:
I copied a current i386 kernel from this week , and
it rebooted okay on the athlon64 platform.
To test I did a make for /usr/ports/sytutils/cdrtools
and it did not complain, so thats a small warm fuzzy.
Now I wait a week and see if it freezes/hangs
The fix was just to remove PAE support from the i386 kernel (until the
bug is found). So, try copying the latest snapshot kernel to /bsd and
reboot. Just grab it from the snapshots/i386 directory on the ftp
server.
I copied a current i386 kernel from this week , and
it rebooted okay on the
On 2007/03/03 14:01, Paul Pruett wrote:
Umm, it frooze/hung up again at 5:08 am. about
23 hours after rebooting with the current 4.1 kernel
on the i386 4.0 userland
(not recommended...I'm sure you know that already though)
I was remote so I did not see the monitor for any
panics, but
The fix was just to remove PAE support from the i386 kernel (until the
bug is found). So, try copying the latest snapshot kernel to /bsd and
reboot. Just grab it from the snapshots/i386 directory on the ftp server.
Agreed, I did not see a easy one line change to kernel compile
to remove PAE
The fix was just to remove PAE support from the i386 kernel (until the
bug is found). So, try copying the latest snapshot kernel to /bsd and
reboot. Just grab it from the snapshots/i386 directory on the ftp server.
Some system utilities were converted to interact with the kernel using
sysctl,
After consideration and due to weird
problems afore discussed, I will likely be
upgrading an openbsd 4.0 i386 server to
an openbsd 4.0 amd64.
Yes in retrospect I should have used the
amd64 build not the i386 build on an athlon64
cpu... But I now have a 'production '
cyrus-imapd/sendmail server
On 2007/02/27 17:03, Paul Pruett wrote:
After consideration and due to weird
problems afore discussed, I will likely be
upgrading an openbsd 4.0 i386 server to
an openbsd 4.0 amd64.
A new i386 snapshot is very likely to fix this.
I have upgraded version on i386 and on amd64,
but never same
I have received several assurances that
-current may have resolved some weirds
for i386 on amd64 processors...
With hesitation I could try jumping to current
instead of stable amd64.
I have used -current on productin before,
but only after verifying the ports could
make w/o fubars
Either amd64
Paul Pruett wrote:
I have received several assurances that
-current may have resolved some weirds
for i386 on amd64 processors...
With hesitation I could try jumping to current
instead of stable amd64.
I have used -current on productin before,
but only after verifying the ports could
9 matches
Mail list logo
