Re: PANIC: ata_qc_new_init crashes at boot
On Mon, Aug 18, 2014 at 2:21 PM, Tejun Heo wrote: > Hello, > > Sorry about the delay. Cc'ing Dan. > > On Wed, Aug 06, 2014 at 02:02:47PM -0400, Nick Krause wrote: >> On Wed, Jul 23, 2014 at 4:39 AM, Peter Zijlstra wrote: >> > On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: >> >> [ +cc Tejun ] >> >> >> >> On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: >> >> > This is a repeatable panic, happens every boot (and prevents starting >> >> > my system) >> >> > >> >> > [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk >> >> > [8.733857] sda: sda1 sda2 sda3 >> >> > [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk >> >> > [8.737943] BUG: unable to handle kernel NULL pointer dereference at >> >> > 0058 >> >> > [8.737947] IP: [] ata_qc_new_init+0x188/0x1b0 >> > >> > I too have this problem on one of my machines. Let me know if there's >> > anything you need. > > Are you still seeing this on every boot? ISTR this getting fixed but > I could be confused. Dan, the original thread is > > > http://lkml.kernel.org/g/CAEuXFEy5=0xkqpiwqnigbpi5ehszq5f_u7sj0t2bho_1lqe...@mail.gmail.com > This is the last I heard: http://marc.info/?l=linux-ide=140630768020241=2 But I never saw a follow up. Hmmm, commit 1a112d10f03e libata: introduce ata_host->n_tags to avoid oops on SAS controllers ...doesn't fix this? Jesse reported positive results here: http://marc.info/?l=linux-ide=140624094731542=2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
Hello, Sorry about the delay. Cc'ing Dan. On Wed, Aug 06, 2014 at 02:02:47PM -0400, Nick Krause wrote: > On Wed, Jul 23, 2014 at 4:39 AM, Peter Zijlstra wrote: > > On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: > >> [ +cc Tejun ] > >> > >> On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: > >> > This is a repeatable panic, happens every boot (and prevents starting my > >> > system) > >> > > >> > [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk > >> > [8.733857] sda: sda1 sda2 sda3 > >> > [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk > >> > [8.737943] BUG: unable to handle kernel NULL pointer dereference at > >> > 0058 > >> > [8.737947] IP: [] ata_qc_new_init+0x188/0x1b0 > > > > I too have this problem on one of my machines. Let me know if there's > > anything you need. Are you still seeing this on every boot? ISTR this getting fixed but I could be confused. Dan, the original thread is http://lkml.kernel.org/g/CAEuXFEy5=0xkqpiwqnigbpi5ehszq5f_u7sj0t2bho_1lqe...@mail.gmail.com Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
Hello, Sorry about the delay. Cc'ing Dan. On Wed, Aug 06, 2014 at 02:02:47PM -0400, Nick Krause wrote: On Wed, Jul 23, 2014 at 4:39 AM, Peter Zijlstra pet...@infradead.org wrote: On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: [ +cc Tejun ] On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: This is a repeatable panic, happens every boot (and prevents starting my system) [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk [8.733857] sda: sda1 sda2 sda3 [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk [8.737943] BUG: unable to handle kernel NULL pointer dereference at 0058 [8.737947] IP: [814e0618] ata_qc_new_init+0x188/0x1b0 I too have this problem on one of my machines. Let me know if there's anything you need. Are you still seeing this on every boot? ISTR this getting fixed but I could be confused. Dan, the original thread is http://lkml.kernel.org/g/CAEuXFEy5=0xkqpiwqnigbpi5ehszq5f_u7sj0t2bho_1lqe...@mail.gmail.com Thanks. -- tejun -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
On Mon, Aug 18, 2014 at 2:21 PM, Tejun Heo t...@kernel.org wrote: Hello, Sorry about the delay. Cc'ing Dan. On Wed, Aug 06, 2014 at 02:02:47PM -0400, Nick Krause wrote: On Wed, Jul 23, 2014 at 4:39 AM, Peter Zijlstra pet...@infradead.org wrote: On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: [ +cc Tejun ] On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: This is a repeatable panic, happens every boot (and prevents starting my system) [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk [8.733857] sda: sda1 sda2 sda3 [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk [8.737943] BUG: unable to handle kernel NULL pointer dereference at 0058 [8.737947] IP: [814e0618] ata_qc_new_init+0x188/0x1b0 I too have this problem on one of my machines. Let me know if there's anything you need. Are you still seeing this on every boot? ISTR this getting fixed but I could be confused. Dan, the original thread is http://lkml.kernel.org/g/CAEuXFEy5=0xkqpiwqnigbpi5ehszq5f_u7sj0t2bho_1lqe...@mail.gmail.com This is the last I heard: http://marc.info/?l=linux-idem=140630768020241w=2 But I never saw a follow up. Hmmm, commit 1a112d10f03e libata: introduce ata_host-n_tags to avoid oops on SAS controllers ...doesn't fix this? Jesse reported positive results here: http://marc.info/?l=linux-idem=140624094731542w=2 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: > [ +cc Tejun ] > > On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: > > This is a repeatable panic, happens every boot (and prevents starting my > > system) > > > > > > > > [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk > > [8.733857] sda: sda1 sda2 sda3 > > [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk > > [8.737943] BUG: unable to handle kernel NULL pointer dereference at > > 0058 > > [8.737947] IP: [] ata_qc_new_init+0x188/0x1b0 I too have this problem on one of my machines. Let me know if there's anything you need. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
On Tue, Jul 22, 2014 at 03:48:02PM -0400, Peter Hurley wrote: [ +cc Tejun ] On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: This is a repeatable panic, happens every boot (and prevents starting my system) [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk [8.733857] sda: sda1 sda2 sda3 [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk [8.737943] BUG: unable to handle kernel NULL pointer dereference at 0058 [8.737947] IP: [814e0618] ata_qc_new_init+0x188/0x1b0 I too have this problem on one of my machines. Let me know if there's anything you need. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
[ +cc Tejun ] On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: > This is a repeatable panic, happens every boot (and prevents starting my > system) > > .config attached, built from commit 15ba2236f3556fc01b9ca91394465152b5ea74b6 > > > > [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk > [8.733857] sda: sda1 sda2 sda3 > [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk > [8.737943] BUG: unable to handle kernel NULL pointer dereference > at 0058 > [8.737947] IP: [] ata_qc_new_init+0x188/0x1b0 > [8.737948] PGD 0 > [8.737949] Oops: 0002 [#1] SMP > [8.737953] Modules linked in: isci libsas scsi_transport_sas > mgag200 drm_kms_helper ttm > [8.737955] CPU: 1 PID: 518 Comm: udevd Not tainted 3.16.0-rc6+ #62 > [8.737956] Hardware name: Intel Corporation S2600CO/S2600CO, BIOS > SE5C600.86B.02.02.0002.122320131210 12/23/2013 > [8.737956] task: 880c1a00b280 ti: 88061a00 task.ti: > 88061a00 > [8.737958] RIP: 0010:[] [] > ata_qc_new_init+0x188/0x1b0 > [8.737959] RSP: 0018:88061a003ae8 EFLAGS: 00010012 > [8.737959] RAX: 0001 RBX: 88000241ca80 RCX: > 00fa > [8.737960] RDX: 0020 RSI: 0020 RDI: > 8806194aa298 > [8.737960] RBP: 88061a003ae8 R08: 8806194a8000 R09: > > [8.737961] R10: R11: 88000241ca80 R12: > 88061ad58200 > [8.737961] R13: 8806194aa298 R14: 814e67a0 R15: > 8806194a8000 > [8.737962] FS: 7f3ad7fe3840() GS:88062762() > knlGS: > [8.737963] CS: 0010 DS: ES: CR0: 80050033 > [8.737963] CR2: 0058 CR3: 00061a118000 CR4: > 001407e0 > [8.737964] Stack: > [8.737965] 88061a003b20 814e96e1 88000241ca80 > 88061ad58200 > [8.737966] 8800b6bf6000 880c1c988000 880619903850 > 88061a003b68 > [8.737967] a0056ce1 88061a003b48 13d6e6f8 > 88000241ca80 > [8.737968] Call Trace: > [8.737971] [] ata_sas_queuecmd+0xa1/0x430 > [8.737976] [] sas_queuecommand+0x191/0x220 [libsas] > [8.737978] [] scsi_dispatch_cmd+0x10e/0x300 > [8.737981] [] scsi_request_fn+0x2f5/0x550 > [8.737983] [] __blk_run_queue+0x33/0x40 > [8.737985] [] queue_unplugged+0x2a/0x90 > [8.737986] [] blk_flush_plug_list+0x1b4/0x210 > [8.737988] [] blk_finish_plug+0x14/0x50 > [8.737990] [] __do_page_cache_readahead+0x198/0x1f0 > [8.737991] [] force_page_cache_readahead+0x31/0x50 > [8.737992] [] page_cache_sync_readahead+0x3e/0x50 > [8.737995] [] generic_file_read_iter+0x496/0x5a0 > [8.737998] [] blkdev_read_iter+0x37/0x40 > [8.738002] [] new_sync_read+0x7e/0xb0 > [8.738004] [] vfs_read+0x94/0x170 > [8.738006] [] SyS_read+0x46/0xb0 > [8.738007] [] ? SyS_lseek+0x91/0xb0 > [8.738011] [] system_call_fastpath+0x16/0x1b > [8.738021] Code: 00 00 00 88 50 29 83 7f 08 01 19 d2 83 e2 f0 83 > ea 50 88 50 34 c6 81 1d 02 00 00 40 c6 81 17 02 00 00 00 5d c3 66 0f > 1f 44 00 00 <89> 14 25 58 00 00 00 > [8.738023] RIP [] ata_qc_new_init+0x188/0x1b0 > [8.738023] RSP > [8.738023] CR2: 0058 > [8.738025] ---[ end trace 831868baa88bb368 ]--- > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PANIC: ata_qc_new_init crashes at boot
[ +cc Tejun ] On 07/22/2014 03:26 PM, Jesse Brandeburg wrote: This is a repeatable panic, happens every boot (and prevents starting my system) .config attached, built from commit 15ba2236f3556fc01b9ca91394465152b5ea74b6 [8.732993] sd 6:0:1:0: [sdb] Attached SCSI disk [8.733857] sda: sda1 sda2 sda3 [8.734318] sd 6:0:0:0: [sda] Attached SCSI disk [8.737943] BUG: unable to handle kernel NULL pointer dereference at 0058 [8.737947] IP: [814e0618] ata_qc_new_init+0x188/0x1b0 [8.737948] PGD 0 [8.737949] Oops: 0002 [#1] SMP [8.737953] Modules linked in: isci libsas scsi_transport_sas mgag200 drm_kms_helper ttm [8.737955] CPU: 1 PID: 518 Comm: udevd Not tainted 3.16.0-rc6+ #62 [8.737956] Hardware name: Intel Corporation S2600CO/S2600CO, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [8.737956] task: 880c1a00b280 ti: 88061a00 task.ti: 88061a00 [8.737958] RIP: 0010:[814e0618] [814e0618] ata_qc_new_init+0x188/0x1b0 [8.737959] RSP: 0018:88061a003ae8 EFLAGS: 00010012 [8.737959] RAX: 0001 RBX: 88000241ca80 RCX: 00fa [8.737960] RDX: 0020 RSI: 0020 RDI: 8806194aa298 [8.737960] RBP: 88061a003ae8 R08: 8806194a8000 R09: [8.737961] R10: R11: 88000241ca80 R12: 88061ad58200 [8.737961] R13: 8806194aa298 R14: 814e67a0 R15: 8806194a8000 [8.737962] FS: 7f3ad7fe3840() GS:88062762() knlGS: [8.737963] CS: 0010 DS: ES: CR0: 80050033 [8.737963] CR2: 0058 CR3: 00061a118000 CR4: 001407e0 [8.737964] Stack: [8.737965] 88061a003b20 814e96e1 88000241ca80 88061ad58200 [8.737966] 8800b6bf6000 880c1c988000 880619903850 88061a003b68 [8.737967] a0056ce1 88061a003b48 13d6e6f8 88000241ca80 [8.737968] Call Trace: [8.737971] [814e96e1] ata_sas_queuecmd+0xa1/0x430 [8.737976] [a0056ce1] sas_queuecommand+0x191/0x220 [libsas] [8.737978] [8149afee] scsi_dispatch_cmd+0x10e/0x300 [8.737981] [814a3bc5] scsi_request_fn+0x2f5/0x550 [8.737983] [81317613] __blk_run_queue+0x33/0x40 [8.737985] [8131781a] queue_unplugged+0x2a/0x90 [8.737986] [8131ceb4] blk_flush_plug_list+0x1b4/0x210 [8.737988] [8131d274] blk_finish_plug+0x14/0x50 [8.737990] [8117eaa8] __do_page_cache_readahead+0x198/0x1f0 [8.737991] [8117ee21] force_page_cache_readahead+0x31/0x50 [8.737992] [8117ee7e] page_cache_sync_readahead+0x3e/0x50 [8.737995] [81172ac6] generic_file_read_iter+0x496/0x5a0 [8.737998] [81219897] blkdev_read_iter+0x37/0x40 [8.738002] [811e307e] new_sync_read+0x7e/0xb0 [8.738004] [811e3734] vfs_read+0x94/0x170 [8.738006] [811e43c6] SyS_read+0x46/0xb0 [8.738007] [811e33d1] ? SyS_lseek+0x91/0xb0 [8.738011] [8171ee29] system_call_fastpath+0x16/0x1b [8.738021] Code: 00 00 00 88 50 29 83 7f 08 01 19 d2 83 e2 f0 83 ea 50 88 50 34 c6 81 1d 02 00 00 40 c6 81 17 02 00 00 00 5d c3 66 0f 1f 44 00 00 89 14 25 58 00 00 00 [8.738023] RIP [814e0618] ata_qc_new_init+0x188/0x1b0 [8.738023] RSP 88061a003ae8 [8.738023] CR2: 0058 [8.738025] ---[ end trace 831868baa88bb368 ]--- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
