Jeremy Chadwick wrote:
As far as SCHED_ULE goes, if you have issues with it, use SCHED_4BSD.
Now, about watchdog timeouts in general -- there's a pending issue
which is still under investigation. Please see this thread:
That was the em thread to which I referred in my original post. That
On Monday 02 October 2006 21:16, Roland Smith wrote:
Well, these are the same guys that bought a license from SCO for SCO's
alleged IP in Linux (and alledgedly in *BSD, before the settlement in
USL vs BSDi was made public). Apparently after a large
bribe^H^H^H^H^Hdiscount from
Scott Long skrev:
In any case, SCHED_ULE is still considered to be highly experimental.
Hopefully it will get some more attention in the near future to
bring it closer to production quality.
Can we have a commit (at least to STABLE) that adds a big fat message
during boot that goes
On Wed, Oct 04, 2006 at 08:59:09AM +0200, Martin Nilsson wrote:
Can we have a commit (at least to STABLE) that adds a big fat message
during boot that goes something like:
### You are using SCHED_ULE scheduler ###
### SCHED_ULE is still considered to be highly experimental
Hello,
i have a problem with some strange spam emails, which lock up my
email reception.
The problem is the following : I am using fetchmail to download my
email (from a pop3 server), and fetchmail passes the email to my
local sendmail daemon who gives it to my local imap server (cyrus).
Is there a way to tweak the timeout behavior of sendmail, or maybe
even no dns resolve option for sendmail, or even better some way to
tell fetchmail to use the idle command to keep the connectio to the
pop server open ?
sendmail.mc supports FEATURE(`accept_unresolvable_domains'),
Hi all,
I have few servers that have Intel and Broadcom (embge) giga NICs
running FreeBSD RELENG_6 (from 6.1-R to 6.2-PRERELEASE).
And (luckily) there are no such problems like watchdog timeouts.
So may be something is different in our configurations, do you want my
kernel confs
or something
Karsten Fuhrmann wrote:
The problem is the following : I am using fetchmail to download my
email (from a pop3 server), and fetchmail passes the email to my local
sendmail daemon who gives it to my local imap server (cyrus). This
works fine. But sometimes i got a spam email, which has an
Jeremy Chadwick skrev:
An alternate idea: remove SCHED_ULE from the GENERIC kernel config
and instead make a ULE config which can be included (similar to
SMP and PAE).
The problem with ULE is that it works so well that you enable it and
forget it. Then a couple of months later you find
Hi,
On this subject, does somebody know why there is no pending issues listed
at http://www.freebsd.org/releases/6.2R/todo.html ?
--
Philippe Pegon
Jeremy Chadwick wrote:
On Wed, Oct 04, 2006 at 02:34:16PM +1000, John Marshall wrote:
$ dmesg | grep bge
bge0: Broadcom BCM5705K Gigabit
Craig Boston ([EMAIL PROTECTED]) on 29/09/2006 at 20:19 wrote:
One thing this patch definitely did do though, is break the nvidia
driver pretty badly. Couldn't keep the X server running for more than a
minute before it froze solid. Lots of Xid: blah blah blah messages.
Yes I remembered to
FreeBSD Security Officer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
Hi,
On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their
End of Life and will no longer be supported by the FreeBSD Security
Team. Users of either of those FreeBSD releases are
Hello,
Is this supposed to work under FreeBSD 6.X amd64 at all ?
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: PLEXTOR DVDR PX-716AL 1.01 Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
cd0: cd present [2295104 x 2048 byte records]
umass0: Unsupported ATAPI command 0x46
(the last line
Daniel O'Connor wrote:
On Wednesday 04 October 2006 20:33, Stefan Lambrev wrote:
Is this supposed to work under FreeBSD 6.X amd64 at all ?
Did you actually try using it?
Of course :) and it does not work - can't mount, read, write and so on.
Checked under other os - it works so
On Wednesday 04 October 2006 20:33, Stefan Lambrev wrote:
Is this supposed to work under FreeBSD 6.X amd64 at all ?
Did you actually try using it?
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so
Hi,
In June 2006, I opened a PR (kern/98622) about a regression on CARP
with IPv6 addresses: CARP is not usable with IPv6. Since I tracked
down the culprit commit (see appropriate info in the PR), I can
affirm that this regression appeared before the 6.1-RELEASE.
Wouldn't it be better to fix
Stefan Lambrev wrote:
Daniel O'Connor wrote:
On Wednesday 04 October 2006 20:33, Stefan Lambrev wrote:
Is this supposed to work under FreeBSD 6.X amd64 at all ?
Did you actually try using it?
Of course :) and it does not work - can't mount, read, write and so on.
Checked under
On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote:
Details are posted at http://vivek.khera.org/scratch/crashlogs/
I have the crashdumps available to a kernel hacker upon request (i'd
rather not make them generally available to the public...)
It seems that you have snapshotted fs exported by
On Wed, Oct 04, 2006 at 09:56:54AM -0400, Vivek Khera wrote:
On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote:
Details are posted at http://vivek.khera.org/scratch/crashlogs/
I have the crashdumps available to a kernel hacker upon request (i'd
rather not make them generally available to
In response to Scott Long [EMAIL PROTECTED]:
Corrected patch is at:
http://people.freebsd.org/~scottl/usb_fastintr_RELENG_6.diff
I have a Dell 1950 here that's been dedicated to helping solve this
problem. I can reliably reproduce the watchdog timeout by doing
the following steps:
1) Mount
Running freebsd 6.1 Stable.
I am aware that there was issues with SiS SATA chipsets requiring a
patch. Has this issue been resolved with not being able to see SATA
drives (at all) in freebsd?
The bug is apparently with in how the SATA regs are addressed. I found a
few references to patches,
Is there a way to tweak the timeout behavior of sendmail, or maybe
even no dns resolve option for sendmail, or even better some way to
tell fetchmail to use the idle command to keep the connectio to the
pop server open ?
sendmail.mc supports
In response to Bill Moran [EMAIL PROTECTED]:
In my case, it's a bce driver that's doing it. I also have some em
cards in this machine that I can test if the information will be
helpful.
Note that I can _not_ reproduce the problem with an em interface (a
PCI NIC). As mentioned earlier, I can
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to work as advertised. (i.e. hitting the power
button cleanly shuts down the OS)
I'm posting this to stable@, but the same behaviour occurs with
On Wed, Oct 04, 2006 at 05:08:08PM +0300, Kostik Belousov wrote:
On Wed, Oct 04, 2006 at 09:56:54AM -0400, Vivek Khera wrote:
On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote:
Details are posted at http://vivek.khera.org/scratch/crashlogs/
I have the crashdumps available to a
On Wed, Oct 04, 2006 at 12:48:12PM +0200, Philippe Pegon wrote:
In June 2006, I opened a PR (kern/98622) about a regression on CARP
with IPv6 addresses: CARP is not usable with IPv6. Since I tracked
down the culprit commit (see appropriate info in the PR), I can
affirm that this regression
On Wed, Oct 04, 2006 at 10:40:25AM -0400, Bill Moran wrote:
In response to Scott Long [EMAIL PROTECTED]:
Corrected patch is at:
http://people.freebsd.org/~scottl/usb_fastintr_RELENG_6.diff
I have a Dell 1950 here that's been dedicated to helping solve this
problem. I can reliably
Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to work as advertised. (i.e. hitting the power
button cleanly shuts down the OS)
I'm posting this to stable@, but the same
In response to Guy Helmer [EMAIL PROTECTED]:
Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to work as advertised. (i.e. hitting the power
button cleanly shuts down
On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote:
The only thing I think was running at the time would be a large file
copy from a remote system to this one using rsync.
As I understand, you got the panic. Then, you shall post the panic
message.
If you have core file, then running kgdb on
At 12:27 PM 10/4/2006, Bill Moran wrote:
In response to Bill Moran [EMAIL PROTECTED]:
In my case, it's a bce driver that's doing it. I also have some em
cards in this machine that I can test if the information will be
helpful.
Note that I can _not_ reproduce the problem with an em
On Wed, Oct 04, 2006 at 01:06:37PM -0400, Vivek Khera wrote:
On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote:
The only thing I think was running at the time would be a large file
copy from a remote system to this one using rsync.
As I understand, you got the panic. Then, you shall
In response to Mike Tancsa [EMAIL PROTECTED]:
At 12:27 PM 10/4/2006, Bill Moran wrote:
In response to Bill Moran [EMAIL PROTECTED]:
In my case, it's a bce driver that's doing it. I also have some em
cards in this machine that I can test if the information will be
helpful.
Note
John Baldwin wrote:
Nothing to worry about. It means that there are more devices that couldn't
be
fit into the available space for the name. A + means there is one more
device on this IRQ and there wasn't enough room for its name. A * means
there are 2 or more devices on this IRQ and
On Oct 4, 2006, at 1:16 PM, Kostik Belousov wrote:
#9 0x80369166 in Xtimerint () at apic_vector.S:153
#10 0x801d1c05 in bge_intr (xsc=0x8698e010) at
bus.h:241
Did you have any problems with your network card ?
On Wed, Oct 04, 2006 at 12:36:22PM -0400, Kris Kennaway wrote:
When this kind of thing happens you just need to periodically make a
bit of noise to make sure it doesn't get forgotten. In particular you
should mention the problem to re@ so they can investigate and track
it.
Do I need to
On Oct 4, 2006, at 1:16 PM, Kostik Belousov wrote:
#10 0x801d1c05 in bge_intr (xsc=0x8698e010) at
bus.h:241
Did you have any problems with your network card ? This seems to be
quite popular plot in recent times.
Another
Bill Moran wrote:
In response to Guy Helmer [EMAIL PROTECTED]:
Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to work as advertised. (i.e. hitting the power
button
Hi,
On Wed, Oct 04, 2006 at 12:28:35PM -0400, Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
What exactly are the last few lines?
Other ACPIish stuff seems to work as advertised. (i.e. hitting the
On Wednesday 04 October 2006 12:42, Guy Helmer wrote:
Bill Moran wrote:
In response to Guy Helmer [EMAIL PROTECTED]:
Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits
there on the shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to
In response to Guy Helmer [EMAIL PROTECTED]:
Bill Moran wrote:
In response to Guy Helmer [EMAIL PROTECTED]:
Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff
On Wed, Oct 04, 2006 at 07:20:19PM +0200, Ivan Voras wrote:
John Baldwin wrote:
Nothing to worry about. It means that there are more devices that couldn't
be
fit into the available space for the name. A + means there is one more
device on this IRQ and there wasn't enough room for its
In response to Bruno Ducrot [EMAIL PROTECTED]:
Hi,
On Wed, Oct 04, 2006 at 12:28:35PM -0400, Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p does the same.
What exactly are the last few lines?
(manually
On Wed, 4 Oct 2006, Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on
the shutdown screen.
A shutdown -p does the same.
Other ACPIish stuff seems to work as advertised. (i.e. hitting the
power button cleanly shuts down the OS)
I'm posting this to stable@,
Hello all,
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can simply reconnect if
our ppp would support it.
Oct 4 20:39:51 coyote ppp[57670]: tun0:
In response to Kris Kennaway [EMAIL PROTECTED]:
This is quite a show-stopper for us, if there's any other testing/etc
I can do, _please_ let me know. I might even be able to get remote
console access to this machine approved for a developer.
Remote console access would be a help. I
On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
Hello all,
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can simply reconnect if
O. Hartmann wrote:
Stefan Lambrev wrote:
Daniel O'Connor wrote:
On Wednesday 04 October 2006 20:33, Stefan Lambrev wrote:
Is this supposed to work under FreeBSD 6.X amd64 at all ?
Did you actually try using it?
Of course :) and it does not work - can't mount, read, write and
cpghost wrote:
On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
Hello all,
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can
Ulrich Spoerlein wrote:
Hello all,
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can simply reconnect if
our ppp would support it.
As a victim of
Jeremy Chadwick wrote:
I was feeling proactive and took a look at the vmstat code, which is
an amazing piece of work (take my comment however you wish, because it
has multiple implications).
Yeah, I see it. It will become a member of a collection of examples for
the
On Wed, Oct 04, 2006 at 02:07:12PM -0400, Bill Moran wrote:
In response to Bruno Ducrot [EMAIL PROTECTED]:
Hi,
On Wed, Oct 04, 2006 at 12:28:35PM -0400, Bill Moran wrote:
A reboot causes the OS to halt, but the hardware just sits there on the
shutdown screen.
A shutdown -p
On Thu, Oct 05, 2006 at 01:36:37AM +0800, Eugene Grosbein wrote:
On Wed, Oct 04, 2006 at 12:36:22PM -0400, Kris Kennaway wrote:
When this kind of thing happens you just need to periodically make a
bit of noise to make sure it doesn't get forgotten. In particular you
should mention the
Ulrich Spoerlein wrote:
cpghost wrote:
On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
Hello all,
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every
On 10/3/06, Daniel Gerzo [EMAIL PROTECTED] wrote:
Hello Nik,
Tuesday, October 3, 2006, 4:31:11 PM, you wrote:
Alexandre Vieira wrote:
I was also told that http://www.serverpronto.com/ is freebsd friendly
and
extremely cheap.
Since this seems to have become a recommendation thread, I'm a
On Wed, Oct 04, 2006 at 01:06:37PM -0400, Vivek Khera wrote:
On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote:
The only thing I think was running at the time would be a large file
copy from a remote system to this one using rsync.
As I understand, you got the panic. Then, you shall
On Oct 4, 2006, at 3:41 PM, Kris Kennaway wrote:
from what i read in the output from kgdb, it seems that something
locked the kernel and we broke to debugger from the watchdog timeout
(I enable software watchdog).
Hmm, be careful with that - if you set the timeout too low (and note
that for
On Wed, Oct 04, 2006 at 03:53:54PM -0400, Vivek Khera wrote:
On Oct 4, 2006, at 3:41 PM, Kris Kennaway wrote:
from what i read in the output from kgdb, it seems that something
locked the kernel and we broke to debugger from the watchdog timeout
(I enable software watchdog).
Hmm, be
Randi Harper wrote:
On 10/3/06, Daniel Gerzo [EMAIL PROTECTED] wrote:
also layeredtech.com is pretty good.
Props to layeredtech.
In the 20 months for which layeredtech has been providing free hosting for
FreeBSD Update, one of the two Portsnap mirrors, and my personal website,
I haven't had
Guy Brand wrote:
Craig Boston ([EMAIL PROTECTED]) on 29/09/2006 at 20:19 wrote:
One thing this patch definitely did do though, is break the nvidia
driver pretty badly. Couldn't keep the X server running for more than a
minute before it froze solid. Lots of Xid: blah blah blah messages.
Yes
On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote:
Details are posted at http://vivek.khera.org/scratch/crashlogs/
I have the crashdumps available to a kernel hacker upon request (i'd
rather not make them generally available to the public...)
It seems that you have snapshotted fs exported by
On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected
cpghost wrote:
On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
Not that it helps you much, but I do see working pppoe redial behavior
with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl
line and it will autoreconnect as soon as it's plugged in again. In the
On Wed, Oct 04, 2006 at 11:39:09PM +0200, Ulrich Spoerlein wrote:
I maintain three FreeBSD boxes from 4.11 to 6.1-RELEASE and 6-STABLE.
They have been showing this for at least 1 or 2 years. So it is/was also
present in the 5.x line.
I usually work around this by having a cron job that
Hi,
What about with just the first change and not the second? Anyways, I'm
starting to see a trend here. Problem reports are clustering around UP
systems, not SMP systems. I don't know if that's just coincidence or not.
We've got also about twenty SMP Systems, seven of them now with 6.1
I also have been using em (on-board NIC) with SMP without any problems, I just
upgraded to check and all is still fine:
New kernel : FreeBSD 6.2-PRERELEASE #7: Mon Oct 2 15:15:47 PDT 2006
Old kernel : FreeBSD 6.1-STABLE #4: Wed Sep 6 16:01:23 PDT 2006
I also have nvidia and use firefox with
On Wed, 04 Oct 2006 00:56:36 +0400
Ruslan Ermilov [EMAIL PROTECTED] wrote:
How did you search for it?
with locate, find , ls and so on.
Oh crap, I just found out why I didn't find it. Just because the kernel
on my system is recent, doesn't mean that the system as a whole was
cvsup'ed recently.
On Tue, 03 Oct 2006 15:57:54 -0400
John Baldwin [EMAIL PROTECTED] wrote:
That I don't know. It might not be enabled on amd64. Does it work
before the patches and not after?
I haven't tried the patches yet, as I couldn't find the files it was
going to change.
That was an error on my part, as
I asked the question below a while back but got no answer.
Does that mean BCM5754 integrated GbE will not be supported
by 6.2 release at all? The HARDWARE.TXT file does not list
it, but the source code seems to have the BCM5754 support,
or at least so the CVS comments say.
Does anyone know when
Martin Blapp wrote:
Hi,
What about with just the first change and not the second? Anyways,
I'm starting to see a trend here. Problem reports are clustering
around UP
systems, not SMP systems. I don't know if that's just coincidence or
not.
We've got also about twenty SMP Systems, seven
Ulrich Spoerlein wrote:
cpghost wrote:
On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
Not that it helps you much, but I do see working pppoe redial behavior
with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl
line and it will autoreconnect as soon as it's plugged
All,
I'm seeing some patterns here with all of the network driver problem
reports, but I need more information to help narrow it down further.
I ask all of you who are having problems to take a minute to fill
out this survey and return it to Kris Kennaway (on cc:) and myself.
Thanks.
1. Are
Hello all,
I have spent the last week or so trouble shooting. I have been trying to
upgrade by freebsd install to p10 (I started having problems when I
tried upgrading to p9. I have been tracking RELENG_6_1.
FreeBSD is running on an older machine. Its a Dell OPIPLEX GX1 355Mhz,
64 Megs ram
Yi-Hua Edward Yang wrote:
I asked the question below a while back but got no answer.
Does that mean BCM5754 integrated GbE will not be supported
by 6.2 release at all? The HARDWARE.TXT file does not list
it, but the source code seems to have the BCM5754 support,
or at least so the CVS comments
There are a couple of people who have expressed interest in the work,
but no one is working on it currently.
-Kip
On 10/3/06, Marc G. Fournier [EMAIL PROTECTED] wrote:
I know there is work being done on this for -HEAD, but does anyone know if it
will run under -STABLE?
I don't see a port for
Marcus Alves Grando wrote:
Eric Anholt wrote:
On Mon, 2006-10-02 at 13:25 +0800, Ganbold wrote:
Hi,
I have strange problem with my Dell Latitude D620 laptop which has
945GM chipset and onboard graphic card.
I'm using September 30th RELENG_6.
If I use acpi_video only, mplayer can only use
On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote:
All,
I'm seeing some patterns here with all of the network driver problem
reports, but I need more information to help narrow it down further.
I ask all of you who are having problems to take a minute to fill
out this survey and
On Wed, Oct 04, 2006 at 03:41:48PM -0400, Kris Kennaway wrote:
On Wed, Oct 04, 2006 at 01:06:37PM -0400, Vivek Khera wrote:
On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote:
The only thing I think was running at the time would be a large file
copy from a remote system to this one
Bruno Ducrot writes:
| On Wed, Oct 04, 2006 at 02:07:12PM -0400, Bill Moran wrote:
| In response to Bruno Ducrot [EMAIL PROTECTED]:
| Hi,
|
| On Wed, Oct 04, 2006 at 12:28:35PM -0400, Bill Moran wrote:
|
|A reboot causes the OS to halt, but the hardware just sits there on the
|
79 matches
Mail list logo
