Hi FreeBSD Community,
i got warning that 9.1RC3 is approaching end of its life, i should upgrade
with in two week. when i started the upgrade, i get the following error.
any solution anyone knows?
[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirror
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
9.1-RELEASE is not officially released yet, so that is why you are
seeing that.
On 12/5/2012 1:50 AM, Shiv. Nath wrote:
> Hi FreeBSD Community,
>
> i got warning that 9.1RC3 is approaching end of its life, i should
> upgrade with in two week. when i
anyone knows what to do?
[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patc
On Wed, 05 Dec 2012 12:16:25 +0100, Shiv. Nath
wrote:
anyone knows what to do?
Maybe wait until 9.1-RELEASE is actually released.
Ronald.
[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3
On Wed, 05 Dec 2012 08:50:04 +0100, Shiv. Nath
wrote:
Hi FreeBSD Community,
i got warning that 9.1RC3 is approaching end of its life, i should
upgrade
with in two week.
Where did you get this warning? I have never seen it anywhere on the
internet or on my machines.
Ronald.
when i
On Wed, 05 Dec 2012 14:58:52 +0100, Franci Nabalanci
wrote:
And when update will be out? There are nothing about month on the
official
site.
According to the commits it is planned for today (USA time, so for me it
is tonight or tomorrow morning).
http://www.secnetix.de/olli/FreeBSD/svn
On Wed, 05 Dec 2012 14:56:35 +0100, Franci Nabalanci
wrote:
Did you try FreeBSD-update fetch?
No, I have never used that.
Ronald.
On Dec 5, 2012 5:31 AM, "Ronald Klop"
wrote:
On Wed, 05 Dec 2012 08:50:04 +0100, Shiv. Nath <
shiv.nath@digital-infotech.**net >
wrote:
Hi FreeBSD
schrieb Harald Schmalzbauer am 23.11.2012 14:39 (localtime):
> ...
> found out thathint.mpt.0.msi_enable="1"
> solves the interrupt storm problem, although dmesg output still is
> exactly the same:
> mpt0: port 0x4000-0x40ff mem
> 0xd644-0xd645,0xd642-0xd643 irq 18 at devi
Hello freebsd-stable@freebsd.org , Please confirm if you are the owner of this
email. Reply
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr.
schrieb Harald Schmalzbauer am 05.12.2012 21:04 (localtime):
> schrieb Harald Schmalzbauer am 23.11.2012 14:39 (localtime):
>> ...
>> found out thathint.mpt.0.msi_enable="1"
>> solves the interrupt storm problem, although dmesg output still is
>> exactly the same:
>> mpt0: port 0x4000-0x
schrieb Harald Schmalzbauer am 05.12.2012 22:23 (localtime):
> kernel: IOC StatusSCSI: Data Underrun
Searching for this topic showd an 53c1030 errata fix:
https://patchwork.kernel.org/patch/94223/
Like you guessed, I can't make use of it, but probably someone else?
Thanks,
-Harry
signa
11 matches
Mail list logo