On Sat, Dec 13, 2014 at 01:13:04AM +0100, Guido Falsi wrote:
On 12/10/14 09:58, Guido Falsi wrote:
On 12/10/14 09:52, Konstantin Belousov wrote:
On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote:
[...]
--- trap 0xc, tip = 0x8056834d, rsp = 0xfe022ed8f6b0, rbp =
On 12/13/14 11:26, Konstantin Belousov wrote:
On Sat, Dec 13, 2014 at 01:13:04AM +0100, Guido Falsi wrote:
On 12/10/14 09:58, Guido Falsi wrote:
On 12/10/14 09:52, Konstantin Belousov wrote:
On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote:
[...]
--- trap 0xc, tip =
On 12/10/14 09:58, Guido Falsi wrote:
On 12/10/14 09:52, Konstantin Belousov wrote:
On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote:
[...]
--- trap 0xc, tip = 0x8056834d, rsp = 0xfe022ed8f6b0, rbp =
0xfe022ed8f6e0 ---
sbappendstream_locked() at
2014-12-09 23:39 GMT+01:00 Guido Falsi m...@madpilot.net:
Hi,
I've experienced a hard lockup on head r275563, amd64.
The hardware is a laptop with an intel graphics card.
If any further info is required just ask.
I had just launched a virtualbox VM with Windows 7, the system locked up
On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote:
Hi,
I've experienced a hard lockup on head r275563, amd64.
The hardware is a laptop with an intel graphics card.
If any further info is required just ask.
I had just launched a virtualbox VM with Windows 7, the system
On 12/10/14 09:52, Konstantin Belousov wrote:
On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote:
Lock order reversal: (sleepable after non-sleepable)
1st 0xf8000874da90 so_snd (so_snd) @
/usr/src/sys/kern/uipc_sockbuf.c:666
2nd 0xf80057ff20a0 drmslk (drmslk) @
Hi,
I've experienced a hard lockup on head r275563, amd64.
The hardware is a laptop with an intel graphics card.
If any further info is required just ask.
I had just launched a virtualbox VM with Windows 7, the system locked up
just after the startup sound was played in the VM, X11
Not sure if this is a known issue since I don't usually use UFS.
Yesterday I put current on an acer laptop with an i3 processor/4GB RAM
with UFS file system on a OCZ vertex 2 SSD and trim enabled via tunefs.
Below is the dmesg along with the LOR message at the bottom. I can
provide more
I am going to respond to this before I forget
I had the SAME exact LOR's with ath 9300 and I reported them,
however I have since switched out motherboards and the LOR's have strangely
diapered
here is a full dmesg for a perfectly working system
FreeBSD clang version 3.3
On Mon, Aug 5, 2013 at 4:24 PM, Sam Fourman Jr. sfour...@gmail.com wrote:
I am going to respond to this before I forget
I had the SAME exact LOR's with ath 9300 and I reported them,
however I have since switched out motherboards and the LOR's have strangely
diapered
here is a full
On Mon, 5 Aug 2013, Davide Italiano wrote:
The LOR is a false positive.
See the comment in sys/ufs/ufs/ufs_dirhash.c
Also, switching motherboards is not related to this in any way. You'll
eventually hit that LOR report, unless you disabled WITNESS.
Ah, thank you Davide; sorry for the noise
11 matches
Mail list logo