From: Guanglei Li
Date: Tue, 6 Feb 2018 10:43:21 +0800
> Scenario:
> 1. Port down and do fail over
> 2. Ap do rds_bind syscall
...
> PID: 45659 PID: 47039
> rds_ib_laddr_check
> /* create id_priv with a null event_handler */
> rdma_create_id
> rdma_bind_addr
>
Scenario:
1. Port down and do fail over
2. Ap do rds_bind syscall
PID: 47039 TASK: 89887e2fe640 CPU: 47 COMMAND: "kworker/u:6"
#0 [898e35f159f0] machine_kexec at 8103abf9
#1 [898e35f15a60] crash_kexec at 810b96e3
#2 [898e35f15b30] oops_end at 8150f518
On Mon, 2018-02-05 at 10:27 +0800, Guanglei Li wrote:
> Scenario:
> 1. Port down and do fail over
> 2. Ap do rds_bind syscall
>
> PID: 47039 TASK: 89887e2fe640 CPU: 47 COMMAND: "kworker/u:6"
> #0 [898e35f159f0] machine_kexec at 8103abf9
> #1 [898e35f15a60] crash_kexec at f
Scenario:
1. Port down and do fail over
2. Ap do rds_bind syscall
PID: 47039 TASK: 89887e2fe640 CPU: 47 COMMAND: "kworker/u:6"
#0 [898e35f159f0] machine_kexec at 8103abf9
#1 [898e35f15a60] crash_kexec at 810b96e3
#2 [898e35f15b30] oops_end at 8150f518