I did the following to verify:
1) Installed 7.2-RC2 on the Perc 4e/Si H430 machine (RAID1), this went fine.
2) Turned off, and placed one drive in the machine with Perc 4e/Si H435,
boot went fine and no long delays after amr0
So the problem as I encountered with 7.1-RELEASE-p4 is not present
Alan Cox escribió:
I believe that this problem is now resolved. A recent MFC overlooked one
critical change. That change was MFCed a few minutes ago. So, please
update your kernel.
Rebuilding right now, thanks.
Regards
Raul
___
freebsd-stable@fre
The just-released 7.2-RC2 should fix this problem. Please let me
know ASAP if it works for you.
Scott
Jeroen Hofstee wrote:
Hello All,
I encountered the same problem as reported to this list earlier,
http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html,
but then with
I have a test machine. Nothing special except for the dell 2350
mobo. Everything works. Somehow I had 7.1-RELEASE on it already.
I zeroed the disk to reinstall 7.1R from disc1. The install went
fine. But when booting from disk I hit the loader skip_newlines
issue:
http://lists.freebsd.org/piperma
Kostik Belousov wrote:
> On Fri, Apr 17, 2009 at 12:27:32PM -0700, Nate Lawson wrote:
>> Ian Smith wrote:
>>> Perhaps a silly question, but is it too late at this stage of the game
>>> to try logging S5 events to syslog before dying? I agree with Stephen,
>>> logging 'shutdown by powerbutton' su
On Apr 17, 2009, at 12:27 PM, Nate Lawson wrote:
Perhaps a silly question, but is it too late at this stage of the
game
to try logging S5 events to syslog before dying? I agree with
Stephen,
logging 'shutdown by powerbutton' surely beats what might otherwise
resemble a spontaneous reboot? O
On Fri, Apr 17, 2009 at 12:27:32PM -0700, Nate Lawson wrote:
> Ian Smith wrote:
> > Perhaps a silly question, but is it too late at this stage of the game
> > to try logging S5 events to syslog before dying? I agree with Stephen,
> > logging 'shutdown by powerbutton' surely beats what might othe
Hello All,
I encountered the same problem as reported to this list earlier,
http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html,
but then with 7.1-RELEASE-p4.
Interestingly enough, FreeBSD booted fine on the machine installed
(updated from 7.0 to 7.1-RELEASE-p4).
This
On Fri, Apr 17, 2009 at 01:15:03PM -0400, Ken Smith wrote:
>
> The first of two planned Release Candidates for the FreeBSD 7.2-RELEASE
> cycle is now available. Testing of some of the recent work would be
> particularly appreciated. This includes:
>
> - bce(4) updated (there is a report t
On Fri, 2009-04-17 at 13:15 -0400, Ken Smith wrote:
> A fix for the "vm_page_insert: page already inserted" panics has been
> committed to RELENG_7_1 this morning so it missed the 7.2-RC1 builds.
> If you wind up being hit by that you can try a normal source based
> update to the current state of
Ian Smith wrote:
> On Fri, 10 Apr 2009, Nate Lawson wrote:
> > Andriy Gapon wrote:
> > > on 09/04/2009 23:24 Stephen Clark said the following:
> > >> Is there a reason it doesn't send and event like Linux that can be acted
> > >> upon by user space other
> > >> than signaling init? I like to h
On Fri, 10 Apr 2009, Nate Lawson wrote:
> Andriy Gapon wrote:
> > on 09/04/2009 23:24 Stephen Clark said the following:
> >> Is there a reason it doesn't send and event like Linux that can be acted
> >> upon by user space other
> >> than signaling init? I like to have a message written in
> >
Daniel Bond wrote:
> Hi,
>
>
> FreeBSD has excellent PAM-support, except for the passwd-command. The
> passwd-command gained PAM support quite a while ago, but there is a
> test preventing it from working with PAM.
> There have been outstanding PR's for this minor issue for years now, I
> think it'
Got it on Vista Home 64 & VMware server
Two CPU's & two gigs of ram.
Works grate so far. fast too
On Fri, 17 Apr 2009 13:15:03 -0400
Ken Smith wrote:
>
> The first of two planned Release Candidates for the
> FreeBSD 7.2-RELEASE
> cycle is now available. Testing of some of the recent
> work wou
Alan Cox wrote:
> I believe that this problem is now resolved. A recent MFC overlooked
> one critical change. That change was MFCed a few minutes ago. So,
> please update your kernel.
>
> Regards,
> Alan
>
>
I will csup and rebuild tonight, thanks for sharing!
___
I believe that this problem is now resolved. A recent MFC overlooked one
critical change. That change was MFCed a few minutes ago. So, please
update your kernel.
Regards,
Alan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
The first of two planned Release Candidates for the FreeBSD 7.2-RELEASE
cycle is now available. Testing of some of the recent work would be
particularly appreciated. This includes:
- bce(4) updated (there is a report that lagg(4) does
not work after the update, fixing that may
> * Danny Braniss [2009-04-08 15:54:25 +0300]:
>
> >
> > > Garance A Drosihn wrote:
> > > > Some friends of mine are looking at the new "DroboPro", which makes a
> > > > lot of disk space available via iSCSI (in addition to firewire 800),
> > > > and they were wondering how well iSCSI works with
On Thu, 16 Apr 2009 21:36:30 +0200 piotr.smy...@heron.pl wrote:
> On Tue, 14 Apr 2009 20:52:38 +1000, Andrew MacIntyre wrote
> > Michal Varga wrote:
> > > 2009/4/13 :
> > >> Yes, I'm 100% positive I tried plugging mouse after the boot up had
> > >> finished. Honestly I am late asking here. I was s
Hi,
FreeBSD has excellent PAM-support, except for the passwd-command. The
passwd-command gained PAM support quite a while ago, but there is a
test preventing it from working with PAM.
There have been outstanding PR's for this minor issue for years now, I
think it's time this one got fixed.
20 matches
Mail list logo
