usb/net/hso: WARNING: ungligned urb->setup_dma

usb/net/hso: WARNING: ungligned urb->setup_dma

[Baruch Siach]

Hi linux-usb list,

(Dropped Jan's bouncing address, added Rpi3 platform lists)

On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> Hi linux-usb list,
> 
> I'm hitting this warning consistently on my Raspberry Pi 3 running kernel 
> v4.10.1 with some unrelated device tree changes, and a debug print (below). 
> The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
> The warning triggers consistently on first write access to /dev/ttyHS0 that 
> ModemManager attempts. The first line in the log is my debug print.

I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the 
same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be 
platform specific. I don't have any other ARM64 machine at the moment, though.

Has anyone noticed USB host issues on Raspberry Pi 3 with 64bit kernel?

baruch

> [   65.004892] dwc2_map_urb_for_dma: setup_dma: f5635066
> [   65.010718] ------------[ cut here ]------------
> [   65.016079] WARNING: CPU: 1 PID: 794 at drivers/usb/dwc2/hcd.c:2631 dwc2_map_urb_for_dma+0x94/0x130
> [   65.025930] 
> [   65.028143] CPU: 1 PID: 794 Comm: ModemManager Not tainted 4.10.1-00008-g76809ec3947f-dirty #719
> [   65.037747] Hardware name: Raspberry Pi 3 Model B (DT)
> [   65.043656] task: ffff8000362e3e80 task.stack: ffff80003556c000
> [   65.050359] PC is at dwc2_map_urb_for_dma+0x94/0x130
> [   65.056090] LR is at dwc2_map_urb_for_dma+0x34/0x130
> [   65.061819] pc : [<ffff0000083ff0ac>] lr : [<ffff0000083ff04c>] pstate: 000001c5
> [   65.070018] sp : ffff80003556fa70
> [   65.074080] x29: ffff80003556fa70 x28: 0000000000000005 
> [   65.080167] x27: ffff80003563d000 x26: ffff8000350d4600 
> [   65.086252] x25: ffff800035686780 x24: 0000000000000002 
> [   65.092247] x23: 0000000000000001 x22: 0000000001080020 
> [   65.097635] x21: ffff800035425800 x20: 0000000001080020 
> [   65.103024] x19: ffff800035b72400 x18: 0000000000000010 
> [   65.108413] x17: 0000ffff908f5a40 x16: ffff0000081abad8 
> [   65.113801] x15: 0000000000000006 x14: ffff00008882c047 
> [   65.119191] x13: ffff00000882c055 x12: ffff00000882e458 
> [   65.124579] x11: ffff80003556f7d0 x10: ffff0000087c9a38 
> [   65.129968] x9 : ffff0000083613e0 x8 : 363566203a616d64 
> [   65.135356] x7 : 5f7075746573203a x6 : 00000000000002fc 
> [   65.140744] x5 : 0000000000000000 x4 : 0000000000000000 
> [   65.146132] x3 : 0000000000000000 x2 : ffff8000362e3e80 
> [   65.151521] x1 : 0000000000000001 x0 : ffff00000880e000 
> [   65.156907] 
> [   65.158414] ---[ end trace a78d20eaecac455a ]---
> [   65.163093] Call trace:
> [   65.165573] Exception stack(0xffff80003556f8a0 to 0xffff80003556f9d0)
> [   65.172108] f8a0: ffff800035b72400 0001000000000000 ffff80003556fa70 ffff0000083ff0ac
> [   65.180052] f8c0: ffff0000086f8f70 ffff000008795000 ffff00000882dce8 ffff0000087fb318
> [   65.187996] f8e0: ffff00000882c048 000000010882bae8 ffff80003556f990 ffff0000080dc664
> [   65.195940] f900: ffff800035b72400 0000000001080020 ffff800035425800 0000000001080020
> [   65.203883] f920: 0000000000000001 0000000000000002 ffff800035686780 ffff8000350d4600
> [   65.211827] f940: ffff00000880e000 0000000000000001 ffff8000362e3e80 0000000000000000
> [   65.219771] f960: 0000000000000000 0000000000000000 00000000000002fc 5f7075746573203a
> [   65.227715] f980: 363566203a616d64 ffff0000083613e0 ffff0000087c9a38 ffff80003556f7d0
> [   65.235659] f9a0: ffff00000882e458 ffff00000882c055 ffff00008882c047 0000000000000006
> [   65.243601] f9c0: ffff0000081abad8 0000ffff908f5a40
> [   65.248548] [<ffff0000083ff0ac>] dwc2_map_urb_for_dma+0x94/0x130
> [   65.254643] [<ffff0000083e8984>] usb_hcd_submit_urb+0x8c/0x8c0
> [   65.260560] [<ffff0000083eb0b8>] usb_submit_urb+0x248/0x480
> [   65.266215] [<ffff0000083d2d2c>] mux_device_request+0xdc/0x1f8
> [   65.272134] [<ffff0000083d2e70>] hso_mux_serial_write_data+0x28/0x38
> [   65.278581] [<ffff0000083d2fa8>] hso_kick_transmit+0x88/0xb8
> [   65.284323] [<ffff0000083d4dc8>] hso_serial_write+0x60/0xc0
> [   65.289979] [<ffff000008345e80>] n_tty_write+0x300/0x3e0
> [   65.295369] [<ffff000008340a50>] tty_write+0x170/0x2b8
> [   65.300585] [<ffff0000081ab6ac>] __vfs_write+0x1c/0x100
> [   65.305884] [<ffff0000081ab92c>] vfs_write+0x9c/0x1a8
> [   65.311010] [<ffff0000081abb1c>] SyS_write+0x44/0xa0
> [   65.316049] [<ffff000008082730>] el0_svc_naked+0x24/0x28
> 
> The debug print otherwise just shows:
> 
> [   64.476785] dwc2_map_urb_for_dma: setup_dma: 00000000
> 
> So it looks like urb->setup_dma content is garbage.
> 
> Any thoughts?
> 
> Thanks,
> baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

usb/net/hso: WARNING: ungligned urb->setup_dma

[Michael Zoran]

On Tue, 2017-02-28 at 14:01 +0200, Baruch Siach wrote:
> Hi linux-usb list,
> 
> (Dropped Jan's bouncing address, added Rpi3 platform lists)
> 
> On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > Hi linux-usb list,
> > 
> > I'm hitting this warning consistently on my Raspberry Pi 3 running
> > kernel?
> > v4.10.1 with some unrelated device tree changes, and a debug print
> > (below).?
> > The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0,
> > PID: 6971.
> > The warning triggers consistently on first write access to
> > /dev/ttyHS0 that?
> > ModemManager attempts. The first line in the log is my debug print.
> 
> I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32)
> using the?
> same kernel version (4.10.1), and on an x86_64 PC (4.9). So this
> seems to be?
> platform specific. I don't have any other ARM64 machine at the
> moment, though.
> 
> Has anyone noticed USB host issues on Raspberry Pi 3 with 64bit
> kernel?
> 
> baruch
> 
> > [???65.004892] dwc2_map_urb_for_dma: setup_dma: f5635066
> > [???65.010718] ------------[ cut here ]------------
> > [???65.016079] WARNING: CPU: 1 PID: 794 at
> > drivers/usb/dwc2/hcd.c:2631 dwc2_map_urb_for_dma+0x94/0x130
> > [???65.025930]?
> > [???65.028143] CPU: 1 PID: 794 Comm: ModemManager Not tainted
> > 4.10.1-00008-g76809ec3947f-dirty #719
> > [???65.037747] Hardware name: Raspberry Pi 3 Model B (DT)
> > [???65.043656] task: ffff8000362e3e80 task.stack: ffff80003556c000
> > [???65.050359] PC is at dwc2_map_urb_for_dma+0x94/0x130
> > [???65.056090] LR is at dwc2_map_urb_for_dma+0x34/0x130
> > [???65.061819] pc : [<ffff0000083ff0ac>] lr : [<ffff0000083ff04c>]
> > pstate: 000001c5
> > [???65.070018] sp : ffff80003556fa70
> > [???65.074080] x29: ffff80003556fa70 x28: 0000000000000005?
> > [???65.080167] x27: ffff80003563d000 x26: ffff8000350d4600?
> > [???65.086252] x25: ffff800035686780 x24: 0000000000000002?
> > [???65.092247] x23: 0000000000000001 x22: 0000000001080020?
> > [???65.097635] x21: ffff800035425800 x20: 0000000001080020?
> > [???65.103024] x19: ffff800035b72400 x18: 0000000000000010?
> > [???65.108413] x17: 0000ffff908f5a40 x16: ffff0000081abad8?
> > [???65.113801] x15: 0000000000000006 x14: ffff00008882c047?
> > [???65.119191] x13: ffff00000882c055 x12: ffff00000882e458?
> > [???65.124579] x11: ffff80003556f7d0 x10: ffff0000087c9a38?
> > [???65.129968] x9 : ffff0000083613e0 x8 : 363566203a616d64?
> > [???65.135356] x7 : 5f7075746573203a x6 : 00000000000002fc?
> > [???65.140744] x5 : 0000000000000000 x4 : 0000000000000000?
> > [???65.146132] x3 : 0000000000000000 x2 : ffff8000362e3e80?
> > [???65.151521] x1 : 0000000000000001 x0 : ffff00000880e000?
> > [???65.156907]?
> > [???65.158414] ---[ end trace a78d20eaecac455a ]---
> > [???65.163093] Call trace:
> > [???65.165573] Exception stack(0xffff80003556f8a0 to
> > 0xffff80003556f9d0)
> > [???65.172108] f8a0: ffff800035b72400 0001000000000000
> > ffff80003556fa70 ffff0000083ff0ac
> > [???65.180052] f8c0: ffff0000086f8f70 ffff000008795000
> > ffff00000882dce8 ffff0000087fb318
> > [???65.187996] f8e0: ffff00000882c048 000000010882bae8
> > ffff80003556f990 ffff0000080dc664
> > [???65.195940] f900: ffff800035b72400 0000000001080020
> > ffff800035425800 0000000001080020
> > [???65.203883] f920: 0000000000000001 0000000000000002
> > ffff800035686780 ffff8000350d4600
> > [???65.211827] f940: ffff00000880e000 0000000000000001
> > ffff8000362e3e80 0000000000000000
> > [???65.219771] f960: 0000000000000000 0000000000000000
> > 00000000000002fc 5f7075746573203a
> > [???65.227715] f980: 363566203a616d64 ffff0000083613e0
> > ffff0000087c9a38 ffff80003556f7d0
> > [???65.235659] f9a0: ffff00000882e458 ffff00000882c055
> > ffff00008882c047 0000000000000006
> > [???65.243601] f9c0: ffff0000081abad8 0000ffff908f5a40
> > [???65.248548] [<ffff0000083ff0ac>] dwc2_map_urb_for_dma+0x94/0x130
> > [???65.254643] [<ffff0000083e8984>] usb_hcd_submit_urb+0x8c/0x8c0
> > [???65.260560] [<ffff0000083eb0b8>] usb_submit_urb+0x248/0x480
> > [???65.266215] [<ffff0000083d2d2c>] mux_device_request+0xdc/0x1f8
> > [???65.272134] [<ffff0000083d2e70>]
> > hso_mux_serial_write_data+0x28/0x38
> > [???65.278581] [<ffff0000083d2fa8>] hso_kick_transmit+0x88/0xb8
> > [???65.284323] [<ffff0000083d4dc8>] hso_serial_write+0x60/0xc0
> > [???65.289979] [<ffff000008345e80>] n_tty_write+0x300/0x3e0
> > [???65.295369] [<ffff000008340a50>] tty_write+0x170/0x2b8
> > [???65.300585] [<ffff0000081ab6ac>] __vfs_write+0x1c/0x100
> > [???65.305884] [<ffff0000081ab92c>] vfs_write+0x9c/0x1a8
> > [???65.311010] [<ffff0000081abb1c>] SyS_write+0x44/0xa0
> > [???65.316049] [<ffff000008082730>] el0_svc_naked+0x24/0x28
> > 
> > The debug print otherwise just shows:
> > 
> > [???64.476785] dwc2_map_urb_for_dma: setup_dma: 00000000
> > 
> > So it looks like urb->setup_dma content is garbage.
> > 
> > Any thoughts?
> > 
> > Thanks,
> > baruch
> 

I've seen similar issues twice before:

1. Back when arm64 was initially being ported to the RPI 3 by people on
the net back in March/April of last year and only the serial console
worked, DMA was broken in the dwc2 driver.  The dwc2 driver would send
and receive garbage data.  The reason was that some of the memory
manager DMA functionality for arm64 wasn't implemented yet.

2. I've also seen in complex cases things can run out of coherent DMA
pool.  If this is what is happening, which I doubt, you can try
increasing the size with the "coherent_pool=" command line option.

I don't know what the device tree changes are, but the dma-ranges in
the device tree is what determines how dma is setup on an arm64
machine.

usb/net/hso: WARNING: ungligned urb->setup_dma

[Stefan Wahren]

Hi Baruch,

Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> Hi linux-usb list,
>
> (Dropped Jan's bouncing address, added Rpi3 platform lists)
>
> On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
>> Hi linux-usb list,
>>
>> I'm hitting this warning consistently on my Raspberry Pi 3 running kernel
>> v4.10.1 with some unrelated device tree changes, and a debug print (below).
>> The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
>> The warning triggers consistently on first write access to /dev/ttyHS0 that
>> ModemManager attempts. The first line in the log is my debug print.
> I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the
> same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be
> platform specific. I don't have any other ARM64 machine at the moment, though.

those platforms usually doesn't use the dwc2 USB host controller. So it 
should be tested with another dwc2 platform.

Is the issue reproducible with other USB devices like keyboards?
Are you using arm64 defconfig?
Are you able to bisect this issue?

Stefan

usb/net/hso: WARNING: ungligned urb->setup_dma

[Baruch Siach]

Hi Stefan,

On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
> Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> > On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > > I'm hitting this warning consistently on my Raspberry Pi 3 running 
> > > kernel
> > > v4.10.1 with some unrelated device tree changes, and a debug print (below).
> > > The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
> > > The warning triggers consistently on first write access to /dev/ttyHS0 that
> > > ModemManager attempts. The first line in the log is my debug print.
> > I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the
> > same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be
> > platform specific. I don't have any other ARM64 machine at the moment, though.
> 
> those platforms usually doesn't use the dwc2 USB host controller. So it
> should be tested with another dwc2 platform.

The code that initializes setup_dma is not under drivers/usb/dwc2/. Though the 
problem looks like memory corruption, so its cause might be anywhere.

> Is the issue reproducible with other USB devices like keyboards?

Other USB devices, including a different cellular USB dongle, do not exhibit 
the same problem.

> Are you using arm64 defconfig?

I'm using that attached arm64 defconfig.

> Are you able to bisect this issue?

I don't have any previously working point.

Thanks,
baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
-------------- next part --------------
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_AUDIT=y
CONFIG_NO_HZ_IDLE=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_USER_NS=y
CONFIG_SCHED_AUTOGROUP=y
CONFIG_BLK_DEV_INITRD=y
# CONFIG_RD_BZIP2 is not set
# CONFIG_RD_LZMA is not set
# CONFIG_RD_XZ is not set
# CONFIG_RD_LZO is not set
# CONFIG_RD_LZ4 is not set
CONFIG_KALLSYMS_ALL=y
# CONFIG_COMPAT_BRK is not set
CONFIG_PROFILING=y
CONFIG_JUMP_LABEL=y
CONFIG_BLK_DEV_INTEGRITY=y
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_ARCH_BCM2835=y
CONFIG_ARM64_VA_BITS_48=y
CONFIG_SCHED_MC=y
CONFIG_HOTPLUG_CPU=y
CONFIG_PREEMPT=y
CONFIG_KSM=y
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_CMA=y
CONFIG_SECCOMP=y
CONFIG_CMDLINE="root=/dev/mmcblk0p2 rootwait console=ttyS0,115200"
CONFIG_CMDLINE_FORCE=y
# CONFIG_EFI is not set
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_COMPAT=y
# CONFIG_SUSPEND is not set
CONFIG_PM=y
CONFIG_CPU_IDLE=y
CONFIG_ARM_CPUIDLE=y
CONFIG_CPU_FREQ=y
CONFIG_CPUFREQ_DT=y
CONFIG_ARM_BIG_LITTLE_CPUFREQ=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_NETFILTER=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=y
CONFIG_NETFILTER_XT_TARGET_LOG=y
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_MANGLE=y
CONFIG_NF_CONNTRACK_IPV6=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_FILTER=y
CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP6_NF_MANGLE=y
CONFIG_IP6_NF_NAT=y
CONFIG_IP6_NF_TARGET_MASQUERADE=y
CONFIG_BRIDGE=y
CONFIG_BRIDGE_VLAN_FILTERING=y
CONFIG_VLAN_8021Q=y
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_VLAN_8021Q_MVRP=y
CONFIG_BT=y
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
# CONFIG_BT_HS is not set
CONFIG_BT_LEDS=y
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_BCM=y
CONFIG_RFKILL=y
CONFIG_RFKILL_REGULATOR=y
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_DMA_CMA=y
CONFIG_VEXPRESS_CONFIG=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_SRAM=y
# CONFIG_VEXPRESS_SYSCFG is not set
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_SAS_LIBSAS=y
# CONFIG_SCSI_LOWLEVEL is not set
CONFIG_NETDEVICES=y
CONFIG_TUN=y
CONFIG_VETH=y
# CONFIG_ETHERNET is not set
CONFIG_PPP=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_ASYNC=y
CONFIG_USB_USBNET=y
# CONFIG_USB_NET_AX8817X is not set
# CONFIG_USB_NET_AX88179_178A is not set
CONFIG_USB_NET_HUAWEI_CDC_NCM=y
CONFIG_USB_NET_CDC_MBIM=y
CONFIG_USB_NET_SMSC95XX=y
# CONFIG_USB_NET_NET1080 is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
# CONFIG_USB_NET_ZAURUS is not set
CONFIG_USB_HSO=y
# CONFIG_WLAN is not set
CONFIG_INPUT_EVDEV=y
CONFIG_KEYBOARD_GPIO=y
CONFIG_INPUT_MISC=y
# CONFIG_SERIO_SERPORT is not set
CONFIG_SERIO_AMBAKMI=y
CONFIG_LEGACY_PTY_COUNT=16
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_BCM2835AUX=y
CONFIG_SERIAL_8250_DW=y
CONFIG_SERIAL_OF_PLATFORM=y
CONFIG_SERIAL_AMBA_PL011=y
CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
CONFIG_SERIAL_XILINX_PS_UART=y
CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y
CONFIG_I2C_BCM2835=y
CONFIG_SPI=y
CONFIG_SPI_BCM2835=y
CONFIG_SPI_BCM2835AUX=y
CONFIG_PPS=y
CONFIG_PINCTRL_SINGLE=y
CONFIG_GPIO_GENERIC_PLATFORM=y
CONFIG_POWER_RESET_GPIO=y
# CONFIG_HWMON is not set
CONFIG_WATCHDOG=y
CONFIG_BCM2835_WDT=y
CONFIG_MFD_RK808=y
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_VEXPRESS_SYSREG is not set
CONFIG_REGULATOR=y
CONFIG_REGULATOR_FIXED_VOLTAGE=y
CONFIG_REGULATOR_GPIO=y
CONFIG_REGULATOR_PWM=y
CONFIG_REGULATOR_RK808=y
CONFIG_FB=y
CONFIG_FB_ARMCLCD=y
# CONFIG_LCD_CLASS_DEVICE is not set
# CONFIG_BACKLIGHT_GENERIC is not set
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_HID_GENERIC is not set
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_USB_HID is not set
CONFIG_USB=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_STORAGE=y
CONFIG_USB_DWC2=y
CONFIG_USB_ULPI=y
CONFIG_MMC=y
# CONFIG_PWRSEQ_SIMPLE is not set
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_PLTFM=y
CONFIG_MMC_SDHCI_IPROC=y
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
CONFIG_LEDS_GPIO=y
CONFIG_LEDS_SYSCON=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_CPU=y
CONFIG_DMADEVICES=y
CONFIG_DMA_BCM2835=y
CONFIG_SYNC_FILE=y
# CONFIG_COMMON_CLK_XGENE is not set
# CONFIG_FSL_ERRATUM_A008585 is not set
CONFIG_MAILBOX=y
CONFIG_BCM2835_MBOX=y
# CONFIG_IOMMU_SUPPORT is not set
CONFIG_RASPBERRYPI_POWER=y
CONFIG_PWM=y
CONFIG_PWM_BCM2835=y
CONFIG_RASPBERRYPI_FIRMWARE=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_DNOTIFY is not set
CONFIG_FANOTIFY=y
CONFIG_QUOTA=y
CONFIG_VFAT_FS=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_CONFIGFS_FS=y
# CONFIG_MISC_FILESYSTEMS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_FS=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOCKUP_DETECTOR=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_FTRACE is not set
CONFIG_MEMTEST=y
CONFIG_CRYPTO_AUTHENC=y
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_ANSI_CPRNG=y
CONFIG_ARM64_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM64_CE=y
CONFIG_CRYPTO_SHA2_ARM64_CE=y
CONFIG_CRYPTO_GHASH_ARM64_CE=y
CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
CONFIG_CRYPTO_CRC32_ARM64=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC7=y

usb/net/hso: WARNING: ungligned urb->setup_dma

[Stefan Wahren]

Hi Baruch,

> Baruch Siach <baruch@tkos.co.il> hat am 28. Februar 2017 um 19:07 geschrieben:
> 
> 
> Hi Stefan,
> 
> On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
> > Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> > > On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > > > I'm hitting this warning consistently on my Raspberry Pi 3 running 
> > > > kernel
> > > > v4.10.1 with some unrelated device tree changes, and a debug print (below).
> > > > The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
> > > > The warning triggers consistently on first write access to /dev/ttyHS0 that
> > > > ModemManager attempts. The first line in the log is my debug print.
> > > I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the
> > > same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be
> > > platform specific. I don't have any other ARM64 machine at the moment, though.
> > 
> > those platforms usually doesn't use the dwc2 USB host controller. So it
> > should be tested with another dwc2 platform.
> 
> The code that initializes setup_dma is not under drivers/usb/dwc2/. Though the 
> problem looks like memory corruption, so its cause might be anywhere.

only a suspicion, but could you please try this patch [1]?

[1] - https://patchwork.kernel.org/patch/9166771/

usb/net/hso: WARNING: ungligned urb->setup_dma

[Baruch Siach]

Hi Stefan,

On Tue, Feb 28, 2017 at 07:32:09PM +0100, Stefan Wahren wrote: 
> > Baruch Siach <baruch@tkos.co.il> hat am 28. Februar 2017 um 19:07 geschrieben:
> > On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
> > > Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> > > > On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > > > > I'm hitting this warning consistently on my Raspberry Pi 3 running 
> > > > > kernel
> > > > > v4.10.1 with some unrelated device tree changes, and a debug print (below).
> > > > > The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
> > > > > The warning triggers consistently on first write access to /dev/ttyHS0 that
> > > > > ModemManager attempts. The first line in the log is my debug print.
> > > > I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the
> > > > same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be
> > > > platform specific. I don't have any other ARM64 machine at the moment, though.
> > > 
> > > those platforms usually doesn't use the dwc2 USB host controller. So it
> > > should be tested with another dwc2 platform.
> > 
> > The code that initializes setup_dma is not under drivers/usb/dwc2/. Though the 
> > problem looks like memory corruption, so its cause might be anywhere.
> 
> only a suspicion, but could you please try this patch [1]?
> 
> [1] - https://patchwork.kernel.org/patch/9166771/

It doesn't change anything.

My guess is that source of the issue is memory corruption that just happens to 
corrupt also the setup_dma field of struct urb. In other words, it has nothing 
to do with DMA, IMO.

Thanks,
baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

usb/net/hso: WARNING: ungligned urb->setup_dma

[Stefan Wahren]

Hi Baruch,

Am 01.03.2017 um 11:54 schrieb Baruch Siach:
> Hi Stefan,
>
> On Tue, Feb 28, 2017 at 07:32:09PM +0100, Stefan Wahren wrote: 
>>> Baruch Siach <baruch@tkos.co.il> hat am 28. Februar 2017 um 19:07 geschrieben:
>>> On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
>>>> Am 28.02.2017 um 13:01 schrieb Baruch Siach:
>>>>> On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
>>>>>> I'm hitting this warning consistently on my Raspberry Pi 3 running 
>>>>>> kernel
>>>>>> v4.10.1 with some unrelated device tree changes, and a debug print (below).
>>>>>> The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
>>>>>> The warning triggers consistently on first write access to /dev/ttyHS0 that
>>>>>> ModemManager attempts. The first line in the log is my debug print.
>>>>> I tested the same hardware successfully on an i.MX6 CuBox-i (ARM32) using the
>>>>> same kernel version (4.10.1), and on an x86_64 PC (4.9). So this seems to be
>>>>> platform specific. I don't have any other ARM64 machine at the moment, though.
>>>> those platforms usually doesn't use the dwc2 USB host controller. So it
>>>> should be tested with another dwc2 platform.
>>> The code that initializes setup_dma is not under drivers/usb/dwc2/. Though the 
>>> problem looks like memory corruption, so its cause might be anywhere.
>> only a suspicion, but could you please try this patch [1]?
>>
>> [1] - https://patchwork.kernel.org/patch/9166771/
> It doesn't change anything.
>
> My guess is that source of the issue is memory corruption that just happens to 
> corrupt also the setup_dma field of struct urb. In other words, it has nothing 
> to do with DMA, IMO.

may you could use

CONFIG_DMA_API_DEBUG

or

CONFIG_SLUB_DEBUG

in order to find the source?

>
> Thanks,
> baruch
>