https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #27 from Justin Keogh ---
I am unable to reproduce this on any of the 4.x.y kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #26 from Justin Keogh ---
Created attachment 174581
--> https://bugzilla.kernel.org/attachment.cgi?id=174581&action=edit
dmesg for the commit that git bisect landed on, with IOMMU disabled
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #25 from Justin Keogh ---
Just to clarify, I couldn't trigger this by writing to the array from /dev/zero
at all (maybe because ZFS), all panics were triggered by writing real data from
another array on the same controller.
--
You ar
https://bugzilla.kernel.org/show_bug.cgi?id=90601
Justin Keogh changed:
What|Removed |Added
Attachment #174451|application/octet-stream|text/plain
mime type|
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #24 from Justin Keogh ---
Created attachment 174461
--> https://bugzilla.kernel.org/attachment.cgi?id=174461&action=edit
dmesg for panic without zfs modules
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #23 from Justin Keogh ---
Created attachment 174451
--> https://bugzilla.kernel.org/attachment.cgi?id=174451&action=edit
dmesg for commit 'scsi: convert device_busy to atomic_t'
--
You are receiving this mail because:
You are the a
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #22 from Justin Keogh ---
Created attachment 174441
--> https://bugzilla.kernel.org/attachment.cgi?id=174441&action=edit
.config
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #21 from Justin Keogh ---
Created attachment 174431
--> https://bugzilla.kernel.org/attachment.cgi?id=174431&action=edit
git bisect log between 3.14.33 and 3.18.7
--
You are receiving this mail because:
You are the assignee for the
https://bugzilla.kernel.org/show_bug.cgi?id=90601
Justin Keogh changed:
What|Removed |Added
CC||kernel@v6y.net
--- Comment #20 from Ju
https://bugzilla.kernel.org/show_bug.cgi?id=90601
mer...@liao.homelinux.org changed:
What|Removed |Added
Attachment #162291|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #19 from mer...@liao.homelinux.org ---
Created attachment 174181
--> https://bugzilla.kernel.org/attachment.cgi?id=174181&action=edit
crash-backtrace
--
You are receiving this mail because:
You are the assignee for the bug.
--
To un
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #18 from mer...@liao.homelinux.org ---
Created attachment 174171
--> https://bugzilla.kernel.org/attachment.cgi?id=174171&action=edit
dmesg
I finally managed to get a dmesg output with the crashing kernel.
Especially this part might
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #16 from mer...@liao.homelinux.org ---
Created attachment 173931
--> https://bugzilla.kernel.org/attachment.cgi?id=173931&action=edit
panic_screenshot
screenshot of kernel panic
--
You are receiving this mail because:
You are the a
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #17 from mer...@liao.homelinux.org ---
I am unable to get a dmesg output since the system crashes on boot.
It looks like it's happening when udev is initialized.
Sorry for the screenshot but the system crashed before any network came u
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #15 from kashyap ---
(In reply to merlin from comment #14)
> @Kashyap
>
> For me it started with 3.16 on all our servers with 3ware/lsi/avagotech
> controllers.
> I rechecked in our internal ticket system.
>
> We are using IOMMU so I
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #14 from mer...@liao.homelinux.org ---
@Kashyap
For me it started with 3.16 on all our servers with 3ware/lsi/avagotech
controllers.
I rechecked in our internal ticket system.
We are using IOMMU so I completely disabled it, recompiled
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #13 from kashyap ---
My old email id is not working now, so I have to update my email id to new
avagotech domain. Sorry for delay in response.
Does this mean issue does not happen with 3.16.1
but only happens with 3.17.1 (onwards) ?
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #12 from Alex Elsayed ---
Created attachment 166681
--> https://bugzilla.kernel.org/attachment.cgi?id=166681&action=edit
Hardware of a second machine with the issue
Intel CPUs on an ASUS board - here's the output of lshw on the mach
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #11 from mer...@liao.homelinux.org ---
I can confirm it's still happening with 3.19 here.
@Alex: What server hardware are you using? We are using Supermicro boards and
Intel CPUs.
--
You are receiving this mail because:
You are the a
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #10 from Alex Elsayed ---
Testing with 3.19 shows it's still there for me.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body
https://bugzilla.kernel.org/show_bug.cgi?id=90601
Alex Elsayed changed:
What|Removed |Added
CC||eternaleye+kernelbugs@gmail
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #8 from mer...@liao.homelinux.org ---
Hi Kashyap,
is there any additional info you need or do you know a better way to create a
useable backtrace for you?
--
You are receiving this mail because:
You are the assignee for the bug.
--
T
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #7 from mer...@liao.homelinux.org ---
Created attachment 162661
--> https://bugzilla.kernel.org/attachment.cgi?id=162661&action=edit
kernel config
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsub
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #6 from mer...@liao.homelinux.org ---
Created attachment 162651
--> https://bugzilla.kernel.org/attachment.cgi?id=162651&action=edit
backtrace with CONFIG_DMA_API_DEBUG enabled
--
You are receiving this mail because:
You are the ass
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #5 from mer...@liao.homelinux.org ---
Created attachment 162641
--> https://bugzilla.kernel.org/attachment.cgi?id=162641&action=edit
syslog before crash
--
You are receiving this mail because:
You are the assignee for the bug.
--
To
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #4 from mer...@liao.homelinux.org ---
Hi Kashyap,
1. I enabled CONFIG_DMA_API_DEBUG , strangely enough after enabling it I
couldn't even boot into the system anymore because it would crash when trying
to access the root partition (afte
https://bugzilla.kernel.org/show_bug.cgi?id=90601
kashyap changed:
What|Removed |Added
CC||kashyap.de...@lsi.com
--- Comment #3 from kashy
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #2 from mer...@liao.homelinux.org ---
I tried to mail "Adam Radford " directly as stated in
drivers/scsi/3w-sas.c but the mail address doesn't exist anymore.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugzilla.kernel.org/show_bug.cgi?id=90601
--- Comment #1 from mer...@liao.homelinux.org ---
Created attachment 162301
--> https://bugzilla.kernel.org/attachment.cgi?id=162301&action=edit
tw_cli raid config
--
You are receiving this mail because:
You are the assignee for the bug.
--
To
29 matches
Mail list logo
