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

2018-04-12 Thread H. Nikolaus Schaller
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

2018-04-12 Thread H. Nikolaus Schaller
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

2018-04-12 Thread 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 release-candidates... I've

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

2018-04-12 Thread 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 release-candidates... I've found it's way easier to test Linux next on

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

2018-04-11 Thread H. Nikolaus Schaller
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

2018-04-11 Thread H. Nikolaus Schaller
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: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5

2018-04-10 Thread 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 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

2018-04-10 Thread 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 was a harmful modification somewhere between > v4.15.0 and v4.16-rc1. > > A