Re: [iwlwifi] BUG: unable to handle kernel

2014-12-18 Thread Grumbach, Emmanuel
On Thu, 2014-12-18 at 09:13 -0800, Fengguang Wu wrote:
 Hi All,
 
 I don't see any relationship between the BUG and this bisected commit.
 Anyway, it's better to report it to the lists than to ignore.

Right - but I have to say that I have no clue how this comment can cause
the bug you are seeing...
Do you even have an Intel Wireless device the VM could access?

 
 git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git master
 
 commit 03d6c3b0fa4f5f0379cede079ec828a6c999fe43
 Author: Emmanuel Grumbach emmanuel.grumb...@intel.com
 AuthorDate: Wed Dec 3 10:39:07 2014 +0200
 Commit: Emmanuel Grumbach emmanuel.grumb...@intel.com
 CommitDate: Sun Dec 14 10:20:29 2014 +0200
 
 iwlwifi: pcie: re-ACK all interrupts after device reset
 
 When we reset the device, the CSR_INT gets cleared as well
 as CSR_INT_MASK. Meaning that we shouldn't get any interrupt
 but, due to a hardware bug, recent devices will keep sending
 interrupts. This leads to an interrupt storm while stopping
 the device.
 The way to fix this is to ACK all the interrupts after the
 device is reset so that the value of CSR_INT will stay
 0x.
 
 Fixes: 522713c81e4e (iwlwifi: pcie: properly reset the device)
 Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
 
 +--++++
 |  | 0a79a0c011 | 03d6c3b0fa | 
 iwlwifi-fi |
 +--++++
 | boot_successes   | 60 | 19 | 3  
 |
 | boot_failures| 0  | 1  | 9  
 |
 | BUG:unable_to_handle_kernel  | 0  | 1  | 9  
 |
 | Oops | 0  | 1  | 9  
 |
 | RIP:strcmp   | 0  | 1  | 9  
 |
 | Kernel_panic-not_syncing:Fatal_exception | 0  | 1  | 9  
 |
 | backtrace:led_trigger_register_simple| 0  | 1  | 9  
 |
 | backtrace:ledtrig_usb_init   | 0  | 1  | 9  
 |
 | backtrace:kernel_init_freeable   | 0  | 1  | 9  
 |
 +--++++
 
 [5.345018] g_serial gadget: Gadget Serial v2.4
 [5.345927] g_serial gadget: g_serial ready
 [5.345927] g_serial gadget: g_serial ready
 [5.346777] BUG: unable to handle kernel 
 [5.346777] BUG: unable to handle kernel paging requestpaging request at 
 8804e5f0
  at 8804e5f0
 [5.348183] IP:
 [5.348183] IP: [81446a68] strcmp+0x6/0x20
  [81446a68] strcmp+0x6/0x20
 [5.349183] PGD 37f1067 
 [5.349183] PGD 37f1067 PUD 37f2067 PUD 37f2067 PMD 37f3067 PMD 37f3067 
 PTE 8004e060PTE 8004e060
 
 [5.350498] Oops:  [#1] 
 [5.350498] Oops:  [#1] DEBUG_PAGEALLOCDEBUG_PAGEALLOC
 
 [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
 [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
 [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
 88001204c000
 [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
 88001204c000
 [5.354143] RIP: 0010:[81446a68] 
 [5.354143] RIP: 0010:[81446a68]  [81446a68] 
 strcmp+0x6/0x20
  [81446a68] strcmp+0x6/0x20
 [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
 [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
 [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
 81d35310
 [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
 81d35310
 [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
 8804e5f0
 [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
 8804e5f0
 [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
 033a
 [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
 033a
 [5.354451] R10:  R11: 82531cd1 R12: 
 88000c19fa00
 [5.354451] R10:  R11: 82531cd1 R12: 
 88000c19fa00
 [5.354451] R13:  R14: 837958b8 R15: 
 
 [5.354451] R13:  R14: 837958b8 R15: 
 
 [5.354451] FS:  () GS:82789000() 
 knlGS:
 [5.354451] FS:  () GS:82789000() 
 knlGS:
 [5.354451] CS:  0010 DS:  ES:  CR0: 8005003b
 [5.354451] CS:  0010 DS:  ES:  CR0: 8005003b
 [5.354451] CR2: 8804e5f0 CR3: 02776000 CR4: 
 06b0
 [

Re: [iwlwifi] BUG: unable to handle kernel

2014-12-18 Thread Fengguang Wu
On Fri, Dec 19, 2014 at 03:42:17AM +0800, Grumbach, Emmanuel wrote:
 On Thu, 2014-12-18 at 09:13 -0800, Fengguang Wu wrote:
  Hi All,
  
  I don't see any relationship between the BUG and this bisected commit.
  Anyway, it's better to report it to the lists than to ignore.
 
 Right - but I have to say that I have no clue how this comment can cause
 the bug you are seeing...

s?comment?commit?

 Do you even have an Intel Wireless device the VM could access?

Nope. It's simple QEMU virtual machine boot test.

Thanks,
Fengguang

  
  git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git 
  master
  
  commit 03d6c3b0fa4f5f0379cede079ec828a6c999fe43
  Author: Emmanuel Grumbach emmanuel.grumb...@intel.com
  AuthorDate: Wed Dec 3 10:39:07 2014 +0200
  Commit: Emmanuel Grumbach emmanuel.grumb...@intel.com
  CommitDate: Sun Dec 14 10:20:29 2014 +0200
  
  iwlwifi: pcie: re-ACK all interrupts after device reset
  
  When we reset the device, the CSR_INT gets cleared as well
  as CSR_INT_MASK. Meaning that we shouldn't get any interrupt
  but, due to a hardware bug, recent devices will keep sending
  interrupts. This leads to an interrupt storm while stopping
  the device.
  The way to fix this is to ACK all the interrupts after the
  device is reset so that the value of CSR_INT will stay
  0x.
  
  Fixes: 522713c81e4e (iwlwifi: pcie: properly reset the device)
  Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
  
  +--++++
  |  | 0a79a0c011 | 03d6c3b0fa | 
  iwlwifi-fi |
  +--++++
  | boot_successes   | 60 | 19 | 3
|
  | boot_failures| 0  | 1  | 9
|
  | BUG:unable_to_handle_kernel  | 0  | 1  | 9
|
  | Oops | 0  | 1  | 9
|
  | RIP:strcmp   | 0  | 1  | 9
|
  | Kernel_panic-not_syncing:Fatal_exception | 0  | 1  | 9
|
  | backtrace:led_trigger_register_simple| 0  | 1  | 9
|
  | backtrace:ledtrig_usb_init   | 0  | 1  | 9
|
  | backtrace:kernel_init_freeable   | 0  | 1  | 9
|
  +--++++
  
  [5.345018] g_serial gadget: Gadget Serial v2.4
  [5.345927] g_serial gadget: g_serial ready
  [5.345927] g_serial gadget: g_serial ready
  [5.346777] BUG: unable to handle kernel 
  [5.346777] BUG: unable to handle kernel paging requestpaging request at 
  8804e5f0
   at 8804e5f0
  [5.348183] IP:
  [5.348183] IP: [81446a68] strcmp+0x6/0x20
   [81446a68] strcmp+0x6/0x20
  [5.349183] PGD 37f1067 
  [5.349183] PGD 37f1067 PUD 37f2067 PUD 37f2067 PMD 37f3067 PMD 37f3067 
  PTE 8004e060PTE 8004e060
  
  [5.350498] Oops:  [#1] 
  [5.350498] Oops:  [#1] DEBUG_PAGEALLOCDEBUG_PAGEALLOC
  
  [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
  [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
  [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
  88001204c000
  [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
  88001204c000
  [5.354143] RIP: 0010:[81446a68] 
  [5.354143] RIP: 0010:[81446a68]  [81446a68] 
  strcmp+0x6/0x20
   [81446a68] strcmp+0x6/0x20
  [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
  [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
  [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
  81d35310
  [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
  81d35310
  [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
  8804e5f0
  [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
  8804e5f0
  [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
  033a
  [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
  033a
  [5.354451] R10:  R11: 82531cd1 R12: 
  88000c19fa00
  [5.354451] R10:  R11: 82531cd1 R12: 
  88000c19fa00
  [5.354451] R13:  R14: 837958b8 R15: 
  
  [5.354451] R13:  R14: 837958b8 R15: 
  
  [5.354451] FS:  () GS:82789000() 
  knlGS:
  [5.354451] FS:  () 

Re: [iwlwifi] BUG: unable to handle kernel

2014-12-18 Thread Grumbach, Emmanuel
On Thu, 2014-12-18 at 13:07 -0800, Fengguang Wu wrote:
 On Fri, Dec 19, 2014 at 03:42:17AM +0800, Grumbach, Emmanuel wrote:
  On Thu, 2014-12-18 at 09:13 -0800, Fengguang Wu wrote:
   Hi All,
   
   I don't see any relationship between the BUG and this bisected commit.
   Anyway, it's better to report it to the lists than to ignore.
  
  Right - but I have to say that I have no clue how this comment can cause
  the bug you are seeing...
 
 s?comment?commit?
 

Yes :)

  Do you even have an Intel Wireless device the VM could access?
 
 Nope. It's simple QEMU virtual machine boot test.
 

In that case - this just can't be right... Don't know what to say...

 Thanks,
 Fengguang
 
   
   git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git 
   master
   
   commit 03d6c3b0fa4f5f0379cede079ec828a6c999fe43
   Author: Emmanuel Grumbach emmanuel.grumb...@intel.com
   AuthorDate: Wed Dec 3 10:39:07 2014 +0200
   Commit: Emmanuel Grumbach emmanuel.grumb...@intel.com
   CommitDate: Sun Dec 14 10:20:29 2014 +0200
   
   iwlwifi: pcie: re-ACK all interrupts after device reset
   
   When we reset the device, the CSR_INT gets cleared as well
   as CSR_INT_MASK. Meaning that we shouldn't get any interrupt
   but, due to a hardware bug, recent devices will keep sending
   interrupts. This leads to an interrupt storm while stopping
   the device.
   The way to fix this is to ACK all the interrupts after the
   device is reset so that the value of CSR_INT will stay
   0x.
   
   Fixes: 522713c81e4e (iwlwifi: pcie: properly reset the device)
   Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
   
   +--++++
   |  | 0a79a0c011 | 03d6c3b0fa | 
   iwlwifi-fi |
   +--++++
   | boot_successes   | 60 | 19 | 3  
   |
   | boot_failures| 0  | 1  | 9  
   |
   | BUG:unable_to_handle_kernel  | 0  | 1  | 9  
   |
   | Oops | 0  | 1  | 9  
   |
   | RIP:strcmp   | 0  | 1  | 9  
   |
   | Kernel_panic-not_syncing:Fatal_exception | 0  | 1  | 9  
   |
   | backtrace:led_trigger_register_simple| 0  | 1  | 9  
   |
   | backtrace:ledtrig_usb_init   | 0  | 1  | 9  
   |
   | backtrace:kernel_init_freeable   | 0  | 1  | 9  
   |
   +--++++
   
   [5.345018] g_serial gadget: Gadget Serial v2.4
   [5.345927] g_serial gadget: g_serial ready
   [5.345927] g_serial gadget: g_serial ready
   [5.346777] BUG: unable to handle kernel 
   [5.346777] BUG: unable to handle kernel paging requestpaging request 
   at 8804e5f0
at 8804e5f0
   [5.348183] IP:
   [5.348183] IP: [81446a68] strcmp+0x6/0x20
[81446a68] strcmp+0x6/0x20
   [5.349183] PGD 37f1067 
   [5.349183] PGD 37f1067 PUD 37f2067 PUD 37f2067 PMD 37f3067 PMD 
   37f3067 PTE 8004e060PTE 8004e060
   
   [5.350498] Oops:  [#1] 
   [5.350498] Oops:  [#1] DEBUG_PAGEALLOCDEBUG_PAGEALLOC
   
   [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
   [5.351360] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-g03d6c3b #1
   [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
   88001204c000
   [5.352660] task: 88001206 ti: 88001204c000 task.ti: 
   88001204c000
   [5.354143] RIP: 0010:[81446a68] 
   [5.354143] RIP: 0010:[81446a68]  [81446a68] 
   strcmp+0x6/0x20
[81446a68] strcmp+0x6/0x20
   [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
   [5.354451] RSP: :88001204fe28  EFLAGS: 00010246
   [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
   81d35310
   [5.354451] RAX:  RBX: 88000c08fe00 RCX: 
   81d35310
   [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
   8804e5f0
   [5.354451] RDX: 88000c08fe68 RSI: 826d05be RDI: 
   8804e5f0
   [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
   033a
   [5.354451] RBP: 88001204fe28 R08: 0001 R09: 
   033a
   [5.354451] R10:  R11: 82531cd1 R12: 
   88000c19fa00
   [5.354451] R10:  R11: 82531cd1 R12: 
   88000c19fa00
   [5.354451] R13:  R14: 837958b8 R15: