TB --- 2013-06-22 04:53:04 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-22 04:53:04 - 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 --- 2013
TB --- 2013-06-22 04:02:48 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-22 04:02:48 - 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 --- 2013
On Sat, Jun 22, 2013 at 12:29:49AM + I heard the voice of
Miguel Clara, and lo! it spake thus:
>
> The only way to turn off is but "force" and this can cause damage to
> filesystems, this is indeed a very big issue, and I'm not sure if
> its specific to KMS or some freebsd-current problem caus
On 22/06/2013, at 4:10, Ian FREISLICH wrote:
> I bought a relay control board that has a USB interface. It presents
> a serial port to Linux on /dev/ttyACMx. However when I plug it
> into my FreeBSD host, it detects as follows:
>
> ugen0.2: at usbus0
> umodem0: on usbus0
> umodem0: data inte
TB --- 2013-06-22 00:20:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-22 00:20:18 - 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 --- 2013
TB --- 2013-06-22 00:20:18 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-22 00:20:18 - 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 --- 2013
Mark Felder feld.me> writes:
>
> On Fri, 14 Jun 2013 12:05:13 -0500, Miguel Clara
gmail.com>
> wrote:
> >
> > I wouldn't consider having no visual output from a laptop when you
> > reboot/shutdown low priority...
> > But that's not for me to decide... in any case is there any Bug
> > Report/P
Hi,
I have the following kgdb session from a page fault seemingly triggered
in pf(4).
I realize the -CURRENT is about a month old, but I cannot find any
commits that seem relevant to this area of the code.
I am happy to dig further and provide any information that is requested.
Glen
Script sta
All,
I'd like to add some additional detail for
/etc/periodic/daily/450.status-security not working properly in all use
cases in PR conf/178611. After looking a bit closer at other versions,
I noticed that FreeBSD 10-CURRENT is also affected along with the
9.1-RELEASE that I use and mentioned
On 21.06.2013 01:56, Jeff Roberson wrote:
> On Thu, 20 Jun 2013, Jeff Roberson wrote:
>
>> On Wed, 19 Jun 2013, Zbyszek Bodek wrote:
>>
>>> Hello,
>>>
>>> I've been trying to compile the kernel on my ARMv7 platform using the
>>> sources from the current FreeBSD HEAD.
>>>
>>> make buildkernel <
Hi
I bought a relay control board that has a USB interface. It presents
a serial port to Linux on /dev/ttyACMx. However when I plug it
into my FreeBSD host, it detects as follows:
ugen0.2: at usbus0
umodem0: on usbus0
umodem0: data interface 1, has no CM over data, has no break
and I cannot
Hi,
You're right on the ability to boot off a gpt partition, with a non-uefi
bios. Sorry for the noise concerning that point.
Cheers
Roger
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
On Fri, Jun 21, 2013 at 8:08 AM, Genre Roger wrote:
> Hi,
>
> When I refer to gpart(8) manpage (9.1 release, updated jan 25,2013), I
> find the description of partition types a bit confusing.
>
> Considering the case of a MoBo with "old way" Bios (non UEFI), the only
> scheme allowed to get a boo
Hi,
When I refer to gpart(8) manpage (9.1 release, updated jan 25,2013), I
find the description of partition types a bit confusing.
Considering the case of a MoBo with "old way" Bios (non UEFI), the only
scheme allowed to get a bootable system is MBR. (Note that after
booting, your OS is abl
Unfortunately log is empty as a well as a lot of user files :( because of
fsck.
On Friday 21 June 2013 01:45:33 Oleg Sidorkin wrote:
> Check the logs for messages that can help to investigate the problem.
> If there is nothing helpful,
> I have no idea but to configure a serial console and see i
Hi,
Anyone got idea how to fix this compilation issue?
Regards,
Alie T
On Wed, Jun 19, 2013 at 12:08 PM, Alie Tan wrote:
> http://freshbsd.org/commit/freebsd/r251982
>
> ===> usr.bin (cleandir)
> "Makefile", line 370: Malformed conditional (${MK_SVN} == "yes" ||
> ${MK_SVNLITE} == "yes")
> "M
On 21.06.2013 04:02, Adrian Chadd wrote:
On 20 June 2013 16:45, Adrian Chadd wrote:
Hi,
I'm having issues with HPET + C3 state on this Atom N450 based
netbook. This is (shocking, I know!) running -HEAD (r251605.)
If I use C2, HPET is fine.
If I use RTC, i8254, LAPIC, C3 is also fine.
LAPIC
In attach file with dmesg log and usb debug enabled.
Maybe it's help?
Ryan Stone wrote:
RS> I am able to reproduce this on a Supermicro X8-something that I have. A
RS> git bisect took me down a strange path into a /projects branch. It is
RS> possible the branch got a bad merge from -CURRENT
18 matches
Mail list logo