On Fri, 18 Jan 2008, Peter Jeremy wrote:
> On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
> >On Fri, 18 Jan 2008, John Baldwin wrote:
> >> amd64 uses link_elf_obj.c, all the other archs use link_elf.c,
> >> hence the duplication.
>
> Then why does amd64 need link_elf.c at all?
I
On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
>On Fri, 18 Jan 2008, John Baldwin wrote:
>> amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence
>> the duplication.
Then why does amd64 need link_elf.c at all?
>I guess one option would be to put #ifdef amd64 aroun
On Thu, Jan 17, 2008 at 10:24:55PM +0100, Claus Guttesen wrote:
> da1 at ciss1 bus 0 target 0 lun 0
> dSaM1P:: A ME expa> Fixed Direct Access SCSI-5 device
> da1: 135.168MB/s transfers
First item in http://jdc.parodius.com/freebsd/common_issues.txt has the
threads you're interested in.
Someone r
> MADT is the ACPI table that enumerates APICs. Do you have the offset of
> madt_probe()?
I am sujre I can get it for you - do I need to do anything special
in DDB, or is it just the numbers in the bt that you are after ?
I can make this panic very easily and do whatever is necessary to
get info
On 12/23/-58 20:59, Nate Lawson wrote:
> Nate Lawson wrote:
>> Volker wrote:
>>> On 12/23/-58 20:59, Nate Lawson wrote:
I've committed the below patch and want to MFC it to 7.0. To do this, I
need people to test this quickly. It probably has no effect in 6.x and
probably doesn't ap
On Thu, Jan 17, 2008 at 04:17:33PM -0600, Mark Linimon wrote:
> On Thu, Jan 17, 2008 at 01:59:01PM -0800, Josef Grosch wrote:
> > I have a mirror at work (Juniper Networks) and we have had all the
> > bits since Tuesday.
>
> You can't have; the final sparc64-6 packages were just finished
> yesterd
Quoting Josef Grosch, who wrote on Thu, Jan 17, 2008 at 01:59:01PM -0800 ..
> On Tue, Jan 15, 2008 at 02:25:43PM -0600, Mark Linimon wrote:
> > On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote:
> > > So may I guess that we have a release ?
> >
> > This question happens every time
On Tue, Jan 15, 2008 at 02:25:43PM -0600, Mark Linimon wrote:
> On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote:
> > So may I guess that we have a release ?
>
> This question happens every time we get near a release.
>
> There will be a release when, and only when, a signed ema
On Thu, Jan 17, 2008 at 01:59:01PM -0800, Josef Grosch wrote:
> I have a mirror at work (Juniper Networks) and we have had all the
> bits since Tuesday.
You can't have; the final sparc64-6 packages were just finished
yesterday, at the last second.
mcl
_
On Thu, Jan 17, 2008 at 10:24:55PM +0100, Claus Guttesen wrote:
> Hi.
>
> I've upgraded to FreeBSD stable as of Jan. 16'th 2008, doen a make
> world/kernel. The server is a DL360 G5 with a builtin p400i controller
> and a p800 controller as well. Upon boot I get a garbled dmesg from
> the p800 con
On Fri, 18 Jan 2008, John Baldwin wrote:
> > Can anyone explain what the underlying problem is? (I am guessing
> > some ordering issue where normally elf64_obj is called first so the
> > other is normally never called..)
>
> amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence
> the
Hi.
I've upgraded to FreeBSD stable as of Jan. 16'th 2008, doen a make
world/kernel. The server is a DL360 G5 with a builtin p400i controller
and a p800 controller as well. Upon boot I get a garbled dmesg from
the p800 controller:
da1 at ciss1 bus 0 target 0 lun 0
dSaM1P:: A Fixed Direct Access
On Thursday 17 January 2008 07:38:32 am Pete French wrote:
> following up my own email here, but I have compiled the kernel
> debugger into my kerenal, and much to my surprise it dooes actualy
> drop into the debugger when it panics.
>
> so, what can I do from there to help sort this out ? a quick
On Wednesday 16 January 2008 10:40:25 pm Daniel O'Connor wrote:
> Hi,
> I have built my own release of 6.3 (slightly older than 6.3 as tagged)
> and I am seeing an odd cosmetic problem. Whenever I kldload a module
> (stuff loaded by the loader doesn't do it) I get this in dmesg..
> kldload: Unsup
On Thursday 17 January 2008 06:17:52 am Norberto Meijome wrote:
> On Wed, 16 Jan 2008 09:31:55 -0500
> John Baldwin <[EMAIL PROTECTED]> wrote:
>
> > Please get a crash dump with matching kernel.debug and
acpi_video.ko.debug.
>
> where do I read about creating a debug version of acpi_video.ko (or
On Thursday 17 January 2008 06:05:17 am Parv wrote:
> in message <[EMAIL PROTECTED]>,
> wrote Vivek Khera thusly...
> >
> >
> > On Jan 10, 2008, at 11:09 AM, John Baldwin wrote:
> >
> >>> *: This is the default behavior for 7.0, I have not encountered
> >>> the problem mentioned above on any 1950
Kris Kennaway wrote:
> KTR_SCHED
Kris, BTW, I am curious if the traces I posted were informative. Let me
know if I did not create them correctly. The xterm test seems to vary
in usefulness depending on video card (faster cards catch up too
quickly), but the freezing still happens quite often usi
Vlad GALU writes:
| On 1/17/08, Ferdinand Goldmann <[EMAIL PROTECTED]> wrote:
| > Hi!
| >
| > I am in the process of buying new Dell hardware, mainly the 2950 III.
| > According to various postings I found, the PERC6/i Controller _should_ work
| > with FreeBSD 6.3. Does anyone successfully use a 29
Wayne Sierke wrote:
On Mon, 2008-01-14 at 21:06 +0100, Kris Kennaway wrote:
Same deal as before then. It cannot be the same problem as in the
previous 6.x trace (unless you are using a non-mpsafe filesystem, i.e.
not UFS).
Kris
In fact I have some MSDOSFS auto-mounting from /etc/fstab, but
Hello!
I found some strange behaviour of NIS/nscd when NIS in compat mode. In
/etc/nsswitch.conf I have:
netgroup: cache compat
passwd: cache compat
group:cache compat
#group_compat: cache nis
#passwd_compat:cache nis
in /etc/nscd.conf:
#nscd.conf
threads 16
On Mon, 2008-01-14 at 21:06 +0100, Kris Kennaway wrote:
> Same deal as before then. It cannot be the same problem as in the
> previous 6.x trace (unless you are using a non-mpsafe filesystem, i.e.
> not UFS).
>
> Kris
In fact I have some MSDOSFS auto-mounting from /etc/fstab, but normally
not
Vivek Khera wrote:
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote:
Where can one go to read up on what MSI is and how it helps us?
Is enabling it just setting a sysctl? Does that have to be done in
loader.conf or can it happen later?
loader.conf (though it is now default on in RELENG_6).
Vivek Khera wrote:
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote:
Where can one go to read up on what MSI is and how it helps us?
Is enabling it just setting a sysctl? Does that have to be done in
loader.conf or can it happen later?
loader.conf (though it is now default on in RELENG_6).
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote:
Where can one go to read up on what MSI is and how it helps us?
Is enabling it just setting a sysctl? Does that have to be done in
loader.conf or can it happen later?
loader.conf (though it is now default on in RELENG_6).
hw.pci.msi_enable=1
It seems that cd driver lacks couple of useful features as compared to acd:
1. device nodes for individual tracks: this might not be so useful for
tracks on audio CDs, but it is especially useful for mixed audio/data
CDs and multi-track data CDs;
2. automatic detection of track type (audio/data) a
Ferdinand Goldmann wrote:
Hi!
I am in the process of buying new Dell hardware, mainly the 2950 III.
According to various postings I found, the PERC6/i Controller _should_
work with FreeBSD 6.3. Does anyone successfully use a 2950 III with
PERC6/i controller and can confirm this?
Sorry if the
On Thu, Jan 17, 2008 at 01:59:36PM +0100, Ferdinand Goldmann wrote:
> I am in the process of buying new Dell hardware, mainly the 2950 III.
> According to various postings I found, the PERC6/i Controller _should_ work
> with FreeBSD 6.3. Does anyone successfully use a 2950 III with PERC6/i
> cont
On 1/17/08, Ferdinand Goldmann <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I am in the process of buying new Dell hardware, mainly the 2950 III.
> According to various postings I found, the PERC6/i Controller _should_ work
> with FreeBSD 6.3. Does anyone successfully use a 2950 III with PERC6/i
> controll
Hi!
I am in the process of buying new Dell hardware, mainly the 2950 III.
According to various postings I found, the PERC6/i Controller _should_ work
with FreeBSD 6.3. Does anyone successfully use a 2950 III with PERC6/i
controller and can confirm this?
Sorry if the question sounds stupid, bu
following up my own email here, but I have compiled the kernel
debugger into my kerenal, and much to my surprise it dooes actualy
drop into the debugger when it panics.
so, what can I do from there to help sort this out ? a quick backtrace
shows the following call sequence:
madt_probe
in message <[EMAIL PROTECTED]>,
wrote Vivek Khera thusly...
>
>
> On Jan 10, 2008, at 11:09 AM, John Baldwin wrote:
>
>>> *: This is the default behavior for 7.0, I have not encountered
>>> the problem mentioned above on any 1950/2950 boxes so far I have
>>> tested.
>>
>> I will enable MSI by de
On Wed, 16 Jan 2008 09:31:55 -0500
John Baldwin <[EMAIL PROTECTED]> wrote:
> Please get a crash dump with matching kernel.debug and acpi_video.ko.debug.
where do I read about creating a debug version of acpi_video.ko (or other .kos
for that matter)?
thx!
B
_
{Beto|Norbe
On Jan 17, 2008 1:31 AM, Johan Ström <[EMAIL PROTECTED]> wrote:
> > Export the disk on the backup server with ggated. Bind it on the
> > client
> > with ggatec. Slap a GELI or GBDE encryption on top of it and then
> > put a
> > ZFS on top of it.
> >
> > You can mount/import this "remote" ZFS at wil
33 matches
Mail list logo
