From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5155981875505233067==" MIME-Version: 1.0 From: Boris Brezillon To: lkp@lists.01.org Subject: Re: [nand] BUG: unable to handle kernel NULL pointer dereference at 000005f4 Date: Sun, 13 Dec 2015 21:50:43 +0100 Message-ID: <20151213215043.15d864da@bbrezillon> In-Reply-To: <20151213014917.GA30401@wfg-t540p.sh.intel.com> List-Id: --===============5155981875505233067== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Fengguang, On Sun, 13 Dec 2015 09:49:17 +0800 Fengguang Wu wrote: > Hi Boris, > = > FYI, this happened when merging your branch, which indicates possible > conflicts with other developer's patches or the new RC release. Is this boot test also run on my bbrezillon-0day/nand/layering-rework branch (before merging it into devel-spot), and if it is, do you see the same error? Is the devel-spot-201512102358 tag publicly accessible? If it's not, could you push it somewhere (or give me a way to generate it by pulling the relevant branches), so that I can investigate on this bug? = > = > linux-next/master also has the problem. Okay. You mean linux-next/master alone, or after merging my branch into linux-next/master? > = > commit af8fc334a121611474134e68e154fd9a6deea96a > Merge: acfc1de 8b402c3 > Author: 0day robot > AuthorDate: Fri Dec 11 00:00:09 2015 +0800 > Commit: 0day robot > CommitDate: Fri Dec 11 00:00:09 2015 +0800 > = > Merge 'bbrezillon-0day/nand/layering-rework' into devel-spot-20151210= 2358 > = > +------------------------------------------+------------+------------+---= ---------+------------+ > | | acfc1de1e0 | 8b402c389e | af= 8fc334a1 | 2f36956512 | > +------------------------------------------+------------+------------+---= ---------+------------+ > | boot_successes | 88 | 63 | 0 = | 0 | > | boot_failures | 2 | 0 | 26= | 19 | > | BUG:kernel_boot_hang | 2 | 0 | 2 = | | > | BUG:unable_to_handle_kernel | 0 | 0 | 24= | 19 | > | Oops | 0 | 0 | 24= | 19 | > | EIP_is_at_nand_transfer_oob | 0 | 0 | 24= | 19 | > | Kernel_panic-not_syncing:Fatal_exception | 0 | 0 | 24= | 19 | > | backtrace:nand_default_bbt | 0 | 0 | 24= | 19 | > | backtrace:ns_init_module | 0 | 0 | 24= | 19 | > | backtrace:kernel_init_freeable | 0 | 0 | 24= | 19 | > +------------------------------------------+------------+------------+---= ---------+------------+ > = > [ 14.253825] sector address bytes: 3 > [ 14.254636] options: 0x42 > [ 14.255940] Scanning device for bad blocks > [ 14.256950] BUG: unable to handle kernel NULL pointer dereference at 0= 00005f4 > [ 14.258509] IP: [] nand_transfer_oob+0x3b/0x220 > [ 14.259810] *pde =3D 00000000 = > [ 14.260629] Oops: 0000 [#1] PREEMPT SMP = > [ 14.261767] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-rc4-02185-= gaf8fc33 #2 > [ 14.263387] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIO= S Debian-1.8.2-1 04/01/2014 > [ 14.284272] task: d05d0000 ti: d05d8000 task.ti: d05d8000 > [ 14.285392] EIP: 0060:[] EFLAGS: 00010297 CPU: 1 > [ 14.303080] EIP is at nand_transfer_oob+0x3b/0x220 > [ 14.304251] EAX: d05d9e74 EBX: d05d9e60 ECX: 00000010 EDX: 00000000 > [ 14.305527] ESI: 00000000 EDI: 00000010 EBP: d05d9dc4 ESP: d05d9da0 > [ 14.313613] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 > [ 14.314765] CR0: 8005003b CR2: 000005f4 CR3: 023f6000 CR4: 00000690 > [ 14.316041] Stack: > [ 14.330028] 00000000 d04fa000 d04fa000 d1d3cc2c d05d9dc4 c18e2931 d05= d9e60 d04fa000 > [ 14.332796] 00000010 d05d9e10 c18e5dd9 d05d9e74 00000010 00000000 000= 00000 00000000 > [ 14.335580] 00000010 d05d9e74 d1d3cc2c 00000000 00000010 00000000 000= 00000 00000000 > [ 14.340054] Call Trace: > [ 14.340806] [] ? nand_read_oob_std+0x31/0x40 > [ 14.342115] [] nand_read_oob+0x239/0x350 > [ 14.343337] [] ? nand_do_read_ops+0x610/0x610 > [ 14.344621] [] mtd_read_oob+0x2e/0x70 > [ 14.345788] [] create_bbt+0x122/0x260 > [ 14.346952] [] ? __might_sleep+0x31/0xa0 > [ 14.348217] [] nand_default_bbt+0x678/0x760 > [ 14.370976] [] ? put_online_cpus+0x3a/0x80 > [ 14.372219] [] ? ns_init_module+0xc0d/0xd22 > [ 14.373483] [] ns_init_module+0xc4f/0xd22 > [ 14.374725] [] ? inftl_scan_bbt+0x49a/0x49a > [ 14.375984] [] do_one_initcall+0x15f/0x16e > [ 14.377222] [] ? parse_args+0x25f/0x420 > [ 14.380154] [] kernel_init_freeable+0xfc/0x179 > [ 14.381531] [] kernel_init+0xb/0xe0 > [ 14.382727] [] ? schedule_tail+0x20/0x80 > [ 14.384002] [] ret_from_kernel_thread+0x21/0x38 > [ 14.385370] [] ? rest_init+0xb0/0xb0 > [ 14.386330] Code: 80 ec 00 00 00 89 55 e8 89 45 dc 74 4b 72 11 83 f9 0= 2 74 0c 0f 0b 8d 76 00 8d bc 27 00 00 00 00 8b 45 08 8b 55 dc 8b 4d 0c 8b 3= 0 <8b> 9a f4 05 00 00 8b 45 e8 01 de 83 f9 08 89 c7 0f 83 47 01 00 > [ 14.395572] EIP: [] nand_transfer_oob+0x3b/0x220 SS:ESP 0068= :d05d9da0 > [ 14.397476] CR2: 00000000000005f4 > [ 14.398286] ---[ end trace 515ef95ee551d435 ]--- > [ 14.399461] Kernel panic - not syncing: Fatal exception I had a quick look at the changes made in my patchset, and I didn't find any obvious errors. I'll try to test the nandsim driver tomorrow. BTW, the backtrace looks a bit weird to me, it mixes nandsim functions (ns_init_module()) with diskonchip functions (inftl_scan_bbt()), which, AFAIK, is not supposed to happen. Thanks, Boris -- = Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com --===============5155981875505233067==--