search for: undiagnosable

There were no live connections. The problem what we had was more related to OS requirement for some software. This drive was not in a bad shape. On 12 July 2016 at 23:03, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 07/12/2016 09:52 AM, Hersh wrote: > >> There was some problem with our system so I re-installed the server with >> CentOS 7. Now, when I am

Hi, There was some problem with our system so I re-installed the server with CentOS 7. Now, when I am trying to run 'fdisk -l' command, it is returning a broken output. It throws this error- "fdisk: cannot open /dev/sdc: Input/output error". There are valid /dev/sdd and /dev/sde devices which are mounted and they are accessible but, somehow /dev/sdc is having a problem and

https://bugs.freedesktop.org/show_bug.cgi?id=99900 --- Comment #22 from Ilia Mirkin <imirkin at alum.mit.edu> --- "Random anything" is a wholly undiagnosable issue. 4.12.11 resolved a regression in 4.12 which caused EDID to not be read properly over DP. There have been many reports of this causing a variety of issues. Sounds like your issue is wholly unrelated to the original issue reported here as well. When in doubt, file a new bug. Marking bugs as d...

On 07/12/2016 09:52 AM, Hersh wrote: > There was some problem with our system so I re-installed the server with > CentOS 7. Now, when I am trying to run 'fdisk -l' command, it is returning > a broken output. > > It throws this error- "fdisk: cannot open /dev/sdc: Input/output error". So, your server had an undiagnosed problem, and now it reports read errors on

I tried to run fsck on /dev/sdc drive and here what I got. [root at localhost ~]# fsck /dev/sdc fsck from util-linux 2.23.2 e2fsck 1.42.9 (28-Dec-2013) fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc Could this be a zero-length partition? [root at localhost ~]# fsck /dev/sdc1 fsck from util-linux 2.23.2 e2fsck 1.42.9 (28-Dec-2013) fsck.ext2:

I tried SIS a couple years ago - I was very excited with the resulting decrease in storage requirements but the undiagnosed intermittent issues became too significant to ignore so I switched away.? Recently I was thinking about it again. The primary issue with SIS seemed to be links would be deleted even though the source attachment files and related mails still existed.? It was possible to

I'd like to (re)start a discussion on a few gotchas in FileCheck that I've noticed working on various tests in llvm's suites. This begain in a review [1], but I'll try to summarize here so it gets the right audience before decisions are made on it (so to speak). 1: https://reviews.llvm.org/D77227 The main sticking point is the abundance of checks in FileCheck tests that appear to

https://bugs.freedesktop.org/show_bug.cgi?id=101206 Bug ID: 101206 Summary: intermittent lock up after login to GNOME under wayland Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=71900 Priority: medium Bug ID: 71900 Assignee: nouveau at lists.freedesktop.org Summary: [NV40] GPU lockup and segmentation fault of Nouveau-1.0.10 on PowerMac G5 with acceleration QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

Thanks, Joseph and Johannes. I have not merged in anything, I am using the code from the repository as is. What is this -debug-only option, and to whom would I pass it? I am running our own JIT application, which uses clang to compile modules on the fly via clang::CompilerInstance::ExecuteAction(). Working on the assumption that there is a mismatch in the declared type of an OpenMP runtime

Yep, it happens three times, then crashes afterwards, since I removed the assert... arg 0: expected %struct.ident_t* got %struct.ident_t.21* value @0 = private unnamed_addr global %struct.ident_t.21 { i32 0, i32 514, i32 0, i32 0, i8* getelementptr inbounds ([23 x i8], [23 x i8]* @.str, i32 0, i32 0) }, align 8 arg 0: expected %struct.ident_t* got %struct.ident_t.21* value @1 = private

Yeah, I remember encountering that error before when getting it to pass the libomp test suite. If you have a struct named "ident_t" somewhere the compiler will rename it because of the conflict with the runtime declaration. This should be solved by casting the usage to the function type found in the definition (i.e. bitcasting a struct.ident_t.21 to struct.ident_t) which solved the

Hi, That patch was from an ongoing effort to consolidate OpenMP generation in clang. If memory serves the implementation there is still a little incomplete. It's supposed to use types from OMPConstants rather than ones it defined itself and the methods used to create the functions shouldn't need to be static. However attempting this caused a lot of errors so there might be an underlying

https://bugs.freedesktop.org/show_bug.cgi?id=92438 Bug ID: 92438 Summary: Segfault in pushbuf_kref when running the android emulator (qemu) on nv50 Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium