On Mon, Sep 28, 2020 at 5:24 AM Zhao, Haifeng <haifeng.zhao@xxxxxxxxx> wrote: > > Andy, > May I ask what you think that's not relevant in the oops ? any rules ? First of all, please don't send private messages on OSS development matters (partially returned Cc list). Second, stop top postings. Now to the question, the rule is simple — it's called "common sense". See below the examples, but you may cut even more. So, don't pollute commit messages with unrelated information. > On Sun, Sep 27, 2020 at 11:31 AM Ethan Zhao <haifeng.zhao@xxxxxxxxx> wrote: ... > > Buffer I/O error on dev nvme0n1p1, logical block 3328, async page read > > BUG: kernel NULL pointer dereference, address: 0000000000000050 The below... > > #PF: supervisor read access in kernel mode > > #PF: error_code(0x0000) - not-present page > > PGD 0 > > Seems like you randomly did something about the series and would like it to be applied?! It's no go! > Please, read my comments again v1 one more time and carefully comment or address. > > Why do you still have these (some above, some below this comment) non-relevant lines of oops? .. > > Oops: 0000 [#1] SMP NOPTI ...is anybody getting new information from the above? I don't think so. > > CPU: 12 PID: 513 Comm: irq/124-pcie-dp Not tainted 5.8.0 el8.x86_64+ #1 > > RIP: 0010:report_error_detected.cold.4+0x7d/0xe6 > > Code: b6 d0 e8 e8 fe 11 00 e8 16 c5 fb ff be 06 00 00 00 48 89 df e8 d3 > > 65 ff ff b8 06 00 00 00 e9 75 fc ff ff 48 8b 43 68 45 31 c9 <48> 8b 50 > > 50 48 83 3a 00 41 0f 94 c1 45 31 c0 48 85 d2 41 0f 94 c0 > > RSP: 0018:ff8e06cf8762fda8 EFLAGS: 00010246 > > RAX: 0000000000000000 RBX: ff4e3eaacf42a000 RCX: ff4e3eb31f223c01 > > RDX: ff4e3eaacf42a140 RSI: ff4e3eb31f223c00 RDI: ff4e3eaacf42a138 > > RBP: ff8e06cf8762fdd0 R08: 00000000000000bf R09: 0000000000000000 > > R10: 000000eb8ebeab53 R11: ffffffff93453258 R12: 0000000000000002 > > R13: ff4e3eaacf42a130 R14: ff8e06cf8762fe2c R15: ff4e3eab44733828 > > FS: 0000000000000000(0000) GS:ff4e3eab1fd00000(0000) knl > > GS:0000000000000000 > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > CR2: 0000000000000050 CR3: 0000000f8f80a004 CR4: 0000000000761ee0 > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > > PKRU: 55555554 > > Call Trace: > > ? report_normal_detected+0x20/0x20 > > report_frozen_detected+0x16/0x20 > > pci_walk_bus+0x75/0x90 > > ? dpc_irq+0x90/0x90 > > pcie_do_recovery+0x157/0x201 > > ? irq_finalize_oneshot.part.47+0xe0/0xe0 > > dpc_handler+0x29/0x40 > > irq_thread_fn+0x24/0x60 The below, for example, does it affect anyhow the meaning of the crash log? I don't think so, can be cut. > > irq_thread+0xea/0x170 > > ? irq_forced_thread_fn+0x80/0x80 > > ? irq_thread_check_affinity+0xf0/0xf0 > > kthread+0x124/0x140 > > ? kthread_park+0x90/0x90 > > ret_from_fork+0x1f/0x30 > > Modules linked in: nft_fib_inet......... > > CR2: 0000000000000050 -- With Best Regards, Andy Shevchenko
