On Friday 04 December 2009 10:35:59 am John Baldwin wrote:
> On Thursday 03 December 2009 4:20:08 pm Hiroki Sato wrote:
> > John Baldwin wrote
> > in <200912030803.29797@freebsd.org>:
> >
> > jh> On Thursday 03 December 2009 5:29:13 am Hiroki Sato wrote:
> > jh> > John Baldwin wrote
> > jh
If you have a large number of routes then you will want to disable the
flowtable. The default maximum number of cacheable flows is fairly
small, raising it can help on the low-end, but fundamentally its an
optimization for systems that have fewer than a few thousand
simultaneous peers - the common
Am 04.12.2009 um 20:56 schrieb Stefan Bethke:
> Am 04.12.2009 um 17:52 schrieb Stefan Bethke:
>
>> I'm getting panics like this every so often (couple weeks, sometimes just a
>> few days.) A second machine that has identical hardware and is running the
>> same source has no such problems.
>>
>
Am 04.12.2009 um 21:33 schrieb Jeremy Chadwick:
> You only have one disk in your pool. I'm not sure how long your system
> stays up before it panics, but could you try doing "zpool scrub tank"
> and let that run for a while? The first ~5 minutes may show the time to
> completion (from "zpool st
Am 04.12.2009 um 21:20 schrieb Thomas Backman:
> Bad RAM/motherboard? My first thought when I read your first mail (re:
> identical hardware) was bad hardware, and this seems to point towards that
> too, no?
> Have you tried memtest86+?
No, I haven't yet, since I don't have physical access righ
On Fri, Dec 04, 2009 at 08:56:05PM +0100, Stefan Bethke wrote:
> Am 04.12.2009 um 17:52 schrieb Stefan Bethke:
>
> > I'm getting panics like this every so often (couple weeks, sometimes just a
> > few days.) A second machine that has identical hardware and is running the
> > same source has no
On Dec 4, 2009, at 8:56 PM, Stefan Bethke wrote:
> Am 04.12.2009 um 17:52 schrieb Stefan Bethke:
>
>> I'm getting panics like this every so often (couple weeks, sometimes just a
>> few days.) A second machine that has identical hardware and is running the
>> same source has no such problems.
>>
On Friday 04 December 2009 02:33 pm, S.N.Grigoriev wrote:
> Hi list,
>
> I've installed openjdk6 from
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/jav
>a. Does this package contain a browser java plugin? I can't find it.
> Any tips are appreciated.
No, OpenJDK does not have a
Am 04.12.2009 um 17:52 schrieb Stefan Bethke:
> I'm getting panics like this every so often (couple weeks, sometimes just a
> few days.) A second machine that has identical hardware and is running the
> same source has no such problems.
>
> FreeBSD XXX.hanse.de 8.0-STABLE FreeBSD 8.0-STABLE #16
Hi list,
I've installed openjdk6 from
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/java.
Does this package contain a browser java plugin? I can't find it. Any tips are
appreciated.
Regards,
Serguey.
___
freebsd-stable@freebsd.org ma
On Sat, Dec 05, 2009 at 03:26:45AM +0900, Yoshiaki Kasahara wrote:
> On Fri, 4 Dec 2009 09:36:01 -0800,
> Pyun YongHyeon said:
>
> >> After I rebooted with the new kernel, the boot sequence stopped just
> >> after setting hostname.
> >>
> >> Setting hostname: elvenbow.cc.kyushu-u.ac.jp
> >
On Fri, 4 Dec 2009 09:36:01 -0800,
Pyun YongHyeon said:
>> After I rebooted with the new kernel, the boot sequence stopped just
>> after setting hostname.
>>
>> Setting hostname: elvenbow.cc.kyushu-u.ac.jp
>> msk0: Uncorrectable PCI Express error
>> vge0: link state changed to DOWN
>> ms
On Fri, Dec 04, 2009 at 02:47:35PM +0900, Yoshiaki Kasahara wrote:
> On Thu, 3 Dec 2009 15:08:10 -0800,
> Pyun YongHyeon said:
>
> > I remember there were several instability reports of vge(4). Would
> > you try the following patch? The patch was generated against
> > CURRENT so it may not
Ok, anyway thanks for your time.
Best Regards
Leonardo Santagostini
2009/12/4 Jung-uk Kim :
> On Thursday 03 December 2009 09:27 pm, Leonardo Santagostini wrote:
>> Sorry, but ive not backed up this file, instead of this, i will
>> copy the entire function (in fact its very short)
>>
>> cpi_pci
I'm getting panics like this every so often (couple weeks, sometimes just a few
days.) A second machine that has identical hardware and is running the same
source has no such problems.
FreeBSD XXX.hanse.de 8.0-STABLE FreeBSD 8.0-STABLE #16: Tue Dec 1 14:30:54 UTC
2009 r...@xxx.hanse.de:/us
On Thursday 03 December 2009 09:27 pm, Leonardo Santagostini wrote:
> Sorry, but ive not backed up this file, instead of this, i will
> copy the entire function (in fact its very short)
>
> cpi_pcib_pci_attach(device_t dev)
> {
> struct acpi_pcib_softc *sc;
> ACPI_FUNCTION_TRACE((char *)(ui
On Thursday 03 December 2009 4:20:08 pm Hiroki Sato wrote:
> John Baldwin wrote
> in <200912030803.29797@freebsd.org>:
>
> jh> On Thursday 03 December 2009 5:29:13 am Hiroki Sato wrote:
> jh> > John Baldwin wrote
> jh> > in <200912020948.05698@freebsd.org>:
> jh> >
> jh> > jh> On Tue
At 10:46 PM 12/3/2009, Zaphod Beeblebrox wrote:
I'm still investigating this, but my quagga is locking hard on FreeBSD 8.0
and not locking hard on 7.2. It seems (at this early point in the
investigation) that both bgpd and zebra are wedging and zebra is listed as
being in the "RUN" state.
curio
I have also seen this with a recent version of FreeBSD 8 (I know 8.0-BETA2
didn't have this problem, also I have an 8.0-RC1 without problems, but I think
RC3 did have it, and I'm sure -RELEASE has it).
A few more details:
It happened both on amd64 and i386. I couldn't debug amd64 (it was a
19 matches
Mail list logo
