blue balls, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
** Tags added: bios-outdated-2205 needs-upstream-testing
** Description changed:
I started a compilation of the Linux kernel with make and after about 3
minutes I stopped it with Ctrl+C
and restarted with
make -j
to enable parallel compilation.
After a few seconds the system
One way to avoid the freeze is to limit the number of parallel
compilations taking place by using:
make -j N
In my case since I have a dual core CPU, N is equal to 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the system you are using to perform the compile is running
out of memory. The kernel is performing oom kills to free memory.
Are you able to add additional memory to the build system? 2G may not
be enough for parallel builds.
You may also want to run a memtest on the system.
--
Joseph, I did ran memtest several times on my system with no problems
found.
I understand that the kernel kills processes to free memory but is it
normal behavior that it should freeze completely the system ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943516
Title:
Linux freeze when compiling
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943516
Title:
Linux freeze when compiling
To manage notifications about this bug go to:
After rebooting, I did a
make -j
again and after a few seconds the system freezed again !
So it seems that this is not a one time event.
I'll try to find out more.
I appreciate any pointers about how to proceed. Is it possible to activate
some form of kernel logging to find out where
Are you able to access any of the other ttys when the system locks up?
This can be done with the key combination: CNTL ALT + f1
** Tags removed: needs-upstream-testing
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
There is some info here for capturing further data:
https://help.ubuntu.com/community/DebuggingSystemCrash
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To Joseph: thanks I'll take a look.
No, the system doesn't respond to any Ctrl+Alt+Fn nor to Ctrl+Alt+Del.
Also it doesn't respond to pressing the power button quickly for 1-2 seconds
- if I keep it pressed for about 5 seconds, the power is cut off.
--
You received this bug notification
I reproduced the bug again, this time with another computer connected
through ssh as described in
https://help.ubuntu.com/community/DebuggingSystemCrash
On one terminal I had a cat /proc/kmsg and on another tail -f
/var/log/syslog.
When the first computer crashed, it still responded to
Here is last lines displayed by the command
tail -f /var/log/syslog
As I said before it's not the full output, just the last few hundred
lines.
I hope this is easy to solve as on my computer it happens every time I do the
make -j on the Linux kernel sources.
I run Linux 10.04 with all
** Description changed:
- I started a compilation of the Linux kernel with make and after about 3
minutes I stopped it with Ctrl+C
- and restarted with
-make -j
+ I started a compilation of the Linux kernel with make and after about 3
minutes I stopped it with Ctrl+C
+ and restarted with
14 matches
Mail list logo
