On Wed, 18 Dec 2013 23:40:23 -0800
Adrian Chadd wrote:
> What's at frame 10?
>
> And list the IP, ie:
>
> list *0x817da911
>
(kgdb) f 10
#10 0x817da911 in rt2860_tx (sc=0xfe9bd000,
m=0xf80004c6dd00, ni=0x0)
at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1472 14
On 19/12/2013 08:04, Freddie Cash wrote:
> On Wed, Dec 18, 2013 at 1:09 PM, Matthias Apitz wrote:
>> Ok, thanks; but see this:
>>
>> $ uname -a
>> FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18
>> 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386
>> $
Am 30.11.2013 14:56, schrieb Konstantin Belousov:
> I propose to unconditionally add the switch -fno-strict-overflow
> to the kernel compilation. See the patch at the end of message for
> exact change proposed.
>
> What does it do. It disallows useless and counter-intuitive
> behaviour of the co
On 16 Dec 2013, at 21:35, Dimitry Andric wrote:
> In any case, if anything like this is implemented, I would really prefer
> something like CMake does, e.g. give you a percentage counter that
> provides some information about how 'far' the build is progressing.
I haven't seen this for a while, b
On Thu, Dec 19, 2013 at 1:18 AM, David Chisnall wrote:
> On 16 Dec 2013, at 21:35, Dimitry Andric wrote:
>
> > In any case, if anything like this is implemented, I would really prefer
> > something like CMake does, e.g. give you a percentage counter that
> > provides some information about how 'f
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
> Your usb wlan dongles use RTL8188EU chip which is currently not
> supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is id-patch urtwn(4). ;-)
Does anyone know if sup
On 19 Dec 2013, at 09:40, Luigi Rizzo wrote:
>
>> If a command produces warning output but exits with success, then that
>> command's output is dumped to stdout (explicitly serialised by Ninja so that
>> it's never interleaved with another command's output).
>>
>> If a command exits with a fa
I had (still have) svn on a USB-stick installation of FreeBSD 9.2-STABLE.
So I tried to use that to checkout the src tree for FreeBSD-HEAD; re(4)
recognized my on-motherboard (MSI Z77 MPOWER) Ethernet but couldn't connect.
So, after NetBSD 6.1_STABLE hung consistently on boot, NetBSD-current amd
Hello!
My system:
FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 08:18:20 UTC 2013
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
I have a problem to install last.fm from FreeBSD 10.0-ALPHA:
/usr/local/bin/ld: ../build/last.fm/release/AbstractBootstrapper.o: undefined
reference to symb
On 12/19/13, Stefan Esser wrote:
> Am 30.11.2013 14:56, schrieb Konstantin Belousov:
>> I propose to unconditionally add the switch -fno-strict-overflow
>> to the kernel compilation. See the patch at the end of message for
>> exact change proposed.
>>
>> What does it do. It disallows useless and
On Thu, Dec 19, 2013 at 06:37:42AM -0500, Ajtim wrote:
> Hello!
>
> My system:
> FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 08:18:20 UTC 2013
> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>
> I have a problem to install last.fm from FreeBSD 10.0-ALPHA:
>
> /usr/local/bin/ld: ../b
> On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
> > Your usb wlan dongles use RTL8188EU chip which is currently not
> > supported by any of drivers.
> I see; I guess I should not have believed when I was told that most likely
> all it would take is id-patch urtwn(4). ;-)
> Does anyone
On Thu, Dec 19, 2013 at 12:33 PM, Thomas Mueller
wrote:
> Better would be if manufacturers' and online vendors' websites would say what
> chipset their Ethernet, Bluetooth adapter, USB wi-fi adapter, etc use.
>
I think manufacturers don't consider this relevant info, they sell
features, not the
On 12/17/13 17:28, Aleksandr Rybalko wrote:
On 18.12.2013 01:27, Nathan Whitehorn wrote:
On 12/17/13 15:32, Aleksandr Rybalko wrote:
On Tue, 17 Dec 2013 14:12:05 -0600
Nathan Whitehorn wrote:
On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrot
Does anybody else have issues with running i386 FreeBSD 10 under Virtual Box?
I have been running a number of different versions of FreeBSD under Virtual
Box for some time without any issues. Last week I installed amd64 FreeBSD
10 rc1 without any issue. Yesterday I decided to try i386 FreeBSD 10
Larry,
On Thu, Dec 19, 2013 at 09:51:16AM -0500, Larry Baird wrote:
L> Does anybody else have issues with running i386 FreeBSD 10 under Virtual Box?
L> I have been running a number of different versions of FreeBSD under Virtual
L> Box for some time without any issues. Last week I installed amd6
Gleb,
> On Thu, Dec 19, 2013 at 09:51:16AM -0500, Larry Baird wrote:
> L> Does anybody else have issues with running i386 FreeBSD 10 under Virtual
> Box?
> L> I have been running a number of different versions of FreeBSD under Virtual
> L> Box for some time without any issues. Last week I instal
On Thu, Dec 19, 2013 at 09:57:38AM +, David Chisnall wrote:
>
> On 19 Dec 2013, at 09:40, Luigi Rizzo wrote:
...
> >> Oh, and when I do a build of LLVM/Clang on my laptop using Ninja, it takes
> >> about 3-5 minutes, whereas when I do it with our build system it takes
> >> about 15. When I
On Thu, Dec 19, 2013 at 10:16:16AM +0100, Stefan Esser wrote:
> Am 30.11.2013 14:56, schrieb Konstantin Belousov:
> > I propose to unconditionally add the switch -fno-strict-overflow
> > to the kernel compilation. See the patch at the end of message for
> > exact change proposed.
> >
> > What do
This series is a split of the previous patch "Xen x86 DomU PVH
support", with the aim to make the review of the code easier.
The series can also be found on my git repo:
git://xenbits.xen.org/people/royger/freebsd.git pvh_v7
or
http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=short
---
sys/xen/xen-os.h |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/sys/xen/xen-os.h b/sys/xen/xen-os.h
index c7474d8..e8a5a99 100644
--- a/sys/xen/xen-os.h
+++ b/sys/xen/xen-os.h
@@ -82,6 +82,13 @@ xen_hvm_domain(void)
return (xen_domain_type == XEN_HVM_DOM
This should not introduce any functional change, and makes the
functions suitable to be called before we have actually mapped the
vcpu_info struct on a per-cpu basis.
---
sys/dev/xen/timer/timer.c | 29 -
1 files changed, 20 insertions(+), 9 deletions(-)
diff --git a
Add the PV/PVH entry point and the low level functions for PVH
initialization.
---
sys/amd64/amd64/locore.S | 53 +++
sys/amd64/amd64/machdep.c| 72 ++
sys/amd64/include/asmacros.h | 26 +++
sys/i386/xen/
---
sys/conf/files.amd64 |1 +
sys/x86/xen/mptable.c | 136 +
2 files changed, 137 insertions(+), 0 deletions(-)
create mode 100644 sys/x86/xen/mptable.c
diff --git a/sys/conf/files.amd64 b/sys/conf/files.amd64
index bdc1517..3bdc05e 100644
-
---
sys/amd64/amd64/machdep.c | 45 +
sys/amd64/include/sysarch.h | 12 +
sys/conf/files.amd64|1 +
sys/x86/xen/pv.c| 114 +++
sys/xen/pv.h| 28 +++
5 files changed, 189 insertions(
---
sys/amd64/amd64/machdep.c | 50 ++
sys/amd64/include/pc/bios.h |2 +
sys/amd64/include/sysarch.h |1 +
sys/x86/xen/pv.c| 26 ++
4 files changed, 60 insertions(+), 19 deletions(-)
diff --git a/sys/amd64/amd64
This adds and enables the console used on XEN kernels.
---
sys/amd64/amd64/machdep.c |4 +++
sys/conf/files |4 +-
sys/dev/xen/console/console.c | 45 ++-
sys/dev/xen/console/xencons_ring.c | 15
sys/i386/in
On PVH we don't need to init the shared info page, or disable emulated
devices. Also, make sure PV IPIs are set before starting the APs.
---
sys/x86/xen/hvm.c | 17 -
1 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/sys/x86/xen/hvm.c b/sys/x86/xen/hvm.c
index 9a041
Since Xen PVH guests doesn't have ACPI, we need to create a dummy
pvcpu device that will be used to fill the pcpu->pc_device field.
---
sys/conf/files.amd64 |1 +
sys/x86/xen/pvcpu.c | 84 ++
2 files changed, 85 insertions(+), 0 deletions(-)
---
sys/xen/gnttab.c | 26 +-
1 files changed, 21 insertions(+), 5 deletions(-)
diff --git a/sys/xen/gnttab.c b/sys/xen/gnttab.c
index 03c32b7..6949be5 100644
--- a/sys/xen/gnttab.c
+++ b/sys/xen/gnttab.c
@@ -25,6 +25,7 @@ __FBSDID("$FreeBSD$");
#include
#include
#i
---
sys/xen/xenstore/xenstore.c | 21 ++---
1 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/sys/xen/xenstore/xenstore.c b/sys/xen/xenstore/xenstore.c
index bcf6357..2893c84 100644
--- a/sys/xen/xenstore/xenstore.c
+++ b/sys/xen/xenstore/xenstore.c
@@ -229,13 +229
Introduce a Xen specific nexus that is going to be in charge for
attaching Xen specific devices. Remove the identify routine from Xen
devices and instead attach them from the nexus (PV/PVH) or xenpci
(HVM).
---
sys/conf/files.amd64|1 +
sys/conf/files.i386 |1 +
sys/dev/xen
PVH guests don't have an emulated lapic.
---
sys/amd64/amd64/mp_machdep.c | 10 ++
sys/amd64/include/apicvar.h |1 +
sys/i386/include/apicvar.h |1 +
sys/i386/xen/xen_machdep.c |2 ++
sys/x86/x86/local_apic.c |8 +---
sys/x86/xen/pv.c |3 +++
Add the PV shutdown hook to PVH.
---
sys/dev/xen/control/control.c | 37 ++---
1 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/sys/dev/xen/control/control.c b/sys/dev/xen/control/control.c
index bc0609d..78894ba 100644
--- a/sys/dev/xen/control/co
AP startup on PVH follows the PV method, so we need to add a hook in
order to diverge from bare metal.
---
sys/amd64/amd64/mp_machdep.c | 16 ---
sys/amd64/include/cpu.h |1 +
sys/x86/xen/hvm.c| 17 +++-
sys/x86/xen/pv.c | 90 +
---
sys/x86/isa/isa.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/sys/x86/isa/isa.c b/sys/x86/isa/isa.c
index 1a57137..09d1ab7 100644
--- a/sys/x86/isa/isa.c
+++ b/sys/x86/isa/isa.c
@@ -241,3 +241,6 @@ isa_release_resource(device_t bus, device_t child, int
type, int
This hook will only be implemented for bare metal, Xen doesn't require
any bootstrap code since APs are started in long mode with paging
enabled.
---
sys/amd64/amd64/machdep.c |6 +-
sys/amd64/include/sysarch.h |3 +++
2 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/sy
Larry,
On Thu, Dec 19, 2013 at 10:33:32AM -0500, Larry Baird wrote:
L> > On Thu, Dec 19, 2013 at 09:51:16AM -0500, Larry Baird wrote:
L> > L> Does anybody else have issues with running i386 FreeBSD 10 under
Virtual Box?
L> > L> I have been running a number of different versions of FreeBSD under
On Wednesday, December 18, 2013 5:45:57 pm Poul-Henning Kamp wrote:
> In message <201312181458.20649@freebsd.org>, John Baldwin writes:
>
> >> >Does it get a crashdump if you try?
> >>
> >> No :-(
> >>
> >> There may be a connection to unclean UFS filesystems (SU + TRIM, no J).
> >
> >Is thi
On Wed, Dec 18, 2013 at 2:40 PM, Outback Dingo wrote:
>
>
>
> On Wed, Dec 18, 2013 at 4:40 PM, Alan Somers wrote:
>>
>> On Wed, Dec 18, 2013 at 11:47 AM, Outback Dingo
>> wrote:
>> >
>> >
>> > On Wed, Dec 18, 2013 at 12:39 PM, Mark Felder wrote:
>> >>
>> >> On Thu, Oct 10, 2013, at 11:26, Alan
Well there's a null node pointer. Need to figure out why. Its totally legit
to have them too, so the code has to cope.
Grr.
Adrian
On Dec 19, 2013 2:07 AM, "Sergey V. Dyatko" wrote:
> On Wed, 18 Dec 2013 23:40:23 -0800
> Adrian Chadd wrote:
>
> > What's at frame 10?
> >
> > And list the IP, ie
It would appear, neither nor are any longer available on
FreeBSD current and 10.x
This breaks the devel/tcl-trf port, which I maintain... Could someone, please,
comment? Should I patch-up the port to disable the functionality? Or?..
Thank you!
-mi
_
TB --- 2013-12-20 03:09:31 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-20 03:09:31 - 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 2013/12/19 17:51, Alexey Dokuchaev wrote:
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
Your usb wlan dongles use RTL8188EU chip which is currently not
supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is id
TB --- 2013-12-20 04:12:42 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-20 04:12:42 - 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 Fri, Dec 20, 2013 at 01:35:37PM +0800, Kevin Lo wrote:
> I'd like to port it after finishing RT5373 driver support. :-)
Nice, looking forward to it. :)
> Here's a site you could use for info about your wireless device:
> http://wikidevi.com/wiki/TP-LINK_TL-WN723N_v3
Thank you Kevin.
./danfe
Thank you for doing the split.
On Thu, Dec 19, 2013 at 07:54:38PM +0100, Roger Pau Monne wrote:
> Add the PV/PVH entry point and the low level functions for PVH
> initialization.
> ---
> sys/amd64/amd64/locore.S | 53 +++
> sys/amd64/amd64/machdep.c| 72
>
47 matches
Mail list logo
