# Query on kernel crash **URL:** \ **Category:** Uncategorized\ **Created:** [September 11, 2026, 9:27pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103 "2026-09-11T21:27:48Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 11, 2026, 9:27pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/1 "2026-09-11T21:27:48Z")
Hi Team, I am seeing a kernel crash with below dumps. Wondering if there is any know issue or patch available. This is on 2.6 kernel, qmisdk (04.00.11) with gobi-net\_2.50, with EM7565 module . 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Unhandled kernel unaligned access[#1]: 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Cpu 0 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $ 0 : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $ 4 : 0000000000000010 0000000000000001 0000000000000000 ffffffff8523e1cf 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $ 8 : 0000000000000000 312f312d312f312d 312e342f312d312e 343a312e332f6570 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $12 : 0000000010008ce1 000000001000001e ffffffff80336450 0000000000000000 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $16 : a800000003553ad0 ffffff0000000000 ffffffffdc5e0008 2aded09ccdfbe639 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $20 : a800000004aa2850 a800000003484a80 a800000004aa2850 000000002b2fdbf0 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $24 : 0000000000000001 ffffffff80484288 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] $28 : a800000003550000 a800000003553aa0 000000002b39d040 ffffffff80100c04 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Hi : 0000000000000000 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Lo : 0000000000000000 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] epc : ffffffff8025dd18 do\_ade+0x2b8/0x5c0 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Tainted: P 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] ra : ffffffff80100c04 ret\_from\_exception+0x0/0x10 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Status: 10008ce3 KX SX UX KERNEL EXL IE 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Cause : 00800010 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] BadVA : 2aded09ccdfbe639 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] PrId : 000d0601 (Cavium Octeon+) 2026 Sep 11 07:36:46+00:00 wglng-8193 kernel [warning] Modules linked in: lm75 pca953x ftdi\_sio core429(P) usbnet GobiSerial GobiNet crc\_ccitt ppp\_async ppp\_mppe ecb arc4 bsd\_comp ppp\_deflate 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] Process slqssdk (pid: 14910, threadinfo=a800000003550000, task=a80000000354ceb8, tls=000000002b3a57d0) 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] Stack : ffffffff80f42590 a8000000042777c0 ffffffff85240000 a800000003484a80 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] a800000002077c20 ffffffff80100c04 0000000000000000 0000000000000001 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 2aded09ccdfbe631 0000000000000000 0000000000000000 0000000000000001 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 0000000000000000 ffffffff8523e1cf 0000000000000000 312f312d312f312d 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 312e342f312d312e 343a312e332f6570 a800000410000500 ffffffff8010605c 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] ffffffff80336450 0000000000000000 a8000000042777c0 ffffffff85240000 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] a800000003484a80 a800000002077c20 a800000004aa2850 a800000003484a80 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] a800000004aa2850 000000002b2fdbf0 0000000000000001 ffffffff80484288 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] a800000004aa2850 ffffffff80f30000 a800000003550000 a800000003553c30 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 000000002b39d040 ffffffff803a1624 0000000010008ce3 0000000000000000 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] … 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] Call Trace: 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] do\_ade+0x2b8/0x5c0 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] ret\_from\_exception+0x0/0x10 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] sysfs\_open\_file+0xa0/0x440 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] \_\_dentry\_open+0x2f4/0x448 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] do\_filp\_open+0x77c/0xc30 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] do\_sys\_open+0x7c/0x1f0 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] [] handle\_sysn32+0x44/0x84 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] 2026 Sep 11 07:36:47+00:00 wglng-8193 kernel [warning] Code: 00431024 1440fff1 00000000 \<6a630000\> 6e630007 24020000 14400034 0060982d 8e020124 2026 Sep 11 07:36:50+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:50+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(1) 2026 Sep 11 07:36:50+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:50+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(1) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(2) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(2) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(3) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] usb\_control\_msg failed (-145) 2026 Sep 11 07:36:51+00:00 wglng-8193 kernel [warning] Write URB timeout, cnt(3) ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 12, 2026, 1:32am UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/2 "2026-09-12T01:32:33Z")
Maybe you can try the latest slqssdk and gobi driver > **[Linux QMI SDK Software History | Source](https://source.sierrawireless.com/resources/airprime/software/linux-qmi-sdk-software-history#sthash.jK5GfVhE.dpbs)** > **[USB Drivers Linux QMI Software History | Source](https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-history#sthash.w2MS79jH.dpbs)** ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 18, 2026, 6:00am UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/3 "2026-09-18T06:00:18Z")
Hello, I checked the above latest driver and SDK. Unfortunately there is lot of changes with our current Gobi driver version. I have query on QMI\_CONTROL\_MSG\_DELAY\_MS in QMIDevice.h file. Can I have higher value , say 200 ms instead of 100 ms? Looks like it can affect the system during initialization as well as Run time. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 18, 2026, 6:13am UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/5 "2026-09-18T06:13:40Z")
Probably you need to make some test on your platform to verify ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 18, 2026, 4:50pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/6 "2026-09-18T16:50:14Z")
Tested with 200 ms and saw runtime kernel crash with random time. Sometime in 4 hours , some time after 1 hour. with 100 ms no issue with Runtime but failing sometime during initialization with MAX\_RETRY as 5. Probably keeping the same 100 ms for delay and increase MAX\_RETRY to 10 is a better approach? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 18, 2026, 4:59pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/7 "2026-09-18T16:59:04Z")
You can use linux command to reattach usb port [https://stackoverflow.com/questions/21580750/disconnect-and-reconnect-ttyusb0-programmatically-in-linux](https://stackoverflow.com/questions/21580750/disconnect-and-reconnect-ttyusb0-programmatically-in-linux) ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 18, 2026, 5:05pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/8 "2026-09-18T17:05:02Z")
The /dev/qcqmi end point is not creating in the failed case during initialization. If we add more delay, it get created. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 18, 2026, 5:24pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/9 "2026-09-18T17:24:23Z")
As you say, adding delay will lead to crash issue. So better to use origjnal timing Once initialization is failed, reattach the usb port by the linux command ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 18, 2026, 5:25pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/10 "2026-09-18T17:25:43Z")
> [@jyijyi](#): > > timing Thank you , will try that. ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 18, 2026, 5:28pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/11 "2026-09-18T17:28:55Z")
if initialization fails (modem detection fails) , /dev/qcqmi node is not created. Are you saying to create it /dev/qcqmi with linux command? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 18, 2026, 5:49pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/12 "2026-09-18T17:49:02Z")
I am saying to reattach usb port See below as example > [@EM7430 send AT command no response](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/21): > > ason0821 I’d suggest you to try the legacy linux generic usbserial driver. Before this, you have to unbind qcserial from your AT port, of course. I’ve tried to do this myself, just for verification. See how it works in my example: [root@yrgw ~]# lsusb Bus 001 Device 002: ID 1199:9071 Sierra Wireless, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation Bus 005 Device 001: ID 1d6b:0001 Linux Foundation Bus 004 Device 001: ID 1d6b:0001 Linux Foundation Bus 003 Device 001: ID 1d6b:0001 Linux … e.g. ```auto echo '3-2' | sudo tee /sys/bus/usb/drivers/usb/unbind echo '3-2' | sudo tee /sys/bus/usb/drivers/usb/bind ``` ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 28, 2026, 3:36pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/13 "2026-09-28T15:36:24Z")
> [@jyijyi](#): > > , reattach the usb port by the linux command Hello jyijyi, Are you saying the crash with adding 100ms more delay for CONTROLMSG\_DELAY is a know issue? Do we have any past known issue with kernel crash with increase in delay ? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 28, 2026, 4:34pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/14 "2026-09-28T16:34:36Z")
no, i don’t know if this is known issue but as you said that using 100ms has no issue in runtime, so you can use this value. ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 28, 2026, 5:53pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/15 "2026-09-28T17:53:38Z")
> [@jyijyi](#): > > this is known issue thank you. I was checking the timeout value in the latest SDK releases and it is the same as 100ms. ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 30, 2026, 2:00pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/16 "2026-09-30T14:00:18Z")
Hello, It looks like with CONTROL\_MSG\_DELAY set to 200 ms, the race condition is exposed and the memory corruption happening. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 30, 2026, 2:23pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/17 "2026-09-30T14:23:27Z")
Then it seems better to use the original 100ms ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 30, 2026, 3:43pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/18 "2026-09-30T15:43:01Z")
are you saying that if it break for 200 ms, go back to 100 ms without fixing the issue we see with 200 ms? ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 30, 2026, 3:50pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/19 "2026-09-30T15:50:11Z")
i still don’t understand why you need to change this value in the driver… ---
**Author:** ![simonkbaby](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@simonkbaby](https://forum.sierrawireless.com/u/simonkbaby)\ **Post date:** [September 30, 2026, 5:19pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/20 "2026-09-30T17:19:16Z")
> [@jyijyi](#): > > still don’t understand why you need to change this value i During bootup initialization phase, sometimes, modem was taking long time to negotiate DATA Format and control Sync messages with Driver ( Even Retry did not worked). When we changed to 200ms it is fixed but sometime we came into this Run time crash issue. Now we are putting back the 100ms Run time and adding another delay of 200 ms for all the control message needed only during initialization. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [September 30, 2026, 5:24pm UTC](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103/21 "2026-09-30T17:24:28Z")
> [@simonkbaby](#): > > Even Retry did not worked I would suggest you take the original code, if the retry does not work, just simply reattach the USB by the following commands: e.g. ```auto echo '3-2' | sudo tee /sys/bus/usb/drivers/usb/unbind echo '3-2' | sudo tee /sys/bus/usb/drivers/usb/bind ``` [Next page](https://forum.sierrawireless.com/t/query-on-kernel-crash/36103.md?page=2)