Date: Thu, 27 May 99 12:03:53 -0400 From: msb <mboers@DatacompUSA.com> To: "Bruce Evans" <bde@zeta.org.au>, <bob@anet.donetsk.ua>, <freebsd-hardware@FreeBSD.ORG> Cc: <freebsd-hackers@FreeBSD.ORG> Subject: Re: Multiproc kernel 3.1-Release & Cyclades Cyclom 8Yep PCI Message-ID: <199905271602.MAA18893@datacompusa.com>
next in thread | raw e-mail | index | archive | help
>>I have multiprocessor machine:
>>
>>matherboard SOYO 5TX2/X5 with 2 intel 166 proceccors
>>multiport card Cyclades Cyclom 8Yep
>>
>>All good work until somthing do start to send to /dev/cXX
>>Then kernel panic and reboot !!!
>>
>There seems to be a problem with nested locks. What was the panic
>message?
I have the same problem with my Cyclom Ye cards (both the isa & pci
variety)
The kernel panics with:
panic messages:
---
panic: rslock: cpu: 0, addr: 0xf026a15c, lock: 0x00000001
mp_lock = 00000001; cpuid = 0; lapic.id = 00000000
a stack trace shows:
#0 boot (howto=260) at ../../kern/kern_shutdown.c:285
#1 0xf01340a5 in panic (fmt=0xf0218870 "from debugger")
at ../../kern/kern_shutdown.c:446
#2 0xf0119e35 in db_panic (addr=-266450897, have_addr=0, count=-1,
modif=0xf8cf0bf0 "") at ../../ddb/db_command.c:432
#3 0xf0119dd5 in db_command (last_cmdp=0xf0232fbc, cmd_table=0xf0232e1c,
aux_cmd_tablep=0xf0245c50) at ../../ddb/db_command.c:332
#4 0xf0119e9a in db_command_loop () at ../../ddb/db_command.c:454
#5 0xf011c1eb in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#6 0xf01e45d1 in kdb_trap (type=3, code=0, regs=0xf8cf0ce4)
at ../../i386/i386/db_interface.c:157
#7 0xf01f7bd8 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi =
-257314816,
tf_esi = 256, tf_ebp = -120648408, tf_isp = -120648436,
tf_ebx = -266377223, tf_edx = -266174249, tf_ecx = 8, tf_eax = 18,
tf_trapno = 3, tf_err = 0, tf_eip = -266450897, tf_cs = 8,
tf_eflags = 70, tf_esp = -266174265, tf_ss = -266228530})
at ../../i386/i386/trap.c:548
#8 0xf01e482f in Debugger (msg=0xf021acce "panic")
at ../../i386/i386/db_interface.c:317
#9 0xf013409c in panic (
fmt=0xf01f67f9 "rslock: cpu: %d, addr: 0x%08x, lock: 0x%08x")
at ../../kern/kern_shutdown.c:444
#10 0xf01f67f9 in bsl1 ()
#11 0xf01fd2b9 in cyopen (dev=12416, flag=5, mode=8192, p=0xf8ceae60)
at ../../i386/isa/cy.c:755
#12 0xf0162d25 in spec_open (ap=0xf8cf0e30)
at ../../miscfs/specfs/spec_vnops.c:210
#13 0xf0162ba9 in spec_vnoperate (ap=0xf8cf0e30)
at ../../miscfs/specfs/spec_vnops.c:129
#14 0xf01c6121 in ufs_vnoperatespec (ap=0xf8cf0e30)
at ../../ufs/ufs/ufs_vnops.c:2312
#15 0xf015d436 in vn_open (ndp=0xf8cf0f04, fmode=5, cmode=0) at
vnode_if.h:163
#16 0xf0159f45 in open (p=0xf8ceae60, uap=0xf8cf0f94)
at ../../kern/vfs_syscalls.c:935
#17 0xf01f8423 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi =
134868999,
tf_esi = 134800052, tf_ebp = -272638536, tf_isp = -120647708,
tf_ebx = 134865472, tf_edx = 11, tf_ecx = 0, tf_eax = 5, tf_trapno
= 12,
tf_err = 2, tf_eip = 134548388, tf_cs = 31, tf_eflags = 582,
tf_esp = -272638592, tf_ss = 39}) at ../../i386/i386/trap.c:1100
#18 0xf01e4fec in Xint0x80_syscall ()
line 755 in cy.c is a call to commctl which is also defined in cy.c
cy.c line 755 is "(void)commctl(com, TIOCM_DTR | TIOCM_RTS, DMSET);"
after crash debugging shows that the value of com is 0x3 at the time of
crash. Since com is a pointer, I think we know that it is wrong. I have
added a printf statement to a varitation of cy.c that shows that just
before the call to commctl, the value of com is correct (not 3).
Any help towards getting the cy driver up and running on the smp kernel
would be appreciated.
--
Michael Boers
Datacomp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905271602.MAA18893>