I just got two panics tonight, the same each time. Current from yesterday,
after the latest round of patch from Kirk. The second panic is exactly the
same including the trace.
-=-=-
(kgdb) exec-file /var/crash/kernel.7
(kgdb) core-file /var/crash/vmcore.7
IdlePTD 3661824
initial pcb at 2e5100
pa
Hi all,
when building a package on -current one gets:
===> Installing for bzip2-1.0.1
mtree: illegal option -- L
usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
[-X excludes]
*** Error code 1
Seems to be a problem in /usr/ports/Mk/bsd.port.mk:
.if ${OSVERSIO
Udo Schweigert wrote:
> ===> Installing for bzip2-1.0.1
> mtree: illegal option -- L
> usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
> [-X excludes]
> *** Error code 1
>
> Seems to be a problem in /usr/ports/Mk/bsd.port.mk:
>
> .if ${OSVERSION} >= 500010
>
[CC'ed -current and -mobile]
> BTW, there is one more problem during detach the pccard nic. When I
> detach my pccard nic, my kernel is panic. I tried this with Melco
> Airconnect WLI-PCM-L11 and COREGA FastEther PCC-TX, and it occured
> with either card.
> I made a quick hack to avoid this pro
On Tue, Jul 25, 2000 at 04:14:07 -0400, Donn Miller wrote:
> Udo Schweigert wrote:
>
> > ===> Installing for bzip2-1.0.1
> > mtree: illegal option -- L
> > usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
> > [-X excludes]
> > *** Error code 1
> >
> > Seems to
> On Tue, 25 Jul 2000 18:48:17 +0900
> [EMAIL PROTECTED] (Mitsuru IWASAKI) said:
> BTW, there is one more problem during detach the pccard nic. When I
> detach my pccard nic, my kernel is panic. I tried this with Melco
> Airconnect WLI-PCM-L11 and COREGA FastEther PCC-TX, and it occured
On 25/07, Hajimu UMEMOTO wrote:
| Yes, I think it is critical for IPv6 users. But, I have never hear
| the problem from other than me. Is this only my problem?
No, I reported it some time ago, and it looks like it is fixed in -CURRENT
sources.
To Unsubscribe: send mail to [EMAIL PROTECTED]
> On Tue, 25 Jul 2000 13:28:39 +0200
> [EMAIL PROTECTED] (Samuel Tardieu) said:
sam> On 25/07, Hajimu UMEMOTO wrote:
sam> | Yes, I think it is critical for IPv6 users. But, I have never hear
sam> | the problem from other than me. Is this only my problem?
sam> No, I reported it some ti
At 25 Jul 2000 07:37:43 GMT,
Ollivier Robert <[EMAIL PROTECTED]> wrote:
> I just got two panics tonight, the same each time. Current from yesterday,
> after the latest round of patch from Kirk. The second panic is exactly the
> same including the trace.
It seems I've got same panics. But sometim
> OK. We have no enough time. I'll commit it.
> Jordan, can I MFC this?
Only if you're really really sure it won't break something else.
I must confess that the way this one has turned up with no independant
confirmation makes me very nervous. :-(
- Jordan
To Unsubscribe: send mail to [EMAIL
On Tue, 25 Jul 2000, Jun Kuriyama wrote:
> At 25 Jul 2000 07:37:43 GMT,
> Ollivier Robert <[EMAIL PROTECTED]> wrote:
> > I just got two panics tonight, the same each time. Current from yesterday,
> > after the latest round of patch from Kirk. The second panic is exactly the
> > same including the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan van Beerschoten wrote:
> btw, I have some big problems with the new version of mtree .. it seems
that
> the -L flag has been abandoned.. which results in almost every port I try
> to install failing.. I have recompiled mtree from the tree and
On Tue, 25 Jul 2000, Ollivier Robert wrote:
> I just got two panics tonight, the same each time. Current from yesterday,
> after the latest round of patch from Kirk. The second panic is exactly the
> same including the trace.
Welp, I didn't get em before, but I do now. I'll see what I can do to
Actually, I'm pretty certain this is the fix:
Index: vfs_bio.c
===
RCS file: /usr2/ncvs/src/sys/kern/vfs_bio.c,v
retrieving revision 1.260
diff -u -r1.260 vfs_bio.c
--- vfs_bio.c 2000/07/11 22:07:43 1.260
+++ vfs_bio.c 2000/0
According to Brian Fundakowski Feldman:
> Actually, I'm pretty certain this is the fix:
Well it won't panic but isn't it putting the problem under the carpet? I
agree the panic seems to be here temporarely but...
--
Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED]
The Postman hits!
On Tue, 25 Jul 2000, Brian Fundakowski Feldman wrote:
> Actually, I'm pretty certain this is the fix:
>
I have removed the panic-calls. I'll see if my system gets otherwise
unstable.. For now i'll be happy if I get enough time for my make world
to complete before my system hangt itself again :
In message <7676.964529079@localhost> "Jordan K. Hubbard" writes:
: > OK. We have no enough time. I'll commit it.
: > Jordan, can I MFC this?
:
: Only if you're really really sure it won't break something else.
: I must confess that the way this one has turned up with no independant
: confirmat
According to Stephan van Beerschoten:
> But indeed.. isn't removing the panic cal just shifting the problem in
> stead of taking care of the panic-originator ?
That's what is bothering me :-)
> And what is the word on thise IOERROR's given by my kernel when its init'ing
> its usb stack.
It sta
On Tue, 25 Jul 2000, Ollivier Robert wrote:
> According to Brian Fundakowski Feldman:
> > Actually, I'm pretty certain this is the fix:
>
> Well it won't panic but isn't it putting the problem under the carpet? I
> agree the panic seems to be here temporarely but...
No, I'm really certain this
auth 0ad9305e unsubscribe freebsd-current [EMAIL PROTECTED]
> On Tue, 25 Jul 2000 09:35:53 -0600
> Warner Losh <[EMAIL PROTECTED]> said:
imp> In message <7676.964529079@localhost> "Jordan K. Hubbard" writes:
imp> : > OK. We have no enough time. I'll commit it.
imp> : > Jordan, can I MFC this?
imp> :
imp> : Only if you're really really sure it w
Date: Tue, 25 Jul 2000 11:47:03 -0400 (EDT)
From: Brian Fundakowski Feldman <[EMAIL PROTECTED]>
To: Ollivier Robert <[EMAIL PROTECTED]>
Cc: "FreeBSD Current Users' list" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Panic: lockmgr: pid 5, n
Stephan van Beerschoten wrote:
>
> And what is the word on thise IOERROR's given by my kernel when its init'ing
> its usb stack.
>
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> uhub0: port 1 power on failed, IOERROR
> uhub0: port
Thomas Stromberg wrote:
>
> It's probably been fixed by now, but what I did when I first had the
> mtree
> problem was set NO_MTREE in /usr/ports/Mk/bsd.port.mk - Not sure of the
> side
> affects though (anyone care to enligtnen me?)
>
> Im sure there is a more elegant solution, I was just looki
> Stephan van Beerschoten wrote:
> >
> > And what is the word on thise IOERROR's given by my kernel when its init'ing
> > its usb stack.
> >
> > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > uhub0: port 1 power on failed, IOERR
On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote:
> > Stephan van Beerschoten wrote:
> > >
> > > And what is the word on thise IOERROR's given by my kernel when its init'ing
> > > its usb stack.
> > >
> > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > > uhub0: 2 por
Wilko Bulte wrote:
> On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote:
> > > Stephan van Beerschoten wrote:
> > > >
> > > > And what is the word on thise IOERROR's given by my kernel when its init'ing
> > > > its usb stack.
> > > >
> > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.0
Even with version 1.54 of mfs_vnops.c and a freshly built world and booted
kernel (with ``options MFS''), I am still seeing these. What could I be
missing?
Thanks,
--
Jos Backus <[EMAIL PROTECTED]>
WebTV Networks, Inc., Mountain View, CA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
Thanks,
--
Jos Backus <[EMAIL PROTECTED]>
WebTV Networks, Inc., Mountain View, CARe: Still seeing /kernel:
mfs_badop[vop_getwritemount] = 45
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Jos Backus wrote:
>Even with version 1.54 of
In message <[EMAIL PROTECTED]> Hajimu UMEMOTO writes:
: Yes, panic will happen only during detach the card. So, install
: should be OK. I'll MFC after 4.1-RELEASE is out.
: Thank you for your suggestion and sorry for makeing this situation.
Thank you for letting us know of the problem. There's
30 matches
Mail list logo
