https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
kalo...@gmail.com changed:
What|Removed |Added
CC||kalo...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Сергей changed:
What|Removed |Added
CC||lv...@wimsg.com
--- Comment #24 from Серг
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Dmitry Afanasiev changed:
What|Removed |Added
CC||k...@matpockuh.ru
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Vladimir Noskov changed:
What|Removed |Added
Severity|Affects Some People |Affects Many People
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Vladimir Noskov changed:
What|Removed |Added
Version|10.2-RELEASE|10.3-RELEASE
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #22 from Vladimir Noskov ---
I upgrade to 10.3-RELEASE.
Error sata is present :(
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #21 from Vladimir Noskov ---
Now... bug repets :(
FreeBSD wcsn.wocson.ru 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0: Thu Jan 14
15:48:17 UTC 2016 r...@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
Now after
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #20 from 21474...@gmail.com ---
I have this issue on two new HP Microserver Gen8, so the probability of a
hardware failure is low.
I have solved the issue disabling the drives stand by.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #19 from Vladimir Noskov ---
Also talks about this:
https://forums.freebsd.org/threads/kernel-ahcich-timeout-in-slot.51868/
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #18 from patpro ---
(In reply to Chris Platts from comment #17)
Interesting! I use smartmontools too, but I can see timeouts during boot, so I
guess this particular problem is not related to smartmontools.
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #17 from Chris Platts ---
Ok, I found the cause of these timeouts for me.
I rebuilt the system from scratch on another disk (connected to the same
controller as my present boot disk).
All the way through the build I had no tim
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #16 from Vladimir Noskov ---
(In reply to Chris Platts from comment #15)
It's not stupidity are just some do not care. Sometimes.
But the fact that there is an error related to the behavior it is hot plug
devices, very bad. Con
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #15 from Chris Platts ---
(In reply to patpro from comment #14)
Fair point!
I'll sort out my system so I have two boot disks available -- one being the
installation upgraded from 9.1 to 10.0 and finally to 10.2 which is
experi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #14 from patpro ---
(In reply to Chris Platts from comment #13)
Well, don't forget I've got the exact same problem on a native Intel chipset
(comment 2) :
ahci0@pci0:0:31:2:class=0x010601 card=0x062415d9 chip=0x1c028086 re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #13 from Chris Platts ---
(In reply to Vladimir Noskov from comment #12)
Ok - I think I've been stupid.
I was understanding 'ahcichX' to be where 'X' is the controller ID. But it
isn't, is it? It's the channel number - the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #12 from Vladimir Noskov ---
I suspect that this has something to do with the hot-plug drives connections.
My suspicions are supported by you.
Developers are !!! Pay attention!
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #11 from Chris Platts ---
(In reply to Vladimir Noskov from comment #10)
No problem :)
These are eSATA interfaces. I've replaced the cables and enclosures (and in
one instance, the drive itself). Still the problem remains.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #10 from Vladimir Noskov ---
"tsschkvy" - read as "words"
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #9 from Vladimir Noskov ---
Yes, I have no quotes, but it works without them. Hmm ...
As far as I understand, the double quotes are needed for multi tsschkvy
parameters.
But the right to put "" for all. :)
When will appear and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #8 from Chris Platts ---
(In reply to Vladimir Noskov from comment #7)
Hi,
Here's my output:
chris@trillian:~ % kenv | grep ahci
hint.ahci.0.msi="0"
hint.ahci.1.msi="0"
Those double-quotes aren't present in device.hints, but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #7 from Vladimir Noskov ---
(In reply to Chris Platts from comment #6)
You place this
hint.ahci.0.msi=0
hint.ahci.1.msi=0
??
You see kernel settings:
# kenv | gr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #6 from Chris Platts ---
(In reply to Vladimir Noskov from comment #5)
Ok -- I tried moving the hits to /boot/device.hints rather than
/boot/loader.conf. Unfortunately the errors persist:
Sep 30 13:25:15 trillian kernel: ahci
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #5 from Vladimir Noskov ---
(In reply to Chris Platts from comment #4)
This hint.ahci.0.msi=0 place to /boot/device.hints
But now my system have defaults settings and I comment this:
##
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Vladimir Noskov changed:
What|Removed |Added
Version|10.1-RELEASE|10.2-RELEASE
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Chris Platts changed:
What|Removed |Added
CC||chris.pla...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
--- Comment #3 from patpro ---
(In reply to patpro from comment #2)
apparently hint.ahci.0.msi=0 did not help, so I removed this setting. And about
4 weeks later, my box had a new freeze.
Currently it runs 10.1-RELEASE-p19, on a Supermicro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
patpro changed:
What|Removed |Added
CC||freebsd...@patpro.net
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
biotin changed:
What|Removed |Added
CC||afg...@yandex.com
--- Comment #1 from bio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201194
Bug ID: 201194
Summary: Kernel: ahcich: Timeout in slot
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Aff
30 matches
Mail list logo
