On Tue, Jul 18, 2006 at 07:51:52AM -0300, User Freebsd wrote:
>
> 'k, had a bunch of fun tonight, but one of the results is that I was able
> to achieve file system deadlock, or so it appears ...
>
> Using the following from DDB:
>
> set $lines=0
> show pcpu
> show allpcpu
> ps
> trace
> alltra
On Wed, 19 Jul 2006, Kostik Belousov wrote:
On Wed, Jul 19, 2006 at 01:31:17AM -0300, User Freebsd wrote:
Kostik/Robert ... does this provide enough (any?) information concerning
the deadlock situation(s) that are being reported? is there anything else
I should do the next time it happens?
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hej Ho,
for quite a while my server (root server / dedicated server) goes
completely dead - sometimes after several weeks, sometimes after 24h hours.
I always thought it's the hosting company and not FreeBSD, but today I
could see the panic.
Looks lik
On Wed, 19 Jul 2006, Kostik Belousov wrote:
You did not provided the output of "show lockedbufs",
Added to my debug list ...
but, even without that data, I doubt that the buf subsystem deadlocked by
itself.
I make an conjecture that the problem is either with you disk hardware (i.e.,
actual
On Wed, 19 Jul 2006, User Freebsd wrote:
Also note that under FreeBSD 4.x, all three of these machines were pretty
much my more solid machines, with even more vServers running on them then
I'm able to run with 6.x ... once I got rid of using unionfs, stability
skyrocketed :(
Hr ... but,
On Wed, 19 Jul 2006, Robert Watson wrote:
On Wed, 19 Jul 2006, User Freebsd wrote:
Also note that under FreeBSD 4.x, all three of these machines were pretty
much my more solid machines, with even more vServers running on them then
I'm able to run with 6.x ... once I got rid of using unionfs,
On Wed, Jul 19, 2006 at 11:23:21AM -0300, User Freebsd wrote:
> On Wed, 19 Jul 2006, Robert Watson wrote:
>
> >
> >On Wed, 19 Jul 2006, User Freebsd wrote:
> >
> >>Also note that under FreeBSD 4.x, all three of these machines were pretty
> >>much my more solid machines, with even more vServers ru
On Wed, 19 Jul 2006, User Freebsd wrote:
Yes, this was going to be my next question -- if you're seeing wedges under
load and there's a common controller in use, maybe we're looking at a
driver bug. Bugs of those sort typically look a lot like what you
describe: an I/O is "lost" and so eveyth
On Wed, 19 Jul 2006, Kostik Belousov wrote:
On Wed, Jul 19, 2006 at 11:23:21AM -0300, User Freebsd wrote:
On Wed, 19 Jul 2006, Robert Watson wrote:
On Wed, 19 Jul 2006, User Freebsd wrote:
Also note that under FreeBSD 4.x, all three of these machines were pretty
much my more solid machines
On Wed, 19 Jul 2006, Robert Watson wrote:
On Wed, 19 Jul 2006, User Freebsd wrote:
Yes, this was going to be my next question -- if you're seeing wedges
under load and there's a common controller in use, maybe we're looking at
a driver bug. Bugs of those sort typically look a lot like what y
Disable hyperthreading in your BIOS.
At 10:20 AM 7/18/2006, Martin Blapp wrote:
Hi,
Ok, seems to be a HTT issue on a untuned system.
On two boxes I get with 'sysctl -a | grep smp | grep kern.smp.cpus'
kern.smp.cpus: 4
Here I see CPU-IDs 0 and 2 in top. No other CPUs seem to be
used. Here I g
User Freebsd wrote:
On Wed, 19 Jul 2006, Robert Watson wrote:
On Wed, 19 Jul 2006, User Freebsd wrote:
Yes, this was going to be my next question -- if you're seeing
wedges under load and there's a common controller in use, maybe
we're looking at a driver bug. Bugs of those sort typically l
On Wed, 19 Jul 2006, User Freebsd wrote:
'k, first question is with the core file provide any insight into this? ie.
provide further confirmation that it looks like the driver vs file system?
Quite possibly, yes.
second question, who is currently maintaining the iir driver? I've CC'd
Achim
Sounds like what always happens when crappy power management stuff is
enabled either on the station or the ap.
I would investigate that first.
Victor Semionov wrote:
Hello list,
I have a wireless card with an Atheros 5212 chipset and I'm experiencing the
following behavior under FreeBSD 6.1:
Hi,
Disable hyperthreading in your BIOS.
Off course this is a solution, but I don't like
it. On a untuned, unmodified, unpatched system top(1)
should display the correct values IMHO.
Martin
___
freebsd-stable@freebsd.org mailing list
http://lists.f
Martin Blapp wrote:
>
> Hi,
>
>> Disable hyperthreading in your BIOS.
>
> Off course this is a solution, but I don't like
> it. On a untuned, unmodified, unpatched system top(1)
> should display the correct values IMHO.
On some systems (like my Dell) it does work as expected on an untuned
syste
How is data transmission related to power management?
On Wednesday 19 July 2006 19:01, you wrote:
> Sounds like what always happens when crappy power management stuff is
> enabled either on the station or the ap.
> I would investigate that first.
>
> Victor Semionov wrote:
> > Hello list,
> >
> >
We just tried running programs under RELENG_6_1 that were compiled under
RELENG_6 checked out 2006-07-19, and couldn't because of the undefined
symbol "__res_state"l, which I would assume is a result of the recent
MFC of the BIND 9 resolver library.Is this to be expected? It will
cause a b
On Wed, 19 Jul 2006, Scott Long wrote:
Now, uranus has all the various kernel debugging enabled right now, and a
serial console, so we're good for the debugging side of things ... and I
believe that I can fairly easily "recreate" the issue by just moving a
whack of vServers onto that machine t
Replying to myself and top-posting...
A very helpful person contacted me off-list and pointed me to this PR that
dates back to 2.2:
http://www.freebsd.org/cgi/query-pr.cgi?pr=2325
I'm going to submit a followup to that so that whomever claims it can see
that it persists into at least 6.1.
Hi all,
I've experienced a panic on a database server running 6.1-STABLE (Jul
3). Altough I don't have a dump, my co-worked managed to take a
screenshot of the console thru DRAC. The text is all messed up as you'll
notice. I had never seen this behaviour (nor a trap 19, to be honest).
This se
Guy Helmer wrote:
We just tried running programs under RELENG_6_1 that were compiled under
RELENG_6 checked out 2006-07-19, and couldn't because of the undefined
symbol "__res_state"l, which I would assume is a result of the recent
MFC of the BIND 9 resolver library.Is this to be expected?
panic @ http://67.19.182.100/panic.jpg , sorry for that.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Scott Long wrote:
Guy Helmer wrote:
We just tried running programs under RELENG_6_1 that were compiled
under RELENG_6 checked out 2006-07-19, and couldn't because of the
undefined symbol "__res_state"l, which I would assume is a result of
the recent MFC of the BIND 9 resolver library.Is th
Guy Helmer wrote:
Scott Long wrote:
Guy Helmer wrote:
We just tried running programs under RELENG_6_1 that were compiled
under RELENG_6 checked out 2006-07-19, and couldn't because of the
undefined symbol "__res_state"l, which I would assume is a result of
the recent MFC of the BIND 9 resol
I just had a kernel panic. This happened seconds after I started a
reboot using alt-ctl-del, at about the time just after it it said it was
writing the entropy file.
Here is the kernel config file, the results of the dump, and dmesg. Do
you want anything else? I hope this info helps.
incl
In message: <[EMAIL PROTECTED]>
Guy Helmer <[EMAIL PROTECTED]> writes:
: We just tried running programs under RELENG_6_1 that were compiled under
: RELENG_6 checked out 2006-07-19, and couldn't because of the undefined
: symbol "__res_state"l, which I would assume is a result of the r
In message: <[EMAIL PROTECTED]>
"M. Warner Losh" <[EMAIL PROTECTED]> writes:
: In message: <[EMAIL PROTECTED]>
: Guy Helmer <[EMAIL PROTECTED]> writes:
: : We just tried running programs under RELENG_6_1 that were compiled under
: : RELENG_6 checked out 2006-07-19, and coul
M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Guy Helmer <[EMAIL PROTECTED]> writes:
> : We just tried running programs under RELENG_6_1 that were compiled under
> : RELENG_6 checked out 2006-07-19, and couldn't because of the undefined
> : symbol "__res_state"l, which I w
Hi,
> On Wed, 19 Jul 2006 18:12:15 -0600 (MDT)
> "M. Warner Losh" <[EMAIL PROTECTED]> said:
imp> In message: <[EMAIL PROTECTED]>
imp> Guy Helmer <[EMAIL PROTECTED]> writes:
imp> : We just tried running programs under RELENG_6_1 that were compiled under
imp> : RELENG_6 checked
On Tue, Jul 11, 2006 at 04:09:08PM -0300, Marcelo Gardini do Amaral wrote:
> Hi,
>
> I'm trying to setup polling in my box. [...]
> But I always get some packet loss.
A few points:
- Polling and SMP are compatible in 6.1. In fact, they were compatible
in earlier versions too; basically it's
31 matches
Mail list logo
