If you let bsdtar continue, and press control-T a few times, does the
user time (u) increase at all? Does it ever go any further, if you let
it run for a very long time?
I believe a problem may have been introduced by r277922, leading to
filesystem hangs in some scenarios. It looks like this com
On Thursday, February 5, 2015, Peter Wemm wrote:
> On Wednesday, February 04, 2015 04:29:41 PM Konstantin Belousov wrote:
> > On Tue, Feb 03, 2015 at 01:33:15PM -0800, Peter Wemm wrote:
> > > Sometime in the Dec 10th through Jan 7th timeframe a timing bug has
> been
> > > introduced to 11.x/head/
The release is the latest snapshot memstick image and kernel is from
https://github.com/dumbbell/freebsd/tree/kms-drm-update-38.
I think this problem existed before I changed kernel.
I haven't changed any settings on the filesystem so I assume TRIM is off.
When stopped "bsdtar" is in state "flsw
On 2015-02-04 20:40, Lundberg, Johannes wrote:
> By the way,
>
> For the second test I first ran portsnap extract without removing the old
> /usr/ports folder and it ran through quickly without any halts..
>
> --
> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD.
>
> On Thu, Feb 5, 2015 at 10:38 A
On 05 Feb 2015, at 02:38, Lundberg, Johannes
wrote:
>
> I deleted /usr/ports and did a new portsnap extract
>
> portsnap stopped at /usr/ports/editors/teco
>
> that folder is empty and the previous folder (editors/tea) is populated
> with files.
>
> portsnap stopped for about 2-3 minutes and
By the way,
For the second test I first ran portsnap extract without removing the old
/usr/ports folder and it ran through quickly without any halts..
--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.
On Thu, Feb 5, 2015 at 10:38 AM, Lundberg, Johannes <
johan...@brilliantservice.co.jp> wrote:
>
On Wed, Feb 04, 2015 at 08:21:44AM -0800, Adrian Chadd wrote:
> ... god, people go through a lot of work to not have to write a wifi driver.
> :)
we're just concerned about you...
...r sanity.
mcl
___
freebsd-current@freebsd.org mailing list
http://li
I deleted /usr/ports and did a new portsnap extract
portsnap stopped at /usr/ports/editors/teco
that folder is empty and the previous folder (editors/tea) is populated
with files.
portsnap stopped for about 2-3 minutes and during the whole time gstat
showed values like this: (disc io load was co
On 2015-02-04 19:29, Lundberg, Johannes wrote:
> Hi
>
> I'm thought I was gonna do some test runs with HEAD on a 2013 Macbook Air
> and noticed some weird behavior regarding disk I/O.
>
> This happens both when doing portsnap extract and clone from git repository.
>
> For example portsnap extrac
Hi
I'm thought I was gonna do some test runs with HEAD on a 2013 Macbook Air
and noticed some weird behavior regarding disk I/O.
This happens both when doing portsnap extract and clone from git repository.
For example portsnap extract, the extraction process (the output of it)
suddenly stops, fo
On Wednesday, February 04, 2015 04:29:41 PM Konstantin Belousov wrote:
> On Tue, Feb 03, 2015 at 01:33:15PM -0800, Peter Wemm wrote:
> > Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been
> > introduced to 11.x/head/-current.With HZ=1000 (the default for bare
> > metal, no
I have a quick question regarding the vt driver which hopefully someone
involved in its design could answer for me.
Roughly 4 months ago, vt gained the ability to listen to a set of
keyboard combinations controlling power/debug situations and the ability
to control (or more precisely, turn off) th
Just a quick report that from my completely unscientific observations it
seems that battery life is extended with the latest drm import on my
Thinkpad X230. I should probably get some numbers first, but my gut
feeling is that it is better.
By the way on the X230 (IvyBridge i7) the loader.conf sett
On 4 February 2015 at 09:29, Konstantin Belousov wrote:
>
> So the issue is reproducable in 3 minutes after boot with the following
> change in kern_clock.c:
> volatile intticks = INT_MAX - (/*hz*/1000 * 3 * 60);
>
> It is fixed (in the proper meaning of the word, not like worked around,
> cov
So it seems that some change between 10 and 4 days ago to the i915kms subsystem
introduced a regression with which loading i915kms through either console, or
Xorg, blanks the screen and makes the system unresponsive in that changing to
another tty, or from Xorg back to tty, does not yield any un-bl
On 2015-02-04 10:11, Claudius Chan wrote:
> Hi,
> this is my first post in this mailing list. I hope this is the correct way
> to post it here.
>
> I have issue when enable the Vt-x/AMD in Virtuabox, after the virtual
> machine boot up. kernel panic happened.
>
> I currently using Virtualbox vers
On a Minnowboard I've the same behavior, 800x600 it boots, at 1024x768
it crash, using a DVI display.
best regards,
pizzamig
On Wed, Feb 4, 2015 at 2:04 PM, Jakob Alvermark wrote:
>
> On 31 dec 2014, at 16:24, Jakob Alvermark wrote:
>
>> On Tue, December 30, 2014 17:00, Nathan Whitehorn wrote:
On 02/04/2015 10:11 AM, Claudius Chan wrote:
Hi,
this is my first post in this mailing list. I hope this is the correct way
to post it here.
I have issue when enable the Vt-x/AMD in Virtuabox, after the virtual
machine boot up. kernel panic happened.
I currently using Virtualbox version:
$ pkg
... god, people go through a lot of work to not have to write a wifi driver. :)
-a
On 4 February 2015 at 01:06, Lars Engels wrote:
> On Wed, Feb 04, 2015 at 12:04:21AM +, Gavin Atkinson wrote:
>> On Mon, 2 Feb 2015, R0B_ROD wrote:
>> > Thank you for the time you took to help.
>> >
>> > Ac
On Tuesday, February 03, 2015 10:33:36 PM Konstantin Belousov wrote:
> On Mon, Feb 02, 2015 at 09:50:22PM -0600, Eric Badger wrote:
> > On 02/02/2015 03:30 AM, Konstantin Belousov wrote:
> > > On Sun, Feb 01, 2015 at 08:38:29PM -0600, Eric Badger wrote:
> > >> On 01/31/2015 09:36 AM, Konstantin Bel
On 02/04/2015 10:11 AM, Claudius Chan wrote:
Hi,
this is my first post in this mailing list. I hope this is the correct way
to post it here.
I have issue when enable the Vt-x/AMD in Virtuabox, after the virtual
machine boot up. kernel panic happened.
I currently using Virtualbox version:
$ pkg
Hi,
this is my first post in this mailing list. I hope this is the correct way
to post it here.
I have issue when enable the Vt-x/AMD in Virtuabox, after the virtual
machine boot up. kernel panic happened.
I currently using Virtualbox version:
$ pkg info |grep virtual
virtualbox-ose-4.3.20_4
On Tue, Feb 03, 2015 at 01:33:15PM -0800, Peter Wemm wrote:
> Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been
> introduced to 11.x/head/-current.With HZ=1000 (the default for bare
> metal,
> not for a vm); the clocks stop just after 24 days of uptime. This means
>
On 02/03/2015 02:33 PM, Konstantin Belousov wrote:
On Mon, Feb 02, 2015 at 09:50:22PM -0600, Eric Badger wrote:
On 02/02/2015 03:30 AM, Konstantin Belousov wrote:
On Sun, Feb 01, 2015 at 08:38:29PM -0600, Eric Badger wrote:
On 01/31/2015 09:36 AM, Konstantin Belousov wrote:
First, shouldn't
On 31 dec 2014, at 16:24, Jakob Alvermark wrote:
> On Tue, December 30, 2014 17:00, Nathan Whitehorn wrote:
>>
>
>> On 12/30/14 06:40, Jakob Alvermark wrote:
>>
>>> Hi,
>>>
>>>
>>> Have been playing with this machine for a while now.
>>> It is a quad core Pentium N3540 (ValleyView/Bay Trail)
Hi Ed,
I've got a running MinnowBoard.
All problems are not FreeBSD related, but with DVI display.
Setting a fixed resolution instead of a "Auto" solved the problem.
Thanks for the help
Best regards,
pizzamig
PS I'll try to get a GetMemoryMap() / ExitBootServices() retry next week
On Fri, Jan
On Wed, Feb 04, 2015 at 12:04:21AM +, Gavin Atkinson wrote:
> On Mon, 2 Feb 2015, R0B_ROD wrote:
> > Thank you for the time you took to help.
> >
> > According to:
> >http://lists.freebsd.org/pipermail/ \
> >\ freebsd-current/2013-July/042788.html
> >\ freebsd-questions/2014-August
27 matches
Mail list logo
