CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x>
May 31 05:12:27 gar kernel: watchdog: BUG: soft lockup - CPU#14 stuck
for 26s! [kworker/14:2:2123]
May 31 05:12:27 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 au
evice as follows.
Create a file (such as):
/etc/modprobe.d/snd-intel-disable-power-management.conf
Add the following line: options snd_hda_intel power_save=0
Reboot.
Hopefully this may assist.
Thanks for the suggestion.
Journal of the most recent lockup below:
May 19 23:17:01 gar CRON
; > >
>> > > > Is anyone else seeing a similar problem? What can I do to avoid
>> > > > this?
>> > > > Do we need anything else to narrow it down further?
>> > >
>> > > Only time I've seen a soft lockup was from a bad
em? What can I do to avoid
> > > > this?
> > > > Do we need anything else to narrow it down further?
> > >
> > > Only time I've seen a soft lockup was from a bad CPU. There were a
> > > bunch
> > > of them and eventually the compute
el: [drm:fw_domains_get_with_fallback [i915]]
> *ERROR* gt: timed out waiting for forcewake ack to clear.
> May 14 00:54:26 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI
> [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
> May 14 00:54:26 gar kernel: watchd
lseye, which is why I'm using
bookworm. (In bullseye, the kernel and the firmware-misc-nonfree
packages weren't recent enough).
Since it happened just twice in the last (almost) 3 months, I think I'd
need to manually trigger the cause of this lockup - any suggestions are
welcome.
Thanks for your time!
On Mon, 15 May 2023 18:30:31, David wrote:
On Mon, 2023-05-15 at 11:17 +0300, Anssi Saari wrote:
Christian Gelinek writes:
> Is anyone else seeing a similar problem? What can I do to avoid
> this?
> Do we need anything else to narrow it down further?
Only time I've seen a s
narrow it down further?
> >
> > Only time I've seen a soft lockup was from a bad CPU. There were a
> > bunch
> > of them and eventually the computer hung. Going back to the slow
> > plodding Celeron fixed all issues. Except CPU performance of course.
>
> It
On 15/05/2023 02:13, Christian Gelinek wrote:
It seems to be an issue with the i915 driver, potentially triggered by
snd_hda_intel.
Yes indeed that looks like it, to my untrained eye.
Does it happen on Debian Stable (bullseye) also?
I have one laptop with Intel CPU, Intel integrated graphics, o
On Mon, 2023-05-15 at 11:17 +0300, Anssi Saari wrote:
> Christian Gelinek writes:
>
> > Is anyone else seeing a similar problem? What can I do to avoid
> > this?
> > Do we need anything else to narrow it down further?
>
> Only time I've seen a soft lock
Christian Gelinek writes:
> Is anyone else seeing a similar problem? What can I do to avoid this?
> Do we need anything else to narrow it down further?
Only time I've seen a soft lockup was from a bad CPU. There were a bunch
of them and eventually the computer hung. Going back
aint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:26 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck
for 26s! [kworker/15:1:233]
May 14 00:54:26 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec
lback [i915]]
*ERROR* gt: timed out waiting for forcewake ack to clear.
May 14 00:54:26 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:26 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck
for 26s! [kw
Apr 10 07:50:28 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck
for 26s! [kworker/15:2:1033]
Apr 10 07:50:28 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4
dns_resolver nfs lockd grace fscache netfs rfkill qrtr
On 4/20/22 00:43, David Christensen wrote:
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
I found my spare mouse last week and swapped out the mouse I have been
using for the past few years. The problems went away. The bad mo
On 4/21/2022 5:28 PM, David Christensen wrote:
On 4/21/22 13:50, David Wright wrote:
On Thu 21 Apr 2022 at 01:02:56 (-0700), David Christensen wrote:
What package do I file a bug report against?
It's not clear from reading your posts (unless it requires some
correlation, on my part, of your
On Thu, Apr 21, 2022 at 05:28:35PM -0700, David Christensen wrote:
> On 4/21/22 13:50, David Wright wrote:
> > On Thu 21 Apr 2022 at 01:02:56 (-0700), David Christensen wrote:
>
> > > What package do I file a bug report against?
> >
> > It's not clear from reading your posts (unless it requires s
On 4/21/22 13:50, David Wright wrote:
On Thu 21 Apr 2022 at 01:02:56 (-0700), David Christensen wrote:
What package do I file a bug report against?
It's not clear from reading your posts (unless it requires some
correlation, on my part, of your observations) whether you have
had storms on US
On Thu 21 Apr 2022 at 01:02:56 (-0700), David Christensen wrote:
> On 4/20/22 15:31, David Christensen wrote:
>
> > The rear USB 2.0 ports are down right now. Are there any commands
> > I should run before rebooting (to test if the problem is hardware
> > software)?
>
>
> I ran the desktop with
On 4/20/22 15:31, David Christensen wrote:
The rear USB 2.0 ports are down right now. Are there any commands I
should run before rebooting (to test if the problem is hardware software)?
I ran the desktop with the keyboard and mouse connected directly to the
rear USB 3.0 ports. I did not se
On 4/20/22 14:40, Felix Miata wrote:
David Christensen composed on 2022-04-20 14:14 (UTC-0700):
Can you suggestion and commands to run that might provide clues?
Other than switching between use of DDX display drivers (intel, nouveau) and DIX
driver (modesetting, which supports: AMD, Intel, N
David Christensen composed on 2022-04-20 14:14 (UTC-0700):
> Felix Miata wrote:
>> There are two different technologies for X display drivers.
>> xserver-xorg-video-intel uses the older, DDX. It hasn't had an official
>> release in
>> nearly a decade. Unofficially it's in maintenance mode. The n
On 4/20/22 11:23, Felix Miata wrote:
David Christensen composed on 2022-04-20 10:31 (UTC-0700):
1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945
chipset (Intel® 82945GM Graphics and Memory Controller). I believe
Debian uses the xserver-xorg-video-intel driver.
3. Des
David Christensen composed on 2022-04-20 10:31 (UTC-0700):
> 1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945
> chipset (Intel® 82945GM Graphics and Memory Controller). I believe
> Debian uses the xserver-xorg-video-intel driver.
> 3. Desktop with Intel DQ67SW motherboa
On 4/20/22 4:51 AM, songbird wrote:
Dieter Rohlfing wrote:
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13 (kernel 4.19.0-0.bpo.
On 4/20/22 3:43 AM, Cindy Sue Causey wrote:
On 4/20/22, Dieter Rohlfing wrote:
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13
On 4/20/22 2:23 AM, Dieter Rohlfing wrote:
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE de
Dieter Rohlfing wrote:
> Am Wed, 20 Apr 2022 00:43:35 -0700
> schrieb David Christensen :
>
>>I have been experiencing intermittent storms of random keyboard and
>>mouse GUI events over the past year or more:
>
> Same for me.
>
> System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) ru
On 4/20/22, Dieter Rohlfing wrote:
> Am Wed, 20 Apr 2022 00:43:35 -0700
> schrieb David Christensen :
>
>>I have been experiencing intermittent storms of random keyboard and
>>mouse GUI events over the past year or more:
>
> Same for me.
>
> System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFC
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
>I have been experiencing intermittent storms of random keyboard and
>mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running
on an ASRock DeskMini H110M.
On 4/20/22 12:43 AM, David Christensen wrote:
debian-user:
I have an SSD with Debian:
2022-04-19 23:24:11 dpchrist@tinkywinky ~
$ cat /etc/debian_version ; uname -a
9.13
Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07)
x86_64 GNU/Linux
I have been experiencing intermitte
debian-user:
I have an SSD with Debian:
2022-04-19 23:24:11 dpchrist@tinkywinky ~
$ cat /etc/debian_version ; uname -a
9.13
Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07)
x86_64 GNU/Linux
I have been experiencing intermittent storms of random keyboard and
mouse GUI eve
David Christensen composed on 2021-12-27 21:05 (UTC-0800):
> I moved the Debian 10 system disk to an Intel DQ67SW motherboard with an
> Intel Core i7-2600S processor and Intel HD Graphics 2000. It played ~90
> minutes of Amazon video flawlessly. I believe Debian 10 is now using
> the i915 gra
On 12/26/21 9:34 PM, David Christensen wrote:
On 12/26/21 9:13 PM, Andrew M.A. Cater wrote:
David - there's a very similar set of queries on debian-laptop at the
moment
also about a Dell E6520. Are you using one that has Nvidia graphics
with the
Nvidia N4200M?
I moved the Debian 10 system
On 12/26/21 9:13 PM, Andrew M.A. Cater wrote:
David - there's a very similar set of queries on debian-laptop at the moment
also about a Dell E6520. Are you using one that has Nvidia graphics with the
Nvidia N4200M?
Yes.
2021-12-26 21:27:09 root@laalaa ~
# cat /etc/debian_version ; uname -a
On Sun, Dec 26, 2021 at 07:45:15PM -0800, David Christensen wrote:
> On 12/25/21 12:48 PM, David Christensen wrote:
> > On 12/5/21 2:46 AM, Georgi Naplatanov wrote:
> > >
> > >
> > > On 12/5/21 05:47, David Christensen wrote:
> > > > debian-user:
> > > >
> > > > I installed debian-live-11.1.0-am
Kamil Jońca composed on 2021-02-12 15:53 (UTC+0100):
> And today, lockup happened with smplayer (with mpv under the hood) so it
> is more general issue with X/kernel/hardware. :(
I would continue using the DV
Kamil Jońca writes:
>
> Yesterday this lockup happens with monitor connected by DVI. So my
> theory that these lockups are related to DVI/HDMI connection became
> untrue.
And today, lockup happened with smplayer (with mpv under the hood) so it
is more general issue with X/kernel/har
On Sat, 06 Feb 2021 12:38:30 +0100
Kamil Jońca wrote:
> >
> > Is your HD 5450 passively cooled? If yes, you might try placing a
> > case fan
>
> Yes. I try to avoid fans, but I think I have no choice.
If noise is your objection to fans, have some reviews of quiet
equipment: https://silentpcre
Felix Miata writes:
> Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):
>
>> Yesterday this lockup happens with monitor connected by DVI. So my
>> theory that these lockups are related to DVI/HDMI connection became untrue.
>> I will try to investigate further. Again
Kamil Jońca writes:
> Felix Miata writes:
>
>> Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):
>>
>>> Yesterday this lockup happens with monitor connected by DVI. So my
>>> theory that these lockups are related to DVI/HDMI connection became untrue.
&
Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):
> Yesterday this lockup happens with monitor connected by DVI. So my
> theory that these lockups are related to DVI/HDMI connection became untrue.
> I will try to investigate further. Again thanks to Felix for his
> efforts so far
ted monitor via hdmi output (instead old one)
> And strange things starts happend.
> When I tried to play movie with vlc there were hand for few seconds and
> then monitor "resets", and there were only black rectanle - have to
> reopen movie.
>
Yesterday this lockup happ
Felix Miata writes:
> Kamil Jońca composed on 2021-02-04 07:14 (UTC+0100):
>
>> Felix Miata writes:
>
>>> How quickly after video start does this happen, right away, or only after a
>>> while?
>
>> when I launch vlc with list of movie files. vlc "waits" (and then there
>>
>> []
>
Kamil Jońca composed on 2021-02-04 07:14 (UTC+0100):
> Felix Miata writes:
>> How quickly after video start does this happen, right away, or only after a
>> while?
> when I launch vlc with list of movie files. vlc "waits" (and then there
>
> []
[ I replied yesterday, but I cannot see this on list ]
Felix Miata writes:
> Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100):
> ...
>> kjonca@alfa:~%uname -a
>> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64
>> GNU/Linux
>> kjonca@alfa:~%cat /etc/debian_version
>> bu
Felix Miata writes:
> Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100):
> ...
>> kjonca@alfa:~%uname -a
>> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64
>> GNU/Linux
>> kjonca@alfa:~%cat /etc/debian_version
>> bullseye/sid
>
>> This is sid upgraded ~ weekly.
>
> How
Kamil Jońca writes:
> Felix Miata writes:
>
>> Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100):
>> ...
>>> kjonca@alfa:~%uname -a
>>> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64
>>> GNU/Linux
>>> kjonca@alfa:~%cat /etc/debian_version
>>> bullseye/sid
>>
>>> This
Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100):
...
> kjonca@alfa:~%uname -a
> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 GNU/Linux
> kjonca@alfa:~%cat /etc/debian_version
> bullseye/sid
> This is sid upgraded ~ weekly.
How quickly after video start does this happ
Felix Miata writes:
> Kamil Jońca composed on 2021-01-28 17:58 (UTC+0100):
>
>> When I back to DVI monitor everthing work without errors.
>
> Did you find a solution?
No. I back to my old DVI monitor. :(
>
> Which Debian? I too have a PC with HD 5450 Radeon. I could try to reproduce if
> knowin
Kamil Jońca composed on 2021-01-28 17:58 (UTC+0100):
> When I back to DVI monitor everthing work without errors.
Did you find a solution?
Which Debian? I too have a PC with HD 5450 Radeon. I could try to reproduce if
knowing what to boot is what I have installed.
--
Evolution as taught in publi
Dan Ritter writes:
> Kamil Jo?ca wrote:
>>
>> There is desktop box with sid.
>>
>> sudo lspci|grep -i vga
>> 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
>> Cedar [Radeon HD 5000/6000/7350/8350 Series]
>>
>> So far I have monitor connected via DVI
>>
>> Recently
Kamil Jo?ca wrote:
>
> There is desktop box with sid.
>
> sudo lspci|grep -i vga
> 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Cedar [Radeon HD 5000/6000/7350/8350 Series]
>
> So far I have monitor connected via DVI
>
> Recently I connected monitor via hdmi out
n]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
alfa kernel: [114335.021950] radeon :08:00.0: ring 5 stalled for more than
10252msec
alfa kernel: [114335.021959] radeon :08:00.0: GPU lockup (current fence id
0x0002112c last fence id 0x00021130 on ring 5)
alfa kernel: [114
Am Montag, 12. Oktober 2020, 17:33:46 CEST schrieb Alexander V. Makartsev:Got
into a
similar problem for years. Suddenly keyboard (the internal of my notebook)
stopped and
I had to restart the window manager.
This happened only in plasma5, not in LXDE or other window manager.
I read in some
On 12.10.2020 17:18, Thomas George wrote:
> 10/12/20. Mouse working perfectly since reboot on 10/6/20 but this
> morning no response from keyboard. Tried ctl-alt-f1 and ctl-alt-f7 but
> no response. Not able to switch workplaces. Continued working in the
> current workspace using the mouse only. Ve
10/12/20. Mouse working perfectly since reboot on 10/6/20 but this
morning no response from keyboard. Tried ctl-alt-f1 and ctl-alt-f7 but
no response. Not able to switch workplaces. Continued working in the
current workspace using the mouse only. Verified mouse and keyboard
batteries both at 50
On 10/6/20 1:27 PM, Thomas George wrote:
Mouse clicks don't work though mouse moves the pointer.
This happens infrequently, once in a day or two. I am using two pc's, a
raspberrypi and a Ubuntu Studio each with its own Logitech usb keyboard
and have experienced this problem on both systems.
On Tue, 6 Oct 2020 14:27:10 -0400
Thomas George wrote:
> Is there a known solution?
I don't know about a known solutions, but a workaround might be
ctl-alt-f1, followed by ctl-alt-f7. I think this will force X to
re-initialize some things.
--
Does anybody read signatures any more?
https://cha
Thomas George wrote:
> Mouse clicks don't work though mouse moves the pointer.
>
> This happens infrequently, once in a day or two. I am using two pc's, a
> raspberrypi and a Ubuntu Studio each with its own Logitech usb keyboard and
> have experienced this problem on both systems.
I noticed this
On 07-10-2020 07:05, to...@tuxteam.de wrote:
> On Tue, Oct 06, 2020 at 04:11:39PM -0400, Thomas George wrote:
>> The problem is extremely intermittent. I use the mouse many times a
>> day with no problem. Then unexpectedly the click does not work.
Have you even tried another mouse?
> I've seen
On Tue, Oct 06, 2020 at 04:11:39PM -0400, Thomas George wrote:
> The problem is extremely intermittent. I use the mouse many times a
> day with no problem. Then unexpectedly the click does not work.
I've seen several mice fail in exactly this way, with a mechanical
problem. Not saying that this mu
The problem is extremely intermittent. I use the mouse many times a day
with no problem. Then unexpectedly the click does not work.
On 10/6/20 3:58 PM, to...@tuxteam.de wrote:
On Tue, Oct 06, 2020 at 02:27:10PM -0400, Thomas George wrote:
Mouse clicks don't work though mouse moves the pointer.
On Tue, Oct 06, 2020 at 02:27:10PM -0400, Thomas George wrote:
> Mouse clicks don't work though mouse moves the pointer.
>
> This happens infrequently, once in a day or two. I am using two
> pc's, a raspberrypi and a Ubuntu Studio each with its own Logitech
> usb keyboard and have experienced thi
On Tuesday 06 October 2020 14:27:10 Thomas George wrote:
> Mouse clicks don't work though mouse moves the pointer.
>
> This happens infrequently, once in a day or two. I am using two pc's,
> a raspberrypi and a Ubuntu Studio each with its own Logitech usb
> keyboard and have experienced this prob
Mouse clicks don't work though mouse moves the pointer.
This happens infrequently, once in a day or two. I am using two pc's, a
raspberrypi and a Ubuntu Studio each with its own Logitech usb keyboard
and have experienced this problem on both systems.
I have tried to recover with various keyb
Hi,
so far the i915.enable_rc6=0 option seems to have worked. No system hangs
with it so far. Haven't got a feel if battery run-time is worse, but the
difference probably isn't that bad.
Ondrej G.
On Wed, Feb 21, 2018 at 8:09 PM, Ondřej Grover
wrote:
> Hi Henning,
> thanks for the tip.
>
> How
Hi Henning,
thanks for the tip.
However, I've been experiencing this issue already before the
spectre/meltdown bunch hit the fan.
It does sound like it a bit, but likely is some different HW stuff.
For now I'm experimenting with i915.enable_rc6=0. I hope it won't bog down
the battery run-time too
On Wed, Feb 21, 2018 at 09:51:58AM +0100, Ondřej Grover wrote:
> Hello,
>
> I need help debugging random total system lock-ups.
> This is a notebook Acer Aspire V3-572G-78A running Debian Stretch with
> the 4.9.0-5-amd64 kernel.
>
> When running on battery (does not happen on AC power), usually a
Hello,
I need help debugging random total system lock-ups.
This is a notebook Acer Aspire V3-572G-78A running Debian Stretch with
the 4.9.0-5-amd64 kernel.
When running on battery (does not happen on AC power), usually after
resuming from RAM, after some rather random time (can be a few minutes t
Folks,
I have three servers that, when I run apt upgrade or apt dist-upgrade and
any kvm's are running, the system freezes. When it does, the console shows
some daemon is reloading, but I have been unable to ascertain which daemon
-- it never actually gets to the name of the daemon that is reload
Hi
For a while now I'm seeing what looks like the same problem with Jessie.
Typically after a few hours of using X the system freezes with a "BUG:
soft lockup". For a few minutes I can still log in through ssh, but then
that stops working as well and the system stops responding to
On Sat, 30 Dec 2017 11:47:23 +0100
Alex ARNAUD wrote:
> Hello all,
>
> I'm helping a user to figure out an issue. On her syslog file I could
> find:
> > BUG: soft lockup - CPU#0 stuck for 22s!
>
>
> - Package version of firmware-amd-graphics: 20161130-3~b
Alex ARNAUD wrote:
> Her configuration is that one:
> - Debian Jessie 8.10
>
> - Kernel : Linux colossus 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3
> (2017-12-13) x86_64 GNU/Linux
> - Kernel package: linux-image-amd64 version "3.16+63"
>
> - Xorg version: 1.16.4
> - Package version of xserver-xorg-c
Hello all,
I'm helping a user to figure out an issue. On her syslog file I could find:
BUG: soft lockup - CPU#0 stuck for 22s!
And the following stack trace:
Stack:
Dec 28 14:34:09 colossus kernel: [946492.108011] a041af86
880429a20728 a04a801d 0001
D
Mini Trader wrote:
> Java 7 rarely has issues on Java 8 and if they do it's a program error not
> system. At this point I'll go back to Jessie or Ubuntu 16.
I don't know how deep you are in java, but IMO it really depends. It depends
on how the program is designed and most of all how it is compil
Java 7 rarely has issues on Java 8 and if they do it's a program error not
system. At this point I'll go back to Jessie or Ubuntu 16.
Thanks for the feedback.
On Sat, Jul 1, 2017 at 6:41 PM deloptes wrote:
> Mini Trader wrote:
>
> > I tried oracles version as well and same response. Is there an
Mini Trader wrote:
> I tried oracles version as well and same response. Is there any sort of
> utility that can be used to sandbox this and see what is going on?
>
If a java program was compiled and designed to run on specific version it
could be that it causes problems on higher version - espec
I tried oracles version as well and same response. Is there any sort of
utility that can be used to sandbox this and see what is going on?
Any log files other than kernlog or syslog?
On Sat, Jul 1, 2017 at 4:42 PM deloptes wrote:
> Mini Trader wrote:
>
> > My last two cents on this are that the
Mini Trader wrote:
> My last two cents on this are that the vCenter consoles shows the machine
> going to 100% CPU. I've tried even executing the java process with the
> nice command to see if this could throttle the CPU.
>
> Whatever it is that this java process is doing is completely throwing
ooks to
>> be
>> > a java application.
>> >
>> > When connecting to the app from certain devices the entire system will
>> > lockup inside an ESXi VM.
>> >
>> > There doesn't appear to be any errors. The system just
ul 1, 2017 at 10:22 AM, deloptes wrote:
> Mini Trader wrote:
>
> > I've installed Debian 9/Stetch and am having issues with what looks to be
> > a java application.
> >
> > When connecting to the app from certain devices the entire system will
> > lockup ins
Mini Trader wrote:
> I've installed Debian 9/Stetch and am having issues with what looks to be
> a java application.
>
> When connecting to the app from certain devices the entire system will
> lockup inside an ESXi VM.
>
> There doesn't appear to be any errors
I've installed Debian 9/Stetch and am having issues with what looks to be a
java application.
When connecting to the app from certain devices the entire system will
lockup inside an ESXi VM.
There doesn't appear to be any errors. The system just locks up, no
console, no IP nothing
I've installed Debian 9/Stetch and am having issues with what looks to be a
java application.
When connecting to the app from certain devices the entire system will
lockup inside an ESXi VM.
There doesn't appear to be any errors. The system just locks up, no more
IP nothing works.
firmware update won't fix
> this particular problem. But it will fix a few others that cause
> unpredictable behavior.
So far so good (knock on wood); I think this has solved the problem for
me. It has been two days now that I don't see any kind of lockup in the
logs, which are now much smaller in size!
Thank you,
--
Seb
On Sat, 07 May 2016, Seb wrote:
> On Sat, 7 May 2016 17:55:08 -0300,
> Henrique de Moraes Holschuh wrote:
> > On Fri, 06 May 2016, Seb wrote:
> >> May 5 22:48:19 otaria kernel: [ 6706.415698] Hardware name: LENOVO
> >> 10FWCTO1WW/SKYBAY, BIOS FWKT38A 01/28/2016
>
> > Please update that BIOS. It
On Sat, 7 May 2016 17:55:08 -0300,
Henrique de Moraes Holschuh wrote:
> On Fri, 06 May 2016, Seb wrote:
>> May 5 22:48:19 otaria kernel: [ 6706.415698] Hardware name: LENOVO
>> 10FWCTO1WW/SKYBAY, BIOS FWKT38A 01/28/2016
> Please update that BIOS. It is too old (and no, I am *not* joking).
A fe
On Fri, 06 May 2016, Seb wrote:
> May 5 22:48:19 otaria kernel: [ 6706.415698] Hardware name: LENOVO
> 10FWCTO1WW/SKYBAY, BIOS FWKT38A 01/28/2016
Please update that BIOS. It is too old (and no, I am *not* joking).
People, as a rule of thumb: if it has an Intel Skylake processor or newer
(6th
ssor (i7-6700 @ 3.4 GHz). The graphics card (GT-720) on nouveau
> or
> proprietary Nvidia drivers may also be suspect, as I've always had
> issues with Nvidia cards in my older systems (I had no choice with
> this
> new system).
>
> Here's a more encompassing
with this
new system).
Here's a more encompassing excerpt of the lockup in my first message, in
case something catches attention:
---<cut here---start--->---
May 5 22:48:19 otaria kernel: [ 6706.415657] NMI watchdog: Watchdog detected
On Sat, May 7, 2016 at 7:43 PM Sven Arvidsson wrote:
> On Fri, 2016-05-06 at 21:02 -0500, Seb wrote:
> > For a few weeks, I'm experiencing complete system freezes that occur
> > nearly every day and seemingly at random or not linked to any easily
> > identifiable activity. This is a new system (
On Fri, 2016-05-06 at 21:02 -0500, Seb wrote:
> For a few weeks, I'm experiencing complete system freezes that occur
> nearly every day and seemingly at random or not linked to any easily
> identifiable activity. This is a new system (Lenovo ThinkCentre
> M800),
Another thought: Is the intel-micr
and
> looking at /var/log/kern.log or /var/log/syslog shows soft or hard
> lockups (excerpt of a hard lockup example):
Yeah, hard crashes sucks.
Are all the logs similar? The call trace in that log seems very short.
Is this a new install or did you have a previous working setup?
Trying newer a
ry day and seemingly at random or not linked to any easily
identifiable activity. This is a new system (Lenovo ThinkCentre M800),
so I doubt hardware is the culprit. Checking the output of dmesg, and
looking at /var/log/kern.log or /var/log/syslog shows soft or hard
lockups (excerpt of a hard lock
27;ve been getting random lockups of the machine -- no
> keyboard or mouse functionality. Programs running in the background at the
> time of the lockup continue to run, and I can ssh into the box when it's
> locked up.
FYI in case you didn't notice this later thread and replies:
d or mouse functionality. Programs running in the background at the
time of the lockup continue to run, and I can ssh into the box when it's
locked up.
At first I thought it might have been a program that was causing the
problems, but when ssh'ed into the box and after trying to kill a
Is there an alternative to KDE Connect elsewhere?
Is there a non-KDE substitute that makes it easy to create a WiFi
hotspot/access point connection? (NetworkManager cannot do this in
non-KDE environments in Debian. It can under GNOME in Fedora.)
--
Udyant Wig
On 10/11/2015 1:06 PM, Renaud (Ron) OLGIATI wrote:
On Sun, 11 Oct 2015 20:55:56 +0300
moxalt wrote:
Basically, don't use GDM with KDE, and don't run KDE on systems that are short
of RAM. Or at all.
Yes, better use XFCE or LXDE, which are not bloated messes like KDE or Gnome.
Cheers,
Ron
Yes, and after getting it working, didn't care for KDE anyway and
uninstalled it. Now it's just Xfce, dwm, and cinammon.
Andrea
1 - 100 of 315 matches
Mail list logo
