1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | workQPanic-Kernel work queue overflow while attempting async communication and thereafter initializing tyGSOctalModule with vxWorks |
From: | Mrinal Bera via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Sat, 28 Oct 2023 04:12:46 +0000 |
Hello,
While working with vxWorks 6.9.4 on MVME 3100 with TVME 200 and XM Octal modules, I get the following error whenever tried to start any asyn communication.
workQPanic: Kernel work queue overflow.
Exception at interrupt level:
Regs at 0x0
Exception at interrupt level:
data storage
Exception current instruction address: 0x0026bb84
Machine Status Register: 0x00001230
Data Exception Address Register: 0x01309ff0
Condition Register: 0x28002444
Exception Syndrome Register: 0x00800000
Regs at 0x1309f98
Press any key to stop auto-boot...
6
After that, the system reboots automatically and then keeps showing the same error while initializing tyGSOctalModule as can be seen below:
# tyGSOctalModuleInit(char *name, charBooting mv3100...
workQPanic: Kernel work queue overflow.
Exception at interrupt level:
Regs at 0x0
Exception at interrupt level:
data storage
Exception current instruction address: 0x0026bb84
Machine Status Register: 0x00001230
Data Exception Address Register: 0x01309ff0
Condition Register: 0x28002444
Exception Syndrome Register: 0x00800000
Regs at 0x1309f98
Press any key to stop auto-boot...
6
This error repeats on every auto reboot unless the VME crate is switched OFF and switched ON again.
I saw a very old tech-talk thread on this error: https://epics.anl.gov/tech-talk/1999/msg00470.php
I could understand that its something to do with too many interrupts happening but couldn’t figure out how to get rid of this issue.
Here is my ipac and serial setup:
ipacAddTVME200("601fa2")
tyGSOctalDrv(2)
tyGSOctalModuleInit("UART0","232",
0x80,
0,
0)
tyGSAsynInit("serial1",
"UART0",
0,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial2",
"UART0",
1,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial3",
"UART0",
2,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial4",
"UART0",
3,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial5",
"UART0",
4,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial6",
"UART0",
5,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial7",
"UART0",
6,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial8",
"UART0",
7,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n”)
tyGSOctalModuleInit("UART1",
"232",
0x81,
0,
1)
tyGSAsynInit("serial9",
"UART1",
0,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial10",
"UART1",
1,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial11",
"UART1",
2,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial12",
"UART1",
3,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial13",
"UART1",
4,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial14",
"UART1",
5,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial15",
"UART1",
6,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n")
tyGSAsynInit("serial16",
"UART1",
7,
9600, 'O',
1,
7, 'N',
"\r\n",
"\r\n”)
dbLoadTemplate("substitutions/asynRecord.substitutions”)
Any ideas on how to get rid of this error?
Thanks and regards,
Mrinal
|