Quoting Michel Talon <[EMAIL PROTECTED]>:
I guess I'm still just a bit stunned that a bug this obvious not only
found it's way into the STABLE branch, but is still there. Maybe it's
not as obvious as I think, or not many folks are using it? All I know
for sure here is that if I had upgraded to
On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote:
> Kostik Belousov writes:
> >Since nobody except you experience that problems (at least, only you
> >notified
> >about the problem existence)
>
> Did you miss the part of:
>
> >User Freebsd writes:
> >>Since there are several of us
Kostik Belousov writes:
I think that then 6.2 and 6.3 is not for you either. Problems
cannot be fixed until enough information is given.
I am trying.. but so far only other users who are having the same problem
are commenting on this and other simmilar threads.
We just need some guidance..
On Friday 30 June 2006 10:21, Daniel O'Connor wrote:
> I have an odd problem with 6.1 where it panics, and then when it reboots
> the system hangs solid just after printing how much memory is in the
> system, the only way out is the reset switch.
> Fatal trap 12: page fault while in kernel mode
> f
On Sun, Jul 02, 2006 at 05:49:44PM -0400, Francisco Reyes wrote:
> User Freebsd writes:
>
> >Since there are several of us experiencing what looks to be the same sort
> >of deadlock issue, I beseech you not to give up
>
> I will try to setup the environment, but to be honest no more 6.X for us
>Submitter-Id: stable-users
>Originator:Iasen Kostoff
>Organization: OTEL.net
>Confidential: no
>Synopsis: Bug in ata (ata-all.c) driver
>Severity: serious
>Priority: medium
>Category: kern
>Class: sw-bug
>Release: FreeBSD 6.1-STABLE i386
>Environ
On Saturday 01 July 2006 21:24, ASTESIN wrote:
> Purpose: just Apache + mod_perl + MySQL 5.x application server.
> Install went fine, system boots, I'm going to try PAE kernel on it. But
> somathing makes me doubt that things are going on well...
>
> I.e. I worry about strange messages in dmesg out
User Freebsd writes:
Since there are several of us experiencing what looks to be the same sort
of deadlock issue, I beseech you not to give up
I will try to setup the environment, but to be honest no more 6.X for us
until 6.2 or 6.3.. We have lost clients already.
Is this a problem that yo
On Sun, 02 Jul 2006 15:34:24 +0200
Volker <[EMAIL PROTECTED]> wrote:
> I've had the same today and thought it has been my mistake (doing a
> pkg_version in parallel).
Ther seems to ne a problem with the latest version of portupgrade, this
happened for me on two 6-stable systems (one i386, the oth
Hello.
Tried today to delete and prepare a fresh installed external USB 2.0
drive as GELI provider, here is the result of an aborted dd:
sotokan# dd if=/dev/random of=/dev/da0a.eli bs=16k
^C8388825+0 records in
8388824+0 records out
137442492416 bytes transferred in 33883.288406 secs (4056350 b
On Sat, 1 Jul 2006, Francisco Reyes wrote:
John Hay writes:
I only started to see the lockd problems when upgrading the server side
to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x
and 7-current and the lockd problem only showed up when upgrading the
server from 5.x to 6.x.
In the last episode (Jul 02), Robert Watson said:
> On Sun, 2 Jul 2006, Fabian Keil wrote:
> >The ssh man page offers:
> >
> >|~B Send a BREAK to the remote system (only useful for SSH
> >|protocol version 2 and if the peer supports it).
> >
> >I am using ssh 2, but the only reaction I
Robert Watson <[EMAIL PROTECTED]> wrote:
> On Sun, 2 Jul 2006, Fabian Keil wrote:
> > I am using ssh 2, but the only reaction I get is a new line.
> >
> > |FreeBSD/i386 (tor.fabiankeil.de) (ttyd0)
> > |
> > |login: ~B
> > |
>
> It sounds like your serial console server may not know how to map SS
On Sun, 2 Jul 2006, Fabian Keil wrote:
Robert Watson <[EMAIL PROTECTED]> wrote:
On Sun, 2 Jul 2006, Fabian Keil wrote:
After manually triggering a test panic through debug.kdb.enter I
could enter ddb and everything seemed to be working.
However today I got another hang and couldn't enter t
Robert Watson <[EMAIL PROTECTED]> wrote:
> On Sun, 2 Jul 2006, Fabian Keil wrote:
> > After manually triggering a test panic through debug.kdb.enter I
> > could enter ddb and everything seemed to be working.
> >
> > However today I got another hang and couldn't enter the debugger by
> > sending B
This is the same issue that I've been hitting, and that requires the
serial console / DDB stuff described in the debugging deadlocks web page
that I pointed you at ...
So far *knock on wood* since adding all of the debugging to one of my
server, none of mine have done it ... but the more ppl
On Sunday 02 July 2006 08:37, Dominik Zalewski wrote:
> On Sunday 02 July 2006 16:35, Vlad GALU wrote:
> > On 7/2/06, Dominik Zalewski <[EMAIL PROTECTED]> wrote:
> > > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using
> > > cvsup and then I ran as usually portupgrade -a . It upgrad
On Sun, 2 Jul 2006, Fabian Keil wrote:
I'm very interested in tracking down this problem, but have had a lot of
trouble getting reliable reports of problems -- i.e., ones where I could
get any debugging information. I had a similar conversation on these lines
yeterday with Roger (Tor author)
Robert Watson <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Jun 2006, Fabian Keil wrote:
>
> > There was a "request" for Tor related problem reports a while ago,
> > I couldn't find the message again, but I believe it was posted here.
>
> I'm very interested in tracking down this problem, but have had
Thanks a lot. After I remove the kdbmux, it works fine. :)
On 7/2/06, Robert Watson <[EMAIL PROTECTED]> wrote:
On Sun, 2 Jul 2006, Ren Zhen wrote:
> After I login, press Ctrl+Alt+ESC, kernel says:
> KDB: enter: manual escape to debugger
> [thread pid 16 tid 100014 ]
> Stopped at kdb_ente
On Sunday 02 July 2006 16:35, Vlad GALU wrote:
> On 7/2/06, Dominik Zalewski <[EMAIL PROTECTED]> wrote:
> > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup
> > and then I ran as usually portupgrade -a . It upgraded my portupgrade to
> > version portupgrade-2.1.3.2,2. After
On Sunday 02 July 2006 16:34, you wrote:
> On 12/23/-58 20:59, Dominik Zalewski wrote:
> > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup
> > and then I ran as usually portupgrade -a . It upgraded my portupgrade to
> > version portupgrade-2.1.3.2,2. After that portupgrade
On 7/2/06, Dominik Zalewski <[EMAIL PROTECTED]> wrote:
I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and
then I ran as usually portupgrade -a . It upgraded my portupgrade to version
portupgrade-2.1.3.2,2. After that portupgrade stopped working.
Here is an error message
On 12/23/-58 20:59, Dominik Zalewski wrote:
> I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and
> then I ran as usually portupgrade -a . It upgraded my portupgrade to version
> portupgrade-2.1.3.2,2. After that portupgrade stopped working.
>
> in /var/db/pkg ... /var/d
I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and
then I ran as usually portupgrade -a . It upgraded my portupgrade to version
portupgrade-2.1.3.2,2. After that portupgrade stopped working.
Here is an error message:
[EMAIL PROTECTED] /]# portupgrade -a
[Updating the p
On Sun, 2 Jul 2006, Ren Zhen wrote:
After I login, press Ctrl+Alt+ESC, kernel says:
KDB: enter: manual escape to debugger
[thread pid 16 tid 100014 ]
Stopped at kdb_enter+0x2b: nop
db>
Then, my T23 lock up. I can only switch off the computer.
But, I use "boot -d" at booting kdb will wor
After I login, press Ctrl+Alt+ESC, kernel says:
KDB: enter: manual escape to debugger
[thread pid 16 tid 100014 ]
Stopped at kdb_enter+0x2b: nop
db>
Then, my T23 lock up. I can only switch off the computer.
But, I use "boot -d" at booting kdb will work fine. I press c it continue.
When "lo
27 matches
Mail list logo
