Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 11:12:24 +0200 Ladislav Michl wrote: > On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: > > On Wed, 11 Apr 2018 10:27:46 +0200 > > Ladislav Michl wrote: > > > > > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 11:12:24 +0200 Ladislav Michl wrote: > On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: > > On Wed, 11 Apr 2018 10:27:46 +0200 > > Ladislav Michl wrote: > > > > > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > > > > On Wed, 11 Apr

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Tony, > Am 12.04.2018 um 17:03 schrieb Tony Lindgren : > > * H. Nikolaus Schaller [180411 07:05]: >>> Am 10.04.2018 um 22:56 schrieb Ladislav Michl : >>> Well, that's a shame... However, this code is in production for several >>>

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Tony, > Am 12.04.2018 um 17:03 schrieb Tony Lindgren : > > * H. Nikolaus Schaller [180411 07:05]: >>> Am 10.04.2018 um 22:56 schrieb Ladislav Michl : >>> Well, that's a shame... However, this code is in production for several >>> months now, >> >> Well, we could have tested earlier

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

* H. Nikolaus Schaller [180411 07:05]: > > Am 10.04.2018 um 22:56 schrieb Ladislav Michl : > > Well, that's a shame... However, this code is in production for several > > months now, > > Well, we could have tested earlier release-candidates... I've

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

* H. Nikolaus Schaller [180411 07:05]: > > Am 10.04.2018 um 22:56 schrieb Ladislav Michl : > > Well, that's a shame... However, this code is in production for several > > months now, > > Well, we could have tested earlier release-candidates... I've found it's way easier to test Linux next on

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

> Am 11.04.2018 um 11:12 schrieb Ladislav Michl : > > On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: >> On Wed, 11 Apr 2018 10:27:46 +0200 >> Ladislav Michl wrote: >> >>> On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

> Am 11.04.2018 um 11:12 schrieb Ladislav Michl : > > On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: >> On Wed, 11 Apr 2018 10:27:46 +0200 >> Ladislav Michl wrote: >> >>> On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: On Wed, 11 Apr 2018 09:36:56 +0200

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: > On Wed, 11 Apr 2018 10:27:46 +0200 > Ladislav Michl wrote: > > > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > > > On Wed, 11 Apr 2018 09:36:56 +0200 > > > Ladislav Michl

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, Apr 11, 2018 at 10:52:01AM +0200, Boris Brezillon wrote: > On Wed, 11 Apr 2018 10:27:46 +0200 > Ladislav Michl wrote: > > > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > > > On Wed, 11 Apr 2018 09:36:56 +0200 > > > Ladislav Michl wrote: > > > > > > > Hi Boris, >

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 10:27:46 +0200 Ladislav Michl wrote: > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > > On Wed, 11 Apr 2018 09:36:56 +0200 > > Ladislav Michl wrote: > > > > > Hi Boris, > > > > > > On Wed, Apr 11, 2018 at

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 10:27:46 +0200 Ladislav Michl wrote: > On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > > On Wed, 11 Apr 2018 09:36:56 +0200 > > Ladislav Michl wrote: > > > > > Hi Boris, > > > > > > On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: >

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > On Wed, 11 Apr 2018 09:36:56 +0200 > Ladislav Michl wrote: > > > Hi Boris, > > > > On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: [...] > > > Not sure this approach is safe on all archs:

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, Apr 11, 2018 at 10:08:06AM +0200, Boris Brezillon wrote: > On Wed, 11 Apr 2018 09:36:56 +0200 > Ladislav Michl wrote: > > > Hi Boris, > > > > On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: [...] > > > Not sure this approach is safe on all archs: if the cache is VIVT or

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 09:36:56 +0200 Ladislav Michl wrote: > Hi Boris, > > On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: > > Hi Ladislav, > > > > On Wed, 11 Apr 2018 08:26:07 +0200 > > Ladislav Michl wrote: > > > > > Hi Andreas,

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

On Wed, 11 Apr 2018 09:36:56 +0200 Ladislav Michl wrote: > Hi Boris, > > On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: > > Hi Ladislav, > > > > On Wed, 11 Apr 2018 08:26:07 +0200 > > Ladislav Michl wrote: > > > > > Hi Andreas, > > > > > > On Wed, Apr 11, 2018 at

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Boris, On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: > Hi Ladislav, > > On Wed, 11 Apr 2018 08:26:07 +0200 > Ladislav Michl wrote: > > > Hi Andreas, > > > > On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > > > Hi Ladis, > > > > >

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Boris, On Wed, Apr 11, 2018 at 09:15:28AM +0200, Boris Brezillon wrote: > Hi Ladislav, > > On Wed, 11 Apr 2018 08:26:07 +0200 > Ladislav Michl wrote: > > > Hi Andreas, > > > > On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > > > Hi Ladis, > > > > > > On Tue, 10 Apr 2018

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladislav, On Wed, 11 Apr 2018 08:26:07 +0200 Ladislav Michl wrote: > Hi Andreas, > > On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > > Hi Ladis, > > > > On Tue, 10 Apr 2018 22:56:43 +0200 > > Ladislav Michl wrote: > > > > >

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladislav, On Wed, 11 Apr 2018 08:26:07 +0200 Ladislav Michl wrote: > Hi Andreas, > > On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > > Hi Ladis, > > > > On Tue, 10 Apr 2018 22:56:43 +0200 > > Ladislav Michl wrote: > > > > > Hi Nikolaus, > > > > > > On Tue, Apr 10,

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladislav, > Am 10.04.2018 um 22:56 schrieb Ladislav Michl : > > Hi Nikolaus, > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: >> Hi, >> we just started testing the v4.16 kernel and found the >> device no longer bootable (works with v4.15). It

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladislav, > Am 10.04.2018 um 22:56 schrieb Ladislav Michl : > > Hi Nikolaus, > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: >> Hi, >> we just started testing the v4.16 kernel and found the >> device no longer bootable (works with v4.15). It turned >> out that there

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Andreas, On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > Hi Ladis, > > On Tue, 10 Apr 2018 22:56:43 +0200 > Ladislav Michl wrote: > > > Hi Nikolaus, > > > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > > > Hi, > > > we

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Andreas, On Wed, Apr 11, 2018 at 06:59:03AM +0200, Andreas Kemnade wrote: > Hi Ladis, > > On Tue, 10 Apr 2018 22:56:43 +0200 > Ladislav Michl wrote: > > > Hi Nikolaus, > > > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > > > Hi, > > > we just started testing the

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladis, On Tue, 10 Apr 2018 22:56:43 +0200 Ladislav Michl wrote: > Hi Nikolaus, > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > > Hi, > > we just started testing the v4.16 kernel and found the > > device no longer bootable (works with v4.15).

Re: [Letux-kernel] [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Ladis, On Tue, 10 Apr 2018 22:56:43 +0200 Ladislav Michl wrote: > Hi Nikolaus, > > On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > > Hi, > > we just started testing the v4.16 kernel and found the > > device no longer bootable (works with v4.15). It turned > > out

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Nikolaus, On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > Hi, > we just started testing the v4.16 kernel and found the > device no longer bootable (works with v4.15). It turned > out that there was a harmful modification somewhere between > v4.15.0 and v4.16-rc1. > > A

Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi Nikolaus, On Tue, Apr 10, 2018 at 06:25:17PM +0200, H. Nikolaus Schaller wrote: > Hi, > we just started testing the v4.16 kernel and found the > device no longer bootable (works with v4.15). It turned > out that there was a harmful modification somewhere between > v4.15.0 and v4.16-rc1. > > A

[Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi, we just started testing the v4.16 kernel and found the device no longer bootable (works with v4.15). It turned out that there was a harmful modification somewhere between v4.15.0 and v4.16-rc1. A git bisect points to this patch: commit bdaca9345d41fd9420995469d27603ea62054691 Author:

[Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

Hi, we just started testing the v4.16 kernel and found the device no longer bootable (works with v4.15). It turned out that there was a harmful modification somewhere between v4.15.0 and v4.16-rc1. A git bisect points to this patch: commit bdaca9345d41fd9420995469d27603ea62054691 Author: