On Tue, Dec 22, 2009 at 01:52:14PM +0800, James Chang wrote:
> Dears,
>
> Today, I use ctm upgrade my FreeBSD source code to "src-7 859"
> When I try to make world, in make buildworld stage it show me "World
> build completed on Tue Dec 22 12:57:30 CST 2009"
> But when I execute "make installw
Dear Sir,
My update steps as following:
1.ctm to the latest source
2.rm -rf /usr/orb/*
3.cd /usr/src
4.make buildworld
5.make buildkernel
7.make installkernel
8.make installworld
9.FAILED :<
Best Regards!
James Chang
2009/12/22 Andriy G
on 22/12/2009 07:52 James Chang said the following:
> Today, I use ctm upgrade my FreeBSD source code to "src-7 859"
> When I try to make world, in make buildworld stage it show me "World
> build completed on Tue Dec 22 12:57:30 CST 2009"
> But when I execute "make installworld" it show me the
On Tue, Dec 22, 2009 at 07:19:24AM +0100, Oliver Lehmann wrote:
> Jeremy Chadwick wrote:
>
> > If all you're looking for is CPU temperature, try looking at ACPI
> > thermal zones. Some BIOSes/mainboard manufacturers implement this on
> > workstations. Otherwise, if you have a Intel Core, C2D, or
On Tue, Dec 22, 2009 at 06:51:04AM +0100, Oliver Lehmann wrote:
> Andriy Gapon wrote:
>
> > BTW, mbmon haven't seen any updates in quite a long while, so it's missing
> > support for many newer chips.
> > Unfortunately, state of hardware/sensors monitoring is relatively poor in
> > FreeBSD.
>
>
Dears,
Today, I use ctm upgrade my FreeBSD source code to "src-7 859"
When I try to make world, in make buildworld stage it show me "World
build completed on Tue Dec 22 12:57:30 CST 2009"
But when I execute "make installworld" it show me the following ERROR message:
===> sys/boot/i386/btx (in
Jeremy Chadwick wrote:
> If all you're looking for is CPU temperature, try looking at ACPI
> thermal zones. Some BIOSes/mainboard manufacturers implement this on
> workstations. Otherwise, if you have a Intel Core, C2D, or C2Q CPU,
> load the coretemp(4) driver.
i7-920 in my case... and seems t
on 22/12/2009 07:51 Oliver Lehmann said the following:
> Andriy Gapon wrote:
>
>> BTW, mbmon haven't seen any updates in quite a long while, so it's missing
>> support for many newer chips.
>> Unfortunately, state of hardware/sensors monitoring is relatively poor in
>> FreeBSD.
>
> Hm so I guess
On Tue, Dec 22, 2009 at 06:51:04AM +0100, Oliver Lehmann wrote:
> Andriy Gapon wrote:
>
> > BTW, mbmon haven't seen any updates in quite a long while, so it's missing
> > support for many newer chips.
> > Unfortunately, state of hardware/sensors monitoring is relatively poor in
> > FreeBSD.
>
>
Andriy Gapon wrote:
> BTW, mbmon haven't seen any updates in quite a long while, so it's missing
> support for many newer chips.
> Unfortunately, state of hardware/sensors monitoring is relatively poor in
> FreeBSD.
Hm so I guess there is no other way in determining the CPUs temperature?
Why do
on 22/12/2009 07:34 Oliver Lehmann said the following:
> Andriy Gapon wrote:
>
>> You need ichsmb(4) driver for this hardware.
>
> Ok,
>
> now I got
>
> ichsmb0: port 0x400-0x41f mem
> 0xfb9fe000-0xfb9fe0ff irq 18 at device 31.3 on pci0
> ichsmb0: [ITHREAD]
> smbus0: on ichsmb0
> smb0: on s
Andriy Gapon wrote:
> You need ichsmb(4) driver for this hardware.
Ok,
now I got
ichsmb0: port 0x400-0x41f mem
0xfb9fe000-0xfb9fe0ff irq 18 at device 31.3 on pci0
ichsmb0: [ITHREAD]
smbus0: on ichsmb0
smb0: on smbus0
Any idea how to get mbmon to work?
r...@kartoffel olivleh1> mbmon
No Ha
Zane C.B. wrote:
With the GENERIC kernel on releng_8 and releng_8_0, I am having
issues with the Atheros wireless on my laptop.
Upon boot I am getting the message below.
ath0: irq 17 at device 0.0 on pci3
ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x).
ath0: cannot map register s
On Mon, 21 Dec 2009 22:32:40 -0500
Dan Langille wrote:
> Zane C.B. wrote:
> > With the GENERIC kernel on releng_8 and releng_8_0, I am having
> > issues with the Atheros wireless on my laptop.
> >
> > Upon boot I am getting the message below.
> >
> > ath0: irq 17 at device 0.0 on pci3
> > ath0
On Monday 21 December 2009 09:23:57 pm Zane C.B. wrote:
> With the GENERIC kernel on releng_8 and releng_8_0, I am having
> issues with the Atheros wireless on my laptop.
>
> Upon boot I am getting the message below.
>
> ath0: irq 17 at device 0.0 on pci3
> ath0: 0x1 bytes of rid 0x10 res 3
With the GENERIC kernel on releng_8 and releng_8_0, I am having
issues with the Atheros wireless on my laptop.
Upon boot I am getting the message below.
ath0: irq 17 at device 0.0 on pci3
ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x).
ath0: cannot map register space
device_attach:
With the GENERIC kernel on releng_8 and releng_8_0, I am having
issues with the Atheros wireless on my laptop.
Upon boot I am getting the message below.
ath0: irq 17 at device 0.0 on pci3
ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x).
ath0: cannot map register space
device_attach:
On Sun, 20 Dec 2009, Torfinn Ingolfsen wrote:
Hi,
I just booted my Dell OptiPlex SX260[1] from a usb memory stick with
FreeBSD 8.0-release on it. Part of the dmesg output is:
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
on 21/12/2009 18:42 Oliver Lehmann said the following:
> I got a new system (LGA-1366) with an X58 chipset.
> The SMB controller seems not to be supported? At least the smb driver
> does no good:
>
> no...@pci0:0:31:3: class=0x0c0500 card=0x3a301849 chip=0x3a308086
> rev=0x00 hdr=0x00
>
Hi,
I got a new system (LGA-1366) with an X58 chipset.
The SMB controller seems not to be supported? At least the smb driver
does no good:
no...@pci0:0:31:3: class=0x0c0500 card=0x3a301849 chip=0x3a308086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'SMB controlle
On Monday 21 December 2009 8:25:47 am Denis Barov wrote:
> Hello, list.
>
> I try to migrate one of my MFS-based system from 7.1 to 7.2 and get kernel
> trap 12 just after DDB initialisation
> (screenshot: http://dindin.ru/download/kernel_trap.png)
>
> FreeBSD svn revision: r11, architecture:
On Monday 21 December 2009 9:45:53 am Steven Hartland wrote:
> - Original Message -
> From: "John Baldwin"
> >> I've uploaded a two more traces for the oxt test failure / segv.
> >> http://code.google.com/p/phusion-passenger/issues/detail?id=441#c1
> >>
> >> >From looking at the test cas
- Original Message -
From: "John Baldwin"
I've uploaded a two more traces for the oxt test failure / segv.
http://code.google.com/p/phusion-passenger/issues/detail?id=441#c1
>From looking at the test case it testing the capture of failures and its
ability
to create a stack trace output
People who collect ISO images from more than just the FreeBSD Project
have been mentioning it would be nice if "FreeBSD" was part of the
filenames for a while now. I just committed a change to head that will
add "FreeBSD-" to the beginning of the filenames. So for example
9.0-RELEASE-am
Hello, list.
I try to migrate one of my MFS-based system from 7.1 to 7.2 and get kernel
trap 12 just after DDB initialisation
(screenshot: http://dindin.ru/download/kernel_trap.png)
FreeBSD svn revision: r11, architecture: amd64
there was a lot of changes in sys/amd64/amd64/pmap.c and can't
On Thursday 17 December 2009 12:27:17 pm Steven Hartland wrote:
> - Original Message -
> From: "John Baldwin"
> > For the hang it seems you have a thread waiting in a blocking read(), a
> > thread
> > waiting in a blocking accept(), and lots of threads creating condition
> > variables.
26 matches
Mail list logo
