linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, rydberg@bitmath.org,
	andriy.shevchenko@linux.intel.com, m.felsch@pengutronix.de,
	robh@kernel.org, mylene.josserand@bootlin.com,
	p.zabel@pengutronix.de
Subject: Re: RFC: Input: edt-ft5x06 - FT6336G Touch Panel
Date: Mon, 16 Mar 2020 15:57:36 +0100	[thread overview]
Message-ID: <20200316145736.GG16310@optiplex> (raw)
In-Reply-To: <20200305163649.GC10366@ripley>

On 02/03/20, Oliver Graute wrote:
> Hello,
> 
> I have on of these FT6336G Touch Panels here and I try to get it work
> with the ft6236 driver. It comes up with model identification "0x11". So
> I added that identification to the switch case in
> edt_ft5x06_ts_identify(). But it crashes directly after the probe with a
> corrupted stack. No clue why. Some ideas?

I still observe sometimes crashes with ft6236G. When it occurs it is
always a stack corruption in the probe function on bootup.

No clue why stack is corrupted sometimes. Is this related to the buggy
revision field?

Some further suggestions for debugging this?

[    3.806780] edt_ft5x06 1-0038: Model "EP0110M09", Rev. "�", 0x0 sensors
[    3.808468] at24 2-0050: 2-0050 supply vcc not found, using dummy regulator
[    3.814864] DEBUG: edt_ft5x06_ts_probe 1201
[    3.826215] DEBUG: edt_ft5x06_ts_probe 1211
[    3.830512] DEBUG: edt_ft5x06_ts_probe 1214
[    3.834904] input: EP0110M09 as /devices/platform/bus@5a000000/5a820000.i2c/i2c-1/1-0038/input/input0
[    3.844164] at24 2-0050: 4096 byte 24c32 EEPROM, writable, 1 bytes/write
[    3.844264] DEBUG: edt_ft5x06_ts_probe 1222
[    3.850919] i2c i2c-2: LPI2C adapter registered
[    3.855187] edt_ft5x06 1-0038: EDT FT5x06 initialized: IRQ 55, WAKE pin -1, Reset pin -1.
[    3.867878] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: edt_ft5x06_ts_probe+0x5c4/0xb00
[    3.878579] CPU: 4 PID: 115 Comm: kworker/u10:2 Not tainted 5.6.0-rc1-next-20200214-00057-g9e78f1560095-dirty #99
[    3.888838] Hardware name: Advantech iMX8QM DMSSE20 (DT)
[    3.894153] Workqueue: events_unbound async_run_entry_fn
[    3.899465] Call trace:
[    3.901909]  dump_backtrace+0x0/0x1c0
[    3.905571]  show_stack+0x14/0x20
[    3.908884]  dump_stack+0xb4/0xfc
[    3.912202]  panic+0x158/0x320
[    3.914929] mmc0: SDHCI controller on 5b010000.mmc [5b010000.mmc] using ADMA
[    3.915254]  print_tainted+0x0/0xa8
[    3.915262]  edt_ft5x06_ts_probe+0x5c4/0xb00
[    3.930063]  i2c_device_probe+0x2d0/0x2f8
[    3.934074]  really_probe+0xd8/0x438
[    3.935270] sdhci-esdhc-imx 5b030000.mmc: Got CD GPIO
[    3.937642]  driver_probe_device+0xdc/0x130
[    3.937648]  __device_attach_driver+0x88/0x108
[    3.942717] sdhci-esdhc-imx 5b030000.mmc: Got WP GPIO
[    3.946872]  bus_for_each_drv+0x74/0xc0
[    3.946875]  __device_attach_async_helper+0xb4/0x100
[    3.946877]  async_run_entry_fn+0x40/0x1a0
[    3.946883]  process_one_work+0x19c/0x320
[    3.973252]  worker_thread+0x48/0x420
[    3.976913]  kthread+0xf0/0x120
[    3.980051]  ret_from_fork+0x10/0x18
[    3.983634] SMP: stopping secondary CPUs
[    3.987558] Kernel Offset: disabled
[    3.991048] CPU features: 0x10002,2100600c
[    3.995148] Memory Limit: none
[    3.998201] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: edt_ft5x06_ts_probe+0x5c4/0xb00 ]---

Best Regards,

Oliver

  reply	other threads:[~2020-03-16 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 14:30 RFC: Input: edt-ft5x06 - FT6336G Touch Panel Oliver Graute
2020-03-02 15:00 ` Andy Shevchenko
2020-03-02 17:15   ` Oliver Graute
2020-03-02 18:43     ` Marco Felsch
2020-03-03 19:37       ` Oliver Graute
2020-03-04  7:10         ` Marco Felsch
2020-03-05 16:36           ` Oliver Graute
2020-03-16 14:57             ` Oliver Graute [this message]
2020-03-16 16:30               ` Andy Shevchenko
2020-03-16 20:01                 ` Marco Felsch
2020-03-17 16:57                   ` Oliver Graute
2020-03-17 17:40                     ` Andy Shevchenko

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=20200316145736.GG16310@optiplex \
    --to=oliver.graute@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mylene.josserand@bootlin.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=rydberg@bitmath.org \
    /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).