From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7F2DC43215 for ; Wed, 20 Nov 2019 13:31:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9C0D822520 for ; Wed, 20 Nov 2019 13:31:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="CsLTwXt2"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="FxfxZw/L" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730619AbfKTNb4 (ORCPT ); Wed, 20 Nov 2019 08:31:56 -0500 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:49451 "EHLO wout3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730607AbfKTNb4 (ORCPT ); Wed, 20 Nov 2019 08:31:56 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 3183A550; Wed, 20 Nov 2019 08:31:55 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 20 Nov 2019 08:31:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=kGoU8+LPVS69PgWlnUceaK0UkbL eHqqCU710XidawNk=; b=CsLTwXt2RImR2jJWOXBlLjqrDBixx8faeND8kOJO2NX OpBuddtKU5q7Z5bkTDDE+xjbz83WOwDSJTrYk7spNz9LUJy22N96qoaeg49Ww3zg 6uN1qyJqeyw64yquUlHcTzt2vlO1r+gCXr8VvaXxYkWRGrkmWN0sVYdbe84gQNVI YMiVvj6ia94mjPBV6KBJ6FM6kjnWQ9cBb+DKQCAetgNjyPR4j9CzM0/rWEVfINcN T6lzWK4XoLssEjRyRczxJLVXUnmTUFcLklVg0LDU8P5SeS1NfkWUF/a6NsQRbctS JmZEXHriXCQZGyUL1XX7WN/JqRio4wKo1spBsBnce7g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=kGoU8+ LPVS69PgWlnUceaK0UkbLeHqqCU710XidawNk=; b=FxfxZw/LcvcTiBi4xZ2BDC rWNtClG62C2Mgxx3ATXGL+BvnU11dyQDsk3H9SYLrtOjSBmAP55LGAnjZUwe7yne ejnZdQqiMfPwuCY6MidNaAKkzynVQyDW6TRWWZZZXoOuJoXEhimbYl+I6HPKIyKD dEhbO7N+BvfrlEqcMtMoED769OMcg/fhs3WJw2E9myT7ZPYXZH1FgZdPOQUWCxvh Bv/Ui/DrJ6kit4Xa/sWAA3iIlM60xaQ7AoYgUlfcaxqTDch3yR1Xr7xVobfJz0uH Oqc7ivyTEP+3paRRJqilKzqV9AEakmiPIedDjDHQQ79UqqiIxKxSNZvie4zS5/Sw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehtddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttd ertddtredvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhm qeenucfkphepkeefrdekiedrkeelrddutdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hgrhgvgheskhhrohgrhhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 6D4F93060062; Wed, 20 Nov 2019 08:31:54 -0500 (EST) Date: Wed, 20 Nov 2019 14:31:52 +0100 From: Greg KH To: JH Cc: linux-usb Subject: Re: kernel: Alignment trap Message-ID: <20191120133152.GB2892197@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Wed, Nov 20, 2019 at 09:28:14PM +1100, JH wrote: > Hi, > > I am running 4G LTE (USB protocol) and WiFi on IMX6 board, the kernel > is 4.19.75 LTE. It is not clear where the kernel alignment trap came > from, the only thing I could see is the alignment trap message > generated immediate after USB GSM communication or mwifiex_sdio. Where > that the alignment trap came from? Which parts of the program could > contribute the kernel alignment trap, kernel iteself, or USB GSM or > mwifiex_sdio? Appreciate clues how to fix it. > > Nov 20 05:08:09 solar kernel: usb 1-1: GSM modem (1-port) converter > now attached to ttyUSB0 > Nov 20 05:08:09 solar kernel: option 1-1:1.2: GSM modem (1-port) > converter detected > Nov 20 05:08:09 solar kernel: usb 1-1: GSM modem (1-port) converter > now attached to ttyUSB1 > Nov 20 05:08:10 solar kernel: mwifiex_sdio mmc0:0001:1: info: trying > to associate to 'Solar Analytics Wifi' bssid 78:8a:20:49:4b:c5 > Nov 20 05:08:10 solar kernel: mwifiex_sdio mmc0:0001:1: info: > associated to bssid 78:8a:20:49:4b:c5 successfully > Nov 20 05:08:10 solar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: > link becomes ready > Nov 20 05:23:13 solar kernel: mwifiex_sdio mmc0:0001:1: info: > successfully disconnected from 78:8a:20:49:4b:c5: reason code 3 > Nov 20 05:23:13 solar kernel: IPv6: ADDRCONF(NETDEV_UP): mlan0: link > is not ready > Nov 20 05:23:18 solar kernel: Alignment trap: not handling instruction > e8532f00 at [] > Nov 20 05:23:18 solar kernel: Unhandled fault: alignment exception > (0x001) at 0x38626667 > Nov 20 05:23:18 solar kernel: pgd = 34bdb7e7 > Nov 20 05:23:18 solar kernel: [38626667] *pgd=00000000 You should have a much longer tracedump after this, right? Can you provide that please? And why do you think this was a USB issue? thanks, greg k-h