mailbox# uname -a
FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 22
00:31:29 CEST 2006
[EMAIL PROTECTED]:/usr/obj-local/usr/src/sys/SMP amd64
I get tons of these:
em0: watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP
mailbox#
Hi,
On Wed, Sep 27, 2006 at 08:00:21AM +0200, Martin Nilsson wrote:
I get tons of these:
em0: watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP
mailbox# pciconf -lv
[EMAIL PROTECTED]:0:0: class=0x02 card=0x108c15d9 chip=0x108c8086
rev=0x03
On 9/27/06, Dmitry Pryanishnikov [EMAIL PROTECTED] wrote:
On Tue, 26 Sep 2006, John Baldwin wrote:
I've just found it and fixed it if you upgrade to the newest smbus.c.
Thanks, the problem has indeed been fixed.
I'm sorry to hijack this thread, but what's the recommended way to read out
Vivek Khera wrote:
On Sep 26, 2006, at 10:31 AM, [EMAIL PROTECTED] wrote:
I was able to mount nfs mounting point and to copie 16K of 7G data.
and, it goes to freezing. I can't kill neither cp process neither
mount unmount nfs (umount command goes freezing too). tcpdump tells
me that
On 9/27/06, Ulrich Spoerlein [EMAIL PROTECTED] wrote:
I'm sorry to hijack this thread, but what's the recommended way to read
out temperature values via SMB?
[EMAIL PROTECTED]:31:3: class=0x0c0500 card=0x618015d9 chip=0x24d38086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
John Baldwin wrote:
Hmm, are you willing to test a change that should fix that? If so, try
http://people.freebsd.org/~jhb/patches/btx_crx.patch You'll need to do
a 'make clean make make install' in /sys/boot after applying, and if
the make install suceeeds, do a 'bsdlabel -B ad0s1'
[EMAIL PROTECTED] wrote:
Vivek Khera wrote:
On Sep 26, 2006, at 10:31 AM, [EMAIL PROTECTED] wrote:
I was able to mount nfs mounting point and to copie 16K of 7G data.
and, it goes to freezing. I can't kill neither cp process neither
mount unmount nfs (umount command goes freezing too).
Oliver Brandmueller wrote:
Hi,
On Wed, Sep 27, 2006 at 08:00:21AM +0200, Martin Nilsson wrote:
I get tons of these:
em0: watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP
mailbox# pciconf -lv
[EMAIL PROTECTED]:0:0: class=0x02 card=0x108c15d9
Hello!
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt handler not getting run, or the taskqueue not getting run.
I helped Pyun with some debugging by providing ssh access to
a machine showing the
Hello,
Has anyone else noticed this? Here is how to repeat it:
1. USB Keyboard
2. Sound card (CMedia 8738 in my case)
3. Recent -STABLE
uname -v
FreeBSD 6.2-PRERELEASE #10: Mon Sep 18 15:46:33 BST 2006
Now, play some music (I'm using XMMS) and press on any keyboard
key which toggles an LED
On 9/27/06, Martin Nilsson [EMAIL PROTECTED] wrote:
mailbox# uname -a
FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 22
00:31:29 CEST 2006
[EMAIL PROTECTED]:/usr/obj-local/usr/src/sys/SMP amd64
I get tons of these:
em0: watchdog timeout -- resetting
em0: link state changed
Hello!
On -stable occasionally other people complained about very similar
looking problems with bge and other drivers. My guess is, though
I'm not a kernel developer, just an experienced admin, that
em stands out as problematic just by coincidence. Certain onboard
network components tend to
I have seen the watchdog and reset problem on a -STABLE laptop, both em
and iwi. It only occur when I try to connect using Mulberry e-mail
client so I thought it could be a problem with the linuxilator.
The load on the box is normally low but both driver have shared
interrupts, either with
On Wed, 27 Sep 2006 13:24:15 +0200 glz [EMAIL PROTECTED]
wrote about Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2:
G I have seen the watchdog and reset problem on a -STABLE laptop, both em
G and iwi. It only occur when I try to connect using Mulberry e-mail
G client so I thought it could
Hi,
Is this driver known to be 100% working? I'm running stable 6.2 p6 right now
and have this device driver installed (device sound and device snd_emu10k1
compiled into the kernel) for use with a Creative Live! card. Audio outputs
work correctly, and the various players will produce audio
For the recording software I've used Krec, ffmpeg, darkice
and streamTranscoder (the latter two feeding an icecast
server). 'mixer' has its recording device (=rec) set to line
in, and I'm feeding audio to line in (analog) and spdif in
(digital). There's no problem monitoring the 'line
Hi,
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some watchdog timeout in the log with a bge card, but maybe it's
not the same problem... :
/var/log/messages:Sep 23 02:47:06 anubis kernel: bge1: watchdog timeout --
resetting
/var/log/messages:Sep 23 02:47:06
Me Too(tm).
FreeBSD jacinta.home.cacheboy.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0:
Mon Sep 18 07:59:50 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
i386
Lots of this in dmesg:
em0: watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP
Hi!
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some watchdog timeout in the log with a bge card, but maybe it's
not the same problem... :
As far as I know the watchdog timeouts are _supposed_
On Wed, 27 Sep 2006 04:55:04 -0700
Bill Blue [EMAIL PROTECTED] wrote:
Is this driver known to be 100% working?
For me, it works OK most of the time. Longer audio files (ogg/mp3) usually
play without issues, and under rarely and not-understood circumstances some
sort of slight audio distortion
s/is on the bus/is alone on the irq/.
(And it shows up when I'm running polygraph and apachebench tests.)
On 9/27/06, Adrian Chadd [EMAIL PROTECTED] wrote:
Me Too(tm).
FreeBSD jacinta.home.cacheboy.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE#0: Mon
Sep 18 07:59:50 UTC 2006
[EMAIL
On Wednesday 27 September 2006 11:55, Bill Blue wrote:
Hi,
Is this driver known to be 100% working? I'm running stable 6.2 p6
right now and have this device driver installed (device sound and
device snd_emu10k1 compiled into the kernel) for use with a
Creative Live! card. Audio outputs
On Wed, Sep 27, 2006 at 03:25:55PM +0200, Patrick M. Hausen wrote:
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some watchdog timeout in the log with a bge card, but maybe it's
not the same
On Wed, Sep 27, 2006 at 09:06:09PM +0800, Adrian Chadd wrote:
Me Too(tm).
Me three -- and the interesting part (in my case) is that em0
shares an IRQ with the ATA controller.
http://www.freebsd.org/cgi/query-pr.cgi?pr=103435
Because people are reporting this on more than just the em driver
At 09:25 AM 9/27/2006, Patrick M. Hausen wrote:
Hi!
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some watchdog timeout in the log with a bge card, but maybe it's
not the same problem... :
As
Dear colleagues,
Linux emulation on -STABLE from September, 25 works somewhat
strange.
Shortly: it dumps core.
Explain: I want to bootstrap native Java Development Kit v1.4
using Linux JDK. Immediately
after invoking 'java' executable with full path kernel diagnoses
Segfault
originally posted to [EMAIL PROTECTED]:
Hi,
While trying to figure out why boot/pxeboot failes on some
kernels/hosts, I think i've come up with one solid nogo,
if the kernel is gzipped it always fails.
Can someone confirm this? or am i suffering from some
local problem?
Hello, I would like to convert RSSI to dBm (in fact I would love if
ifconfig cound display SNR in dBM), so I would like to know if this
formula is any right:
/* Calculate the RSSI Value */
V_RSSI = 3.0 * (RSSI_VAL/1024);
RSSI_dBM = (int8_t) ((-50.0 * V_RSSI) - 45.5);
And if there are any other
Hi!
On Wed, Sep 27, 2006 at 06:52:51AM -0700, Jeremy Chadwick wrote:
On Wed, Sep 27, 2006 at 03:25:55PM +0200, Patrick M. Hausen wrote:
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some
Hello, I would like to convert RSSI to dBm (in fact I would love if
ifconfig cound display SNR in dBM), so I would like to know if this
formula is any right:
Take a look here:
http://www.wildpackets.com/elements/whitepapers/Converting_Signal_Strength.pdf
Especially at the top of page 5. RSSI
On Sep 26, 2006, at 8:46 PM, Michael Vince wrote:
Yeah for some reason I couldn't do that, I can't even remember all
the reasons now but the main reason is because I have a USB
keyboard, for some reason I can use the USB keyboard in the BIOS
but as soon as the boot loader starts with the
Is this paper's information accurate regarding atheros?
I have no idea - I think you would be best off calibrating it yourself
with a dBm metre if you can. The antenna will have an effect as well, as
will cabling between it and the receiver chip - all the usual things to
do with working with
Hi,
Yesterday a machine of mine crashed because of a bad power
supply (not FreeBSD's fault); its running 6.2-PRERELEASE
as of 2006-09-20. I've disabled background fsck in rc.conf.
So, when rebooting I expected it to report all filesystems
to be unclean and run fsck on them.
Instead, three
How bad. But no big deal since I use mainly atheros and senao (prism) cards.
Is this paper's information accurate regarding atheros?
Say, RSSI = 23 is -72dbm?
On 9/27/06, Pete French [EMAIL PROTECTED] wrote:
Hello, I would like to convert RSSI to dBm (in fact I would love if
ifconfig cound
Hi.
On Wed, Sep 27, 2006 at 04:19:55PM +0200, Patrick M. Hausen wrote:
You'll still see impact -- that is, no packets flowing. The
reason things are recoverable is solely because of the retry
functionality for layer 2 packets...
You are, of course, right. What I meant is: these
Yes, this is the point. I dont always have a spectrum analiser to
measure my dBm signal nor similar hardware, so I would like to have
this information for each associated host in my freebsd access point,
even if it is not fully accurate, since no software that does this, in
fact is.
I need
Hi Scott,
On Wed, Sep 27, 2006 at 03:16:57AM -0600, Scott Long wrote:
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt handler not getting run, or the taskqueue not getting run.
Since you've stated
On Wed, Sep 27, 2006 at 09:56:22AM -0400, Mike Tancsa wrote:
If it up / downs the interface, it can be painful depending on your
setup. In one of the colos I dont have control over, the switch port
will block for 15 seconds for Spanning Tree when the interface
transitions like that. Even
On Wed, Sep 27, 2006 at 05:28:24PM +0200, Oliver Brandmueller wrote:
Hi Scott,
On Wed, Sep 27, 2006 at 03:16:57AM -0600, Scott Long wrote:
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt
On Wed, Sep 27, 2006 at 05:28:24PM +0200, Oliver Brandmueller wrote:
Disk activity does not trigger the problem, I hammered the disk with
around 85 MB/s (dd) for about half an hour without seeing any effect. A
CPU bound thing like a buildworld triggered the problem.
The SMBus Interface is
Hi,
On Wed, Sep 27, 2006 at 10:50:55AM -0500, Brooks Davis wrote:
Disk activity does not trigger the problem, I hammered the disk with
around 85 MB/s (dd) for about half an hour without seeing any effect. A
CPU bound thing like a buildworld triggered the problem.
I'm not sure that's a
Hi,
On Wed, Sep 27, 2006 at 08:55:53AM -0700, Jeremy Chadwick wrote:
The SMBus Interface is not used at all (it's not even really usable).
Anyway, as soon as I unload the ichsmb module I cannot triger the
problem anymore. If I load it again, the problem cann again be triggered
by a
Hi!
On Wed, Sep 27, 2006 at 05:59:04PM +0200, Oliver Brandmueller wrote:
I don't think it has to especially with ichsmb here, but only with the
fact, that ichsmb is for me exactly the thing that shares the interrupt
with the em interface that shows the problems.
I can confirm that making
Oliver Brandmueller wrote:
Hi,
On Wed, Sep 27, 2006 at 08:55:53AM -0700, Jeremy Chadwick wrote:
The SMBus Interface is not used at all (it's not even really usable).
Anyway, as soon as I unload the ichsmb module I cannot triger the
problem anymore. If I load it again, the problem cann again
Well, HTH - I don't have *any* problems with this configuration:
FreeBSD 6.2-PRERELEASE #6: Wed Sep 20 18:52:56 CEST 2006 [EMAIL
PROTECTED]:/usr/obj/usr/src/sys/MAILSMP
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU)
Origin = GenuineIntel Id = 0xf48 Stepping = 8
On Wed, Sep 27, 2006 at 06:32:59PM +0200, Patrick M. Hausen wrote:
On Wed, Sep 27, 2006 at 05:59:04PM +0200, Oliver Brandmueller wrote:
I don't think it has to especially with ichsmb here, but only with the
fact, that ichsmb is for me exactly the thing that shares the interrupt
with the
On Sep 27, 2006, at 11:50 AM, Jeremy Chadwick wrote:
On Wed, Sep 27, 2006 at 09:56:22AM -0400, Mike Tancsa wrote:
If it up / downs the interface, it can be painful depending on your
setup. In one of the colos I dont have control over, the switch port
will block for 15 seconds for Spanning
Hi, Scott!
On Wed, Sep 27, 2006 at 10:32:49AM -0600, Scott Long wrote:
1. Revert the em driver to its 6.1 form, ask people to test if the
problem persists. If it doesn't, leave it at that for now.
For me the problem manifested itself some time between 6.0
and 6.1. I did the testing with Pyun
On Wed, Sep 27, 2006 at 11:11:33AM +0200, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Vivek Khera wrote:
On Sep 26, 2006, at 10:31 AM, [EMAIL PROTECTED] wrote:
I was able to mount nfs mounting point and to copie 16K of 7G data.
and, it goes to freezing. I can't kill neither cp
As an optional data point you might wish to consider the Intel
driver I am about to release, it has everything that 6.2 does
EXCEPT the interrupt changes. I kept those out because I
didn't want to break backward compatibility. If someone that
has repro'd this problem wants to check this speak up
On Wed, Sep 27, 2006 at 12:44:04PM -0400, Javier Henderson wrote:
You could enable port fast and still have spanning tree in place.
What many reasons do you and others have to shun STP?
Rather than ramble off all the things I've experienced with STP,
most of them are covered in this caveat
At 12:32 PM 9/27/2006, Scott Long wrote:
My theory here is that something in the kernel, likely VM/VFS, is
holding the Giant lock for an inordinate amount of time. During this
time, an interrupt fires on the shared em/ichsmb interrupt. The em
Hi Scott,
Do you think this issue is
On Wed, Sep 27, 2006 at 03:25:55PM +0200, Patrick M. Hausen wrote:
Hi!
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some watchdog timeout in the log with a bge card, but maybe it's
not the
On Thu, Sep 28, 2006 at 06:32:16AM +1200, Jonathan Chen wrote:
On Wed, Sep 27, 2006 at 03:25:55PM +0200, Patrick M. Hausen wrote:
Hi!
On Wed, Sep 27, 2006 at 02:42:30PM +0200, Philippe Pegon wrote:
it's just a me too. On our ftp server (ftp8.fr.freebsd.org), sometimes
we see some
On Wed, 2006-Sep-27 10:32:49 -0600, Scott Long wrote:
My theory here is that something in the kernel, likely VM/VFS, is
holding the Giant lock for an inordinate amount of time.
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long periods (I've seen
Peter Jeremy wrote:
On Wed, 2006-Sep-27 10:32:49 -0600, Scott Long wrote:
My theory here is that something in the kernel, likely VM/VFS, is
holding the Giant lock for an inordinate amount of time.
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long
Now I use map 10.0.0.0/8 - 212.118.z.w/32 and it works fine.
ipnat -s now shows inuse 55633, maximus that i saw was about 8
How to resolve this problem?
___
freebsd-stable@freebsd.org mailing list
On Sep 27, 2006, at 12:51 PM, Kris Kennaway wrote:
See a previous reply to Vivek where I explained what is needed to help
debug this kind of problem.
and my luck has it such that i've not had a lockup since i added that
extra debugging code into the kernel :-) or :-( depending on your
On Wed, Sep 27, 2006 at 04:32:11PM -0400, Vivek Khera wrote:
On Sep 27, 2006, at 12:51 PM, Kris Kennaway wrote:
See a previous reply to Vivek where I explained what is needed to help
debug this kind of problem.
and my luck has it such that i've not had a lockup since i added that
Hello,
I am having a very hard time getting an Intel se7230NH1-E motherboard with
6gb of memory to work. I keep getting two messages about Too many holes
in the physical address space, giving up.
I'm not sure what the BIOS is (it seems to be OEMed to Intel), but with
the menu structure I'd have
I am sending this again since it has been 4 days with no response.
I consider this a showstopper since I could boot from CD but sysinstall
could not see the DVD drives, thus no CD install. I had to mount the CD
in another machine and do a NFS install.
--
Frank
-- Forwarded message
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long periods (I've seen 8msec). See
http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/012346.html
I'm not sure if this is still a problem (but I am still having some
problems which may be
On Wed, Sep 27, 2006 at 01:58:59PM -0700, [EMAIL PROTECTED] wrote:
I am having a very hard time getting an Intel se7230NH1-E motherboard with
6gb of memory to work. I keep getting two messages about Too many holes
in the physical address space, giving up.
I'm not sure what the BIOS is (it
In response to Jeremy Chadwick [EMAIL PROTECTED]:
On Wed, Sep 27, 2006 at 01:58:59PM -0700, [EMAIL PROTECTED] wrote:
I am having a very hard time getting an Intel se7230NH1-E motherboard with
6gb of memory to work. I keep getting two messages about Too many holes
in the physical address
Frank wrote:
I am sending this again since it has been 4 days with no response.
I consider this a showstopper since I could boot from CD but
sysinstall could not see the DVD drives, thus no CD install. I had to
mount the CD in another machine and do a NFS install.
SATA optical drives are
On 37378-12-23 20:59, Patrick M. Hausen wrote:
Hello!
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt handler not getting run, or the taskqueue not getting run.
I helped Pyun with some
Based on what I understand of Intel x86 architecture, to address more
than 4GB of memory space, you have to use Intel's PAE feature. I
don't think the FreeBSD kernels are built with PAE enabled. This
might explain why the kernel states there's too many memory holes.
I'd recommend either 1)
I have no idea if the problem is related to PAE, but have you tried
booting an amd64 kernel on the system?
This is an Intel Pentium 4 (D) system. Would the AMD64 kernel even work?
- Greg
___
freebsd-stable@freebsd.org mailing list
David G Lawrence wrote:
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long periods (I've seen 8msec). See
http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/012346.html
I'm not sure if this is still a problem (but I am still having some
Eduardo Meyer wrote:
Hello, I would like to convert RSSI to dBm (in fact I would love if
ifconfig cound display SNR in dBM), so I would like to know if this
formula is any right:
/* Calculate the RSSI Value */
V_RSSI = 3.0 * (RSSI_VAL/1024);
RSSI_dBM = (int8_t) ((-50.0 * V_RSSI) - 45.5);
Volker wrote:
On 37378-12-23 20:59, Patrick M. Hausen wrote:
Hello!
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt handler not getting run, or the taskqueue not getting run.
I helped Pyun with
Danny Braniss wrote:
originally posted to [EMAIL PROTECTED]:
Hi,
While trying to figure out why boot/pxeboot failes on some
kernels/hosts, I think i've come up with one solid nogo,
if the kernel is gzipped it always fails.
Can someone confirm this? or am i suffering from some
On Wed, 27 Sep 2006, Mike Jakubik wrote:
Frank wrote:
I am sending this again since it has been 4 days with no response.
I consider this a showstopper since I could boot from CD but sysinstall
could not see the DVD drives, thus no CD install. I had to mount the CD in
another machine and do
Absolutely, its an architecture not a brand name, should call it x86_64
as often done in Linux. If you run only a 32bit kernel on that system of
yours you're cheating yourself out of performance anyway.
slurp down an iso and boot that before you go pulling dimms and such :)
Jack
On 9/27/06,
On Tue, 26 Sep 2006, Mark Andrews wrote:
get*by*_r() are deprecated on most platforms and there use
is highly non-portable, lots of different API's.
My understanding was that FreeBSD has copied the Linux version of the
API.
Why are we adding compatability for
On Wed, Sep 27, 2006 at 02:21:16PM -0700, [EMAIL PROTECTED] wrote:
I have no idea if the problem is related to PAE, but have you tried
booting an amd64 kernel on the system?
This is an Intel Pentium 4 (D) system. Would the AMD64 kernel even work?
Maybe. The later Pentium 4 processors do
On 2006-09-27 23:29, Scott Long wrote:
Volker wrote:
[...]
Strange... I've seen exactly that on a (recent) RELENG_6 box but
using a dirty old USB 1.1 NIC (aue). I've seen DOWN and UP messages
(mostly while rebuilding kernel + world + ports) on the console all
the time (but did not care
Absolutely, its an architecture not a brand name, should call it x86_64
as often done in Linux. If you run only a 32bit kernel on that system of
yours you're cheating yourself out of performance anyway.
slurp down an iso and boot that before you go pulling dimms and such :)
Jack
Okay, I'm
On Wed, Sep 27, 2006 at 05:09:16PM +0300, Danny Braniss wrote:
originally posted to [EMAIL PROTECTED]:
Hi,
While trying to figure out why boot/pxeboot failes on some
kernels/hosts, I think i've come up with one solid nogo,
if the kernel is gzipped it always fails.
Can someone
[EMAIL PROTECTED] wrote:
I have no idea if the problem is related to PAE, but have you tried
booting an amd64 kernel on the system?
This is an Intel Pentium 4 (D) system. Would the AMD64 kernel even work?
I'm not an Intel sales rep, but I believe all the P4 systems have
64 bit support.
A simple grep command, 'grep -vf patternfile inputfile' works on Linux,
but the same command doesn't work on FreeBSD-6.1.
To make it work I found I had to use -F to force the interpretation of
fixed-strings. I don't know why it made a difference from Linux, and
nothing in the man page
On 9/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Absolutely, its an architecture not a brand name, should call it x86_64
as often done in Linux. If you run only a 32bit kernel on that system of
yours you're cheating yourself out of performance anyway.
slurp down an iso and boot that
On 9/27/06, Bill Moran [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I have no idea if the problem is related to PAE, but have you tried
booting an amd64 kernel on the system?
This is an Intel Pentium 4 (D) system. Would the AMD64 kernel even work?
I'm not an Intel sales rep, but I
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: As soon as I can locate the O/U/EHCI register docs, I'll crank out a
: patch for everyone to try. If that works then I'll give the same
: treatment to ichsmb.
You might look in the //depot/user/imp/newcard/...
On Tue, 26 Sep 2006, Mark Andrews wrote:
get*by*_r() are deprecated on most platforms and there use
is highly non-portable, lots of different API's.
My understanding was that FreeBSD has copied the Linux version of the
API.
That still doesn't make it portable.
Scott Long wrote:
Well, I kinda danced around the issue before, but I'll say it now. I,
as well as a few others, have seen instances of Giant being held by
the syncer for 5 or more seconds at a time. I can't explain why, and
I've never been able to catch it in the act in a meaningful way. But
On Wed, Sep 27, 2006, Stephen Allen wrote:
A simple grep command, 'grep -vf patternfile inputfile' works on Linux,
but the same command doesn't work on FreeBSD-6.1.
To make it work I found I had to use -F to force the interpretation of
fixed-strings. I don't know why it made a difference from
I have nForce3 motherboard and Athlon 64
Here is /var/log/messages
Sep 28 03:41:03 ddf syslogd: kernel boot file is /boot/kernel/kernel
Sep 28 03:41:03 ddf kernel: Copyright (c) 1992-2006 The FreeBSD Project.
Sep 28 03:41:03 ddf kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
1989, 1991,
[EMAIL PROTECTED] /]# vmstat -i
interrupt total rate
irq1: atkbd0 381 0
irq14: ata0 135495 28
irq15: ata1 166738 34
irq16: atapci3 36963 7
On Tue, 26 Sep 2006 10:38:43 -0700, Kevin Oberman [EMAIL PROTECTED]
wrote:
[...]
About the only thing you should put in make.conf is the name of your
kernel config file:
KERNCONF=MY_SYS would cause the config file /sys/i386/conf/MY_SYS to be
used, assuming it's an i386 system.
OK. Is
--3uo+9/B/ebqu+fSQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 27, 2006 at 05:09:16PM +0300, Danny Braniss wrote:
originally posted to [EMAIL PROTECTED]:
=20
Hi,
While trying to figure out why
Danny Braniss wrote:
originally posted to [EMAIL PROTECTED]:
Hi,
While trying to figure out why boot/pxeboot failes on some
kernels/hosts, I think i've come up with one solid nogo,
if the kernel is gzipped it always fails.
Can someone confirm this? or am i suffering from
92 matches
Mail list logo
