From: Oliver Neukum <oneukum@suse.com>
To: wim@djo.tudelft.nl
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: crash by cdc_acm driver in kernels 4.8-rc1/5
Date: Thu, 08 Sep 2016 15:05:15 +0200 [thread overview]
Message-ID: <1473339915.32073.3.camel@suse.com> (raw)
In-Reply-To: <20160908125850.GC28274@djo.tudelft.nl>
On Thu, 2016-09-08 at 14:58 +0200, Wim Osterholt wrote:
> On Thu, Sep 08, 2016 at 02:20:38PM +0200, Oliver Neukum wrote:
> > >
> > > The oops tells things that I didn't all write down, but it says
> > > null pointer dereference at 00000246
> >
> > That is the important part. I am sorry, but without the oops
> > nobody can help you. Please capture it
>
> Sep 6 19:12:37 localhost kernel: usb 7-1: new full-speed USB device number 2 using uhci_hcd
> Sep 6 19:12:37 localhost kernel: usb 7-1: New USB device found, idVendor=0572, idProduct=1340
> Sep 6 19:12:37 localhost kernel: usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> Sep 6 19:12:37 localhost kernel: usb 7-1: Product: USB Modem
> Sep 6 19:12:37 localhost kernel: usb 7-1: Manufacturer: Conexant
> Sep 6 19:12:37 localhost kernel: usb 7-1: SerialNumber: 12345678
> Sep 6 19:12:38 localhost mtp-probe[13126]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.3/usb7/7-1"
> Sep 6 19:12:38 localhost mtp-probe[13126]: bus: 7, device: 2 was not an MTP device
> Sep 6 19:12:38 localhost kernel: BUG: unable to handle kernel NULL pointer dereference at 00000246
> Sep 6 19:12:38 localhost kernel: IP: [<e0a81a35>] 0xe0a81a35
> Sep 6 19:12:38 localhost kernel: *pde = 00000000
> Sep 6 19:12:38 localhost kernel: Oops: 0000 [#1] SMP
> Sep 6 19:12:38 localhost kernel: Modules linked in: cdc_acm(+) nouveau video drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm agpgart i2c_algo_bit lirc_serial(C) lirc_dev(O) cfg80211 rfkill binfmt_misc svgalib_helper(O) snd_pcm_oss snd_mixer_oss fbcon bitblit softcursor font tileblit sr9700 dm9601 usbnet usb_storage mii snd_hda_codec_generic tg3 snd_hda_intel snd_hda_codec ptp snd_hwdep pps_core gpio_ich snd_hda_core libphy ppdev firmware_class uhci_hcd pcspkr snd_pcm ohci_pci ohci_hcd lpc_ich ehci_pci snd_timer ehci_hcd mfd_core snd usbcore floppy soundcore wmi parport_pc usb_common parport acpi_cpufreq processor button
> Sep 6 19:12:38 localhost kernel: CPU: 0 PID: 13127 Comm: udevd Tainted: G C O 4.8.0-rc5 #1
> Sep 6 19:12:38 localhost kernel: Hardware name: Hewlett-Packard HP xw4300 Workstation/0A00h, BIOS 786D3 v01.08 03/10/2006
> Sep 6 19:12:38 localhost kernel: task: df639c00 task.stack: df4d6000
> Sep 6 19:12:38 localhost kernel: EIP: 0060:[<e0a81a35>] EFLAGS: 00010202 CPU: 0
> Sep 6 19:12:38 localhost kernel: EAX: 00000000 EBX: def22000 ECX: 00000000 EDX: 00000124
> Sep 6 19:12:38 localhost kernel: ESI: def2227c EDI: dee04000 EBP: 00000246 ESP: df4d7ce8
> Sep 6 19:12:38 localhost kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> Sep 6 19:12:38 localhost kernel: CR0: 80050033 CR2: 00000246 CR3: 19b4d000 CR4: 00000690
> Sep 6 19:12:38 localhost kernel: Stack:
> Sep 6 19:12:38 localhost kernel: dee8ba00 dee8ba00 dee8b400 dee04000 df4b6380 df4b63b8 00000001 dee04070
> Sep 6 19:12:38 localhost kernel: daca2ec0 dee8ba1c 00000040 00000010 00000000 def2200c def2227c 00000000
> Sep 6 19:12:38 localhost kernel: dee20800 00000000 df639c00 dcdc37e0 c01f4347 00000246 00000246 dcdc37e0
> Sep 6 19:12:38 localhost kernel: Call Trace:
> Sep 6 19:12:38 localhost kernel: [<c01f4347>] ? 0xc01f4347
Hi,
your stack trace is broken. Did you fail to install the System.map file?
Regards
Oliver
next prev parent reply other threads:[~2016-09-08 13:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 11:58 crash by cdc_acm driver in kernels 4.8-rc1/5 Wim Osterholt
2016-09-08 12:20 ` Oliver Neukum
2016-09-08 12:58 ` Wim Osterholt
2016-09-08 13:05 ` Oliver Neukum [this message]
2016-09-08 15:00 ` Wim Osterholt
2016-09-08 16:54 ` Wim Osterholt
2016-09-09 13:24 ` Wim Osterholt
2016-09-12 2:43 ` Wim Osterholt
2016-09-20 13:05 ` Oliver Neukum
2016-09-20 15:45 ` Wim Osterholt
2016-09-21 12:21 ` Oliver Neukum
2016-09-21 16:21 ` Wim Osterholt
2016-09-21 16:41 ` Wim Osterholt
2016-09-22 14:40 ` Oliver Neukum
2016-09-22 17:56 ` Wim Osterholt
2016-09-22 19:21 ` Wim Osterholt
2016-09-23 10:04 ` Wim Osterholt
2016-09-27 16:34 ` Wim Osterholt
2016-09-28 9:16 ` Oliver Neukum
2016-09-28 14:46 ` Wim Osterholt
2016-09-28 15:08 ` Wim Osterholt
2016-09-28 15:23 ` Oliver Neukum
2016-09-29 13:26 ` Wim Osterholt
2016-10-06 10:53 ` Oliver Neukum
2016-10-17 14:10 ` Oliver Neukum
2016-10-17 15:20 ` Wim Osterholt
2016-10-18 12:18 ` Oliver Neukum
2016-10-18 14:51 ` Wim Osterholt
2016-11-05 13:34 ` Wim Osterholt
2016-11-15 0:16 ` Wim Osterholt
2016-11-15 11:07 ` Oliver Neukum
2016-11-15 11:26 ` poma
2016-11-15 13:29 ` Wim Osterholt
2016-11-16 12:34 ` Oliver Neukum
2016-11-16 15:07 ` Wim Osterholt
2016-11-17 1:57 ` Wim Osterholt
2016-11-17 9:14 ` Wim Osterholt
2016-11-17 16:11 ` Wim Osterholt
2016-11-21 13:19 ` Oliver Neukum
2016-11-21 15:58 ` Wim Osterholt
2016-11-21 20:23 ` Wim Osterholt
2016-11-21 23:49 ` poma
2016-11-22 17:50 ` Bjørn Mork
2016-11-23 0:48 ` Wim Osterholt
2016-11-22 15:38 ` Wim Osterholt
2016-11-22 18:08 ` Bjørn Mork
2016-11-23 0:54 ` Wim Osterholt
2016-11-23 7:37 ` Bjørn Mork
2016-11-23 15:02 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473339915.32073.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wim@djo.tudelft.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).