Thu Jan 19 18:03:38 CST 2017
FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997:
Sat Jan 14 22:35:29 CST 2017
r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64
panic: racct_adjust_resource: resource 4 usage < 0
GNU gdb (GDB) 7.12 [GDB v7.12 for FreeBSD]
Copyright
Hi Adrian,
I was looking at the source for the vt driver. Wondering how much work it is to
add VESA support to the VGA backend? As you say ATM it's hardcoded to use
640x480. Pardon my ignorance, but can we reuse any VESA code from syscons?
Also, how dependent is splash/screensaver support on th
FreeBSD_HEAD_i386 - Build #4695 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4695/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4695/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4695/console
Change summaries:
312
On Thu, Jan 19, 2017 at 08:50:34PM +0100, Andreas Nilsson wrote:
> On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber wrote:
> > I do want to weigh in here and inform I am actively watching this
> > thread. clang(1) is not in disc1.iso or bootonly.iso because the
> > MK_TOOLCHAIN knob is disabled in th
On Wed, Jan 18, 2017 at 02:45:34PM -0500, Shawn Webb wrote:
> On Wed, Jan 18, 2017 at 07:31:12AM -0700, Sean Bruno wrote:
> >
> >
> > On 01/18/17 03:37, peter.b...@bsd4all.org wrote:
> > > Hi,
> > >
> > > A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr.
> > > Since GENERIC
On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber wrote:
> On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote:
> > On Thu, 19 Jan 2017 06:58:16 +0100
> > Matthias Apitz wrote:
> >
> > > El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude
> > > escribió:
> > >
> > > > On 201
On Thu, Jan 19, 2017 at 07:10:00PM +, Glen Barber wrote:
> On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote:
> > On Thu, 19 Jan 2017 06:58:16 +0100
> > Matthias Apitz wrote:
> >
> > > El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude
> > > escribió:
> > >
> > >
On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote:
> On Thu, 19 Jan 2017 06:58:16 +0100
> Matthias Apitz wrote:
>
> > El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude
> > escribió:
> >
> > > On 2017-01-18 14:37, O. Hartmann wrote:
> > > > Am Wed, 18 Jan 2017 16:3
On Sat, Dec 17, 2016 at 1:34 AM, Poul-Henning Kamp wrote:
> I've seen it too. I think beastie sets a scrolling region and
> doesn't clear it.
FWIW- I got some time to mess with it again today, and disabling
beastie (via beastie_disable="YES" in /boot/loader.conf) entirely does
not change the sit
Can someone comment on the status on the ClearFOG PRO?? Ive seen recent commits
going into the tree that mention it specifically in the DTS file, Is
an image buildable? What
is working now, what is not? I have two that need some FreeBSD love.
___
freebsd-
If you plan on running a desktop environment like this make sure its super
speed usb 3.0 or the system will be considerably slow. This is a perfect
backup plan and I always have one for the ready. This is especially
important when on current. I don't think you have to worry so much about
having a s
FreeBSD_HEAD_i386 - Build #4694 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4694/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4694/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4694/console
Change summaries:
3
Hello
I tried both patches (separately) which were suggested in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215898
on FreeBSD-current r312404 today, and now I can confirm that both solved the
original problem, the patched kernel boots and no USB_ERR_TIMEOUT nor
USB_ERR_IOERROR me
I'm utilizing two systems running FreeBSD Current (most recent) on top of
Asrock Z77 M4pro main PCBs (one is the uATX version, the other regular ATX). The
firmware is the last one a customer can pick up from Asrock's website and it is
dated from 2013. Apart from the fact that the hardware is not us
On Thu, Jan 19, 2017 at 4:23 PM, Hans Petter Selasky
wrote:
>
> I can add prints/asserts to show that what happens is that
> "state->nextcallopt > now" while "state->nextcall <= now". This situtation
> is allowed to persist due to the way getnextcpuevent() is currently
> implemented.
>
> Can the
On 01/19/17 11:13, M&S - Krasznai András wrote:
Did anybody experience similar things?
Yes, it might be related to EARLY AP startup.
There is a PR with two patches attached which you can try:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215898
--HPS
_
Hi
I have FreeBSD-current on a Lenovo T510 laptop.
Since a few weeks I observe the following error messages during boot:
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
uhub2: 8 ports with 8 removable, self powered
usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignore
El día Thursday, January 19, 2017 a las 10:16:46AM +0100, O. Hartmann escribió:
> I created images on CURRENT of my own - they all lack in the ability of having
> the necessary tools aboard. So I consider every image useless for rescue
> operations except, maybe, the DVD image - but this one is no
Hi list,
i use 12 current, and will update to r312404.
Buildworld stop with this error:
===> bios (install)
===> bios/smbios (install)
install -T release -o root -g wheel -m 555 smbios.ko /boot/kernel/
install: smbios.ko: No such file or directory
*** Error code 71
Stop.
bmake[5]: stopped in
On Thu, 19 Jan 2017 06:58:16 +0100
Matthias Apitz wrote:
> El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude
> escribió:
>
> > On 2017-01-18 14:37, O. Hartmann wrote:
> > > Am Wed, 18 Jan 2017 16:38:32 +0100
> > > Matthias Apitz schrieb:
> > >
> > >> Why you do not just
On Wed, January 18, 2017 19:29, John Baldwin wrote:
> On Tuesday, January 17, 2017 01:46:31 PM Jakob Alvermark wrote:
>
>> On Fri, January 13, 2017 22:46, Jakob Alvermark wrote:
>>
>>> On Fri, January 13, 2017 19:44, John Baldwin wrote:
>>>
>>>
On Friday, January 13, 2017 09:58:01 AM Jakob Alv
On 01/18/17 09:00, Hans Petter Selasky wrote:
On 01/18/17 02:18, John Baldwin wrote:
You might still want to adjust 'nextevent' to schedule the next interrupt
to be sooner than 'timerperiod' though. You could just set
'nextevent' to
'now' in that case instead of 'next'.
Right, I'll give that
22 matches
Mail list logo