Ulrich Spörlein u...@freebsd.org wrote:
On Thu, 2013-02-07 at 15:33:22 +0100, Fabian Keil wrote:
Ulrich Spörlein u...@freebsd.org wrote:
Yes, it's pretty much as weird as it sounds. All new machine, forklifted
the image from on old i386 machine running 8.x to current on amd64.
TB --- 2013-02-08 09:22:13 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-02-08 09:22:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Fixed.
Adrian
On 8 February 2013 02:25, FreeBSD Tinderbox tinder...@freebsd.org wrote:
TB --- 2013-02-08 09:22:13 - tinderbox 2.10 running on
freebsd-current.sentex.ca
TB --- 2013-02-08 09:22:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26
On Fri, 2013-02-08 at 09:57:09 +0100, Fabian Keil wrote:
Ulrich Spörlein u...@freebsd.org wrote:
On Thu, 2013-02-07 at 15:33:22 +0100, Fabian Keil wrote:
Ulrich Spörlein u...@freebsd.org wrote:
Yes, it's pretty much as weird as it sounds. All new machine, forklifted
the image
Closest would be
http://www.freebsd.org/news/status/report-2008-01-2008-03.html#ProPolice-support-for-FreeBSD
but port part it was not committed.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/CLANG-and-fstack-protector-tp5784739p5784992.html
Sent from the
on 08/02/2013 13:48 Ulrich Spörlein said the following:
The problem here is that I login via my user account, then either use
sudo or sudo -i for a root shell, this however does not raise the
memorylocked limit. So when I said this works during boot and shortly
after, it's because I haven't
On 8 February 2013 07:46, Andriy Gapon a...@freebsd.org wrote:
on 08/02/2013 13:48 Ulrich Spörlein said the following:
The problem here is that I login via my user account, then either use
sudo or sudo -i for a root shell, this however does not raise the
memorylocked limit. So when I said this
I've been spending some time trying to get the fasttrap provider to work
on FreeBSD without panicing. I believe I have succeeded, at least to the
point where it's no longer panicing.
There were two panic causes. The first was
http://www.freebsd.org/cgi/query-pr.cgi?pr=165541 - the FreeBSD port of
Thomas Mueller writes:
I built the newer Xorg and it falls flat: goes to a nongraphic
screen that is blank except for a rectangular cursor in the upper
left corner, and now I want to get back to the earlier Xorg.
System is Intel Sandy Bridge with i7 CPU.
Robert Huff responds:
For those that may have run across the story on Slashdot about this NIC,
here is our statement:
Recently there were a few stories published, based on a blog post by an
end-user, suggesting specific network packets may cause the Intel® 82574L
Gigabit Ethernet Controller to become unresponsive
Hi
I get this panic on insertion of a uath USB dongle.
On amd-64:
uath0: Atheros Communications Inc USB WLAN Device, rev 2.00/0.01, addr 3 on us
bus1
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x0
fault code = supervisor write
On Fri, 8 Feb 2013, Thomas Mueller wrote:
Thomas Mueller writes:
I built the newer Xorg and it falls flat: goes to a nongraphic
screen that is blank except for a rectangular cursor in the upper
left corner, and now I want to get back to the earlier Xorg.
System is Intel Sandy Bridge with
On Friday 08 February 2013 19:21:24 Ian FREISLICH wrote:
Uptime: 7s
Dumping 237 out of 3971
MB:..7%..14%..21%..34%..41%..54%..61%..75%..81%..95%
Reading symbols from /boot/kernel/acpi_asus_wmi.ko...Reading symbols from
/boot/kernel/acpi_asus_wmi.ko.symbols...done. do
Maybe you can also
On Friday 08 February 2013 19:21:24 Ian FREISLICH wrote:
Hi
I get this panic on insertion of a uath USB dongle.
On amd-64:
uath0: Atheros Communications Inc USB WLAN Device, rev 2.00/0.01, addr 3
on us bus1
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
Hi,
Your problem should be fixed by:
http://svnweb.freebsd.org/changeset/base/246565
Please test and report back if it doesn't.
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On Friday 08 February 2013 22:18:24 Hans Petter Selasky wrote:
Hi,
Your problem should be fixed by:
http://svnweb.freebsd.org/changeset/base/246565
Please test and report back if it doesn't.
FYI: This is only a problem in -current, because the changes which introduced
this behaviour
Hans Petter Selasky wrote:
On Friday 08 February 2013 19:21:24 Ian FREISLICH wrote:
Uptime: 7s
Dumping 237 out of 3971
MB:..7%..14%..21%..34%..41%..54%..61%..75%..81%..95%
Reading symbols from /boot/kernel/acpi_asus_wmi.ko...Reading symbols from
On Friday 08 February 2013 22:43:17 Ian FREISLICH wrote:
Hans Petter Selasky wrote:
Hi,
Your problem should be fixed by:
http://svnweb.freebsd.org/changeset/base/246565
Please test and report back if it doesn't.
It doesn't panic anymore. Thanks. There's a new problem though:
On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote:
recommends contacting your motherboard manufacturer if you have continued
concerns or questions whether your products are impacted.
Here is the link:
From Warren Block wbl...@wonkity.com:
After adding those, graphics/libdrm must be rebuilt, and
x11-drivers/xf86-video-intel must have the KMS option enabled and be
rebuilt. If you just added WITH_NEW_XORG, there will be other xorg
components that need to be updated.
O no, I'm getting rid of
Hi,
I suspect something is broken with memsticks built from HEAD. I noticed that I
couldn't boot the latest HEAD (amd64) memstick snapshot on two machines
(Lenovo X220 and HP ProLiant ML350 G5). Trying snapshots from the FreeBSD.org
FTP or allbsd.org makes no difference.
It boots fine until
21 matches
Mail list logo
