lock order reversal
1st 0xc03bbde0 arp mutex (arp mutex) @ ../../../netinet/if_ether.c:151
2nd 0xc6149e7c radix node head (radix node head) @ ../../../net/route.c:549
Debugger(witness_lock)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db trace
One of the alpha package clients panicked with this. It was under
very high load at the time (25 simultaneous package builds):
fatal kernel trap:
trap entry = 0x2 (memory management fault)
faulting va= 0xdeadc0dedeadc0e6
type = access violation
cause =
I sent this message off about 12 hours ago, and I have not seen
it appear anywhere. Since then I have received plenty of other
messages on the mailing lists (including messages I sent after
I sent this one). So, I'm resending this one...
On Jan 24/2003, Max Khon wrote to freebsd-current:
hi,
On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote:
...
Don't use the '-r' option, it gets confused because geom::BSD does
not lie to it.
Yes, that seems to work...
Time to say good bye for '-r' ?
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
To Unsubscribe: send mail to [EMAIL
In message [EMAIL PROTECTED], Michael Reifenberger
writes:
On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote:
...
Don't use the '-r' option, it gets confused because geom::BSD does
not lie to it.
Yes, that seems to work...
Time to say good bye for '-r' ?
Well, we still need it for writing the first
On Sat, Jan 25, 2003 at 10:17:39 +0100, [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Michael Reifenberger
writes:
On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote:
...
Don't use the '-r' option, it gets confused because geom::BSD does
not lie to it.
Yes, that seems to work...
Time
On Sat, Jan 18, 2003 at 02:46:38PM -0800, David O'Brien wrote:
On Sat, Jan 18, 2003 at 06:46:40PM +0200, Mikko Hyvarinen wrote:
Hi again,O
I find it outright odd that the partial patch that didn't help much got
committed quickly but the final fix that makes things work didn't.
Is
hmm, I have no problem with my FireWire CardBus card.
If you can get traceback in DDB, please send it to me.
cardbus0: Resource not specified in CIS: id=10, size=800
cardbus0: Resource not specified in CIS: id=14, size=4000
fwohci1: Texas Instruments TSB43AA22 mem
: dstumbler breaks; on startup it reports
: unable to ioctl device socket: Input/output error.
As root or no?
I have a rebuilt system finally that I could test this against and I'm
actually getting a different error message on startup of dstumbler:
error: unable to ioctl device
On Fri, Jan 24, 2003 at 11:03:52PM -0800, David Schultz wrote:
FreeBSD's ``fix'' for this problem is the same as Windows 98's.
Specifically, there is a 5-second delay (tuneable:
kern.shutdown.poweroff_delay) after all buffers are flushed but
before the power is cut. Maybe we ought to be
Attached is a panic and patch a patch for the problem in the Subject line.
The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
has its P_CONTROLT flag set, then it's session has a valid vnode for it's
controlling terminal. This doesn't hold if the terminal was revoked.
On Fri, 24 Jan 2003, David Schultz wrote:
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown -p. It's possible that the shutdown powered
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have you connected a fw device to the
firewire card?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
In message [EMAIL PROTECTED], Peter Edwards writes:
The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
has its P_CONTROLT flag set, then it's session has a valid vnode for it's
controlling terminal. This doesn't hold if the terminal was revoked.
Can you try this patch
dstumbler uses WI_RID_SCAN_REQ to initiate a scan for AP's. This
required the application know whether it was talking to a
prims/wavelan/symbol card so was replaced by WI_RID_SCAN_APS which
provides a device-independent interface. I changed wicontrol to
deal with this; it would be good if
Fixed. Thanks!
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
msg50907/pgp0.pgp
Description: PGP signature
Is this a known panic? I tried to search the mailinglist archives to
see if somebody had posted something similar, but I couldn't find
anything.
The system is running 5.0-RELEASE with a pretty standard kernel (just
removed all the drivers I don't use and added SMP support). I think
the load of
On Sat, 25 Jan 2003, Morten Rodal wrote:
The system is running 5.0-RELEASE with a pretty standard kernel (just
removed all the drivers I don't use and added SMP support). I think
the load of the system might have been high at the moment as I had
just started
cd /usr/ports make -j8 clean
Thus spake Nate Lawson [EMAIL PROTECTED]:
On Fri, 24 Jan 2003, David Schultz wrote:
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown
On Sat, Jan 25, 2003 at 12:38:28PM -0800, Nate Lawson wrote:
The question is, why? I suspect something to do with memory due to the
second two bytes being a valid kernel address. How about a dmesg?
[forgot to cc: [EMAIL PROTECTED]]
Are you suspecting faulty memory?
See attached dmesg.boot.
On Sat, Jan 25, 2003 at 12:59:25PM -0600, Alan L. Cox wrote:
Kris Kennaway wrote:
bento found the following about 5 minutes after I upgraded it to 5.0.
acquiring duplicate lock of same type: system map
1st system map @ ../../../vm/vm_map.c:2168
2nd system map @
This patch is needed for the MIPS port's infrastructure, and will be
needed for the PowerPC one, as given ports may support any number of
platforms, on those architectures (and arguably, the same applies to
i386 vs. pc98, but historically...). What it does is it sets up a
build-time (and
I have acpi disabled and apm enabled in /boot/device.hints
because acpi didn't do standby properly: apm -Z wouldn't turn off the
screen backlight, and on reawakening the screen would be messed up.
(acpiconf -s {2,3} didn't work either.) With acpi, the following
problem doesn't exist. It also
Kris Kennaway wrote:
bento found the following about 5 minutes after I upgraded it to 5.0.
acquiring duplicate lock of same type: system map
1st system map @ ../../../vm/vm_map.c:2168
2nd system map @ ../../../vm/vm_kern.c:325
Thanks for the stack trace. I've finally flagged the system
On Sun, 2003-01-26 at 08:08, David Schultz wrote:
Good. I was referring to IDE in this case, because I assume
that's what Greg's laptop uses. The ATA driver flushes the cache
when the device is closed, but I don't think that happens during
shutdown. It probably needs to register a shutdown
I'm about to commit code that will make one of :
options SCHED_4BSD
or
options SCHED_ULE
mandatory. This will go in a few hours from now. I will update all of
the standard config files to account for this change. SCHED_4BSD selects
the old scheduler in case you're wondering. Failure to
Ok, this has been commited. Expect build breakage if you don't add one of
these options or use GENERIC.
Cheers,
Jeff
On Sun, 26 Jan 2003, Jeff Roberson wrote:
I'm about to commit code that will make one of :
options SCHED_4BSD
or
options SCHED_ULE
mandatory. This will go in a few
You are missing the src-sys-crypto collection in your supfile.
Either use the src-all collection (*strongly* recommended) or else
read the examples in /usr/share/examples/cvsup carefully and make
sure you are getting all the collections you need.
I guess submitting a patch to
I found the same problem in my FreeBSD box.
Isn't anyone have further informations about this problem?
*** my environment is following:
- FIC PA-2013 motherboard (VIA MVP3 chipsets)
- SiS900 NIC
*** dmesg says: ***
Jan 11 23:15:32 rulue kernel: sis0: SiS 900 10/100BaseTX port
Hey Bro,
Check out this pick. It's GUARANTEED TO WIN.
FAVORITE LINE UNDERDOG
Raiders 4 Bucs
Take RAIDERS.
My source is NEVER wrong.
Get back to me when you win and have fun counting your
30 matches
Mail list logo
