On Fri, 14 Jun 2013 16:00:11 -0700, matt wrote
I'm glad you got this working, it makes the X220 (and probably
other laptops with similar issues) more usable on FreeBSD.
Sure, that's good news !
I'll have to bring my X220 back up to current and start
looking at sleep issues next.
Great !
Hi,
something changed in the last 2-3 weeks on -CURRENT that causes reboots to hang
after this line:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
I need to manually cycle the power to reboot.
Any clues?
Thanks,
Lars
___
/usr/src/contrib/wpa/src/utils/base64.h:15:9: warning: 'BASE64_H' is used as a
header guard here, followed by #define of a different macro [-Wheader-guard]
#ifndef BASE64_H
^~~~
/usr/src/contrib/wpa/src/utils/base64.h:16:9: note: 'BASE64_h' is defined here;
did you mean 'BASE64_H'?
Hi,
any further ideas? This issue still exist when building -CURRENT on -STABLE as
of today.
Thanks,
Lars
On May 23, 2013, at 12:33, Eggert, Lars l...@netapp.com wrote:
Hi,
On May 22, 2013, at 13:37, Dimitry Andric d...@freebsd.org wrote:
Can you try to figure out which copy of clang
My laptop can shutdown after this patch, however I receive the following
messages:
Jun 17 09:34:03 notebook kernel: error: [drm:pid12:i915_hangcheck_ring_idle]
*ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 7438, at 7438],
missed IRQ?
Jun 17 09:36:08 notebook kernel: error:
On 6/17/2013 6:58 AM, Eggert, Lars wrote:
Hi,
any further ideas? This issue still exist when building -CURRENT on -STABLE
as of today.
Thanks,
Lars
ccache is known to be broken with clang [1]. I would recommend not using it.
Sometimes CCACHE_CPP2=1 in make.conf can help. CCACHE_CPP2=1
On 17 June 2013 05:48, Eggert, Lars l...@netapp.com wrote:
Hi,
something changed in the last 2-3 weeks on -CURRENT that causes reboots to
hang after this line:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
I need to manually cycle the power to reboot.
Any clues?
On Jun 17, 2013, at 15:18, Luiz Otavio O Souza lists...@gmail.com
wrote:
It was a change on alq. The fix was committed in r251838.
Awesome! I can confirm it's fixed.
Lars
___
freebsd-current@freebsd.org mailing list
Hi,
On Jun 17, 2013, at 14:51, Bryan Drewery bdrew...@freebsd.org wrote:
ccache is known to be broken with clang [1]. I would recommend not using it.
Pity! We do buildworld often enough that that's an inconvenience.
Sometimes CCACHE_CPP2=1 in make.conf can help. CCACHE_CPP2=1 is
hardcoded in
On 2013-03-28, Andriy Gapon wrote:
Would like to ask for opinions on this topic...
Please read this PR for context:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122838
So I would like to commit the following patch sooner rather than later:
I have revised the patch slightly:
On Jun 17, 2013, at 9:02, Eggert, Lars l...@netapp.com wrote:
Hi,
On Jun 17, 2013, at 14:51, Bryan Drewery bdrew...@freebsd.org wrote:
ccache is known to be broken with clang [1]. I would recommend not using it.
Pity! We do buildworld often enough that that's an inconvenience.
I have
I am able to reproduce this on a Supermicro X8-something that I have. A
git bisect took me down a strange path into a /projects branch. It is
possible the branch got a bad merge from -CURRENT at one point; I'm still
trying to narrow down where things went wrong (and even whether the branch
is
Hi all,
It's that time again! On behalf of monthly@, I would like to inform
you that the next submission date for the April to June quarterly
status reports is July 7th, 2013 - less than a month away.
They don't have to be very long - anything that lets people know what
is going on inside
I have this problem from the beginning (more than year now), I already
wrote about that on current@ some time ago. The problem is that it
appears sporadically (but always in not very suitable moment) and I
can't see anything on terminal, so it's hard to debug/complain.
So I just updated to
Hi Everyone,
If English is not your first language and / or you are not confident about your
writing, please don't let this stop you from submitting something. A native
English speaker (probably me) will read through everything before publication
and fix any errors. As long as the technical
If so, what is the perferred way of doing so?
By PR?
Jimmy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Mon, Jun 17, 2013 at 10:52 AM, d...@gmx.com wrote:
/usr/src/contrib/wpa/src/utils/base64.h:15:9: warning: 'BASE64_H' is used as
a header guard here, followed by #define of a different macro
[-Wheader-guard]
This has been fixed by pluknet and I. Curious though. which compiler
is this? I
On Mon, Jun 17, 2013 at 10:35 PM, Eitan Adler li...@eitanadler.com wrote:
On Mon, Jun 17, 2013 at 10:52 AM, d...@gmx.com wrote:
/usr/src/contrib/wpa/src/utils/base64.h:15:9: warning: 'BASE64_H' is used as
a header guard here, followed by #define of a different macro
[-Wheader-guard]
This
+1 to the question, reported 2 a while ago, one for PF and one for FS.
Gleb quickly fixed the PF one, never had a reply from anyone on FS though.
I still have it with -CURRENT from last week, can report again.
On 17 Jun 2013, at 21:54, Jimmy Kelley ljboi...@gmail.com wrote:
If so, what is
On 16 Jun 2013, at 23:48, Kirk McKusick wrote:
I suppose it's safe to say further comment isn't forthcoming. So with
one vote for and one against (or at least questioning), I'll humbly
leave it up to myself to be the tie-breaker :-).
Here's a proposed patch. I separate kmem access into
When I switched on tso on debian AMT stopped too.
2013/5/27 Kamil Czekirda kczeki...@gmail.com:
From observation:
volt% amttool-tng k5 rem_control info
## 'k5' :: AMT Remote Control
FAULT: 500 Can't connect to k5:16992 (Invalid argument)
(1)
k5% sudo ifconfig em0
em0:
I have tried to install
ftp://ftp1.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/10.0/FreeBSD-10.0-CURRENT-amd64-20130616-r251797-release.iso
Installation has failed due to a corrupted disk from a previous
installation
by another operating system :
In the first attempt ,
when Entire
On Mon, 17 Jun 2013, Damien Fleuriot wrote:
+1 to the question, reported 2 a while ago, one for PF and one for FS.
Gleb quickly fixed the PF one, never had a reply from anyone on FS though.
I still have it with -CURRENT from last week, can report again.
Those FS LORs (from 10-CURRENT
TB --- 2013-06-17 22:50:17 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-17 22:50:17 - 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 ---
TB --- 2013-06-17 22:50:17 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-06-17 22:50:17 - 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 ---
25 matches
Mail list logo
