On Thu, 11 Jun 2015 09:43:15 +0800, Yanhui Shen wrote:
> Hi,
>
> Thanks, it works!
>
> https://svnweb.freebsd.org/base/head/sys/dev/pci/vga_pci.c?r1=284012&r2=284011&pathrev=284012
>
>
>
> 2015-06-11 0:38 GMT+08:00 Adrian Chadd :
>
> > Hi,
> >
> > There was an update to freebsd-h
Hi,
Thanks, it works!
https://svnweb.freebsd.org/base/head/sys/dev/pci/vga_pci.c?r1=284012&r2=284011&pathrev=284012
2015-06-11 0:38 GMT+08:00 Adrian Chadd :
> Hi,
>
> There was an update to freebsd-head a few days ago from hans - it
> disabled PCI interrupts for VGA until a driver claims it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/15 02:20, Palle Girgensohn wrote:
> Also
>
> # uname -a FreeBSD pingpongdb 10.1-RELEASE-p10 FreeBSD
> 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> amd64 # uptime 2:18a
> uname -KU
>
> I am guessing your kernel is new, and your userland is old, as Xin Li said
# uname -KU
1001000 1001000
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
Hi,
There was an update to freebsd-head a few days ago from hans - it
disabled PCI interrupts for VGA until a driver claims it.
See if that helps?
-a
b
On 10 June 2015 at 05:33, Yanhui Shen wrote:
> Hi,
>
> I noticed the interrupt rate of my FreeBSD system is very high (~35%) after
> upgrade
On 06/09/2015 19:48, Xin Li wrote:
> Hi, Randy,
>
> On 06/09/15 16:34, Randy Bush wrote:
>> # uname -a FreeBSD foux.psg.com 10.1-RELEASE-p10 FreeBSD
>> 10.1-RELEASE-p10 #0: Tue May 12 19:33:13 UTC 2015
>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>> i386
>
>> it's really p11
Hi,
I noticed the interrupt rate of my FreeBSD system is very high (~35%) after
upgrade from r279138 to r284205.
To find out which revision cause this problem,
I used a binary search manner and compiled the kernel 11 times.
Finally I located to r279961, the interruption rate is abnormal since th
On 06/10/15 12:34, Kurt Jaeger wrote:
> Hi!
>
>> You kernel hasn't been rebuilt then.
>
> Yes, but normally, freebsd-update provides me with an updated kernel.
>
> The update provides (among other stuff):
>
> /boot/kernel/zfs.ko
> /boot/kernel/zfs.ko.symbols
> /lib/libzpool.so.2
>
> so it does
Hi!
> You kernel hasn't been rebuilt then.
Yes, but normally, freebsd-update provides me with an updated kernel.
The update provides (among other stuff):
/boot/kernel/zfs.ko
/boot/kernel/zfs.ko.symbols
/lib/libzpool.so.2
so it does not touch the value uname reports until a new kernel is built.
You kernel hasn't been rebuilt then.
On 10/06/2015 11:23, Kurt Jaeger wrote:
Hi!
I see the same: uname says: 10.1p10
What does the following say when run from your source directory:
grep BRANCH sys/conf/newvers.sh
BRANCH="RELEASE-p11"
___
freeb
Hi!
I see the same: uname says: 10.1p10
> What does the following say when run from your source directory:
>
> grep BRANCH sys/conf/newvers.sh
BRANCH="RELEASE-p11"
--
p...@opsec.eu+49 171 3101372 5 years to go !
_
What does the following say when run from your source directory:
grep BRANCH sys/conf/newvers.sh
Regards
Steve
On 10/06/2015 10:20, Palle Girgensohn wrote:
Also
# uname -a
FreeBSD pingpongdb 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13
06:54:13 UTC 2015
r...@amd64-bui
Also
# uname -a
FreeBSD pingpongdb 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13
06:54:13 UTC 2015
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
# uptime
2:18am up 36 mins, 4 users, load averages: 0,08 0,14 0,10
# ls -lrt /boot/kernel/kernel /boot/kernel
Xin Li wrote on 06/10/2015 03:55:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/09/15 17:55, Nick Frampton wrote:
Pardon my ignorance, but why was this posted as an EN instead of a
SA if it corrects security vulnerabilities?
We do not generally issue SA's for local DoS issues (histori
Sehr geehrte Damen und Herren,
diese Nachricht wurde als Antwort auf Ihre Support-Anfrage bezüglich
"[FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-15:07.zfs"
automatisch erstellt.
Eine Antwort auf diese Nachricht ist nicht notwendig. Ihrer
Support-Anfrage wurde die Bezeichnung [Op
15 matches
Mail list logo