I was able to compile the latest public karmic 32 bit generic kernel
with the patch. When I have used that kernel I was not able to see
anymore the reported problem. I would say that the fix was working for
me.
Can someone tell me when could this patch appear on an average user desktop?
I would b
to Pekka:
If you have seen the above discussion then there was this link about the
nx-emulation:
https://wiki.ubuntu.com/Security/Features#Non-Exec%20Memory
If you read it you will see that the generic-pae kernel is also using the
nx-emulation if your processor does not support "nx".
As far as
broken the next one:
* 2.6.30-3.4
So it seems with this release came the change that broke it.
Changes:
http://launchpadlibrarian.net/26403381/linux_2.6.30-3.4_i386.changes
--
Random segfaults when using ld.so explicitly to start a program
https://bugs.launchpad.net/bugs/452175
You received this
Public bug reported:
It seems that memory allocation fails occasionally, when an optional
(non-standard, but legal) startup method is used to execute a binary.
Our application requires that method (scratchbox2) so that's why we
found it.
Environment:
-
Ubuntu 9.10 Karmic Koala 32b
Public bug reported:
Binary package hint: ktechlab
When I run the following program in ktechlab, I got a SIGSEGV. Usually
not for the first time but for the 2nd or 3rd.
Program:
processor p16f628
include
banksel T2CON
movlw 0x04
movwf T2CON
loop
I have the same problem with fuse-utils 2.5.3-2.1ubuntu4. I also have my own
kernel with fuse support compiled in statically, and so obviously no fuse
module.
Is there any progress on this bug?
--
fuse-utils 2.5.3-2.1ubuntu3 installation (edgy) crashes in post installation
phase
https://launc
I have updated the BIOS. Thank you for the help.
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
# SMBIOS implementations newer than version 2.8 are not
# fully supported by this version of dmidecode.
1101
# SMBIOS implementations newer than version 2.8 are not
# fully suppo
Unfortunately, I can see this warning with the 4.2.0-16 kernel, as well:
Oct 30 07:56:24 fozzy kernel: [ 1314.912537] WARNING: CPU: 0 PID: 0 at
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11100
intel_check_page_flip+0xfc/0x110 [i915]()
Oct 30 07:56:24 fozzy kernel: [ 131
Public bug reported:
I see warnings similar to this occasionally in the dmesg output.
I first noticed it, when the system refused to put load on all but one core,
and I tried to find the reason.
But it happened again a few times, and I did not notice that effect (or any).
I do not know the trigge
I tried the 4.3-rc6 version: it did boot, but I saw the screen flickering after
any change on it.
I saw these in the logs:
Oct 24 14:32:30 fozzy kernel: [1.125622] i915 :00:02.0: Direct firmware
load for i915/skl_dmc_ver1.bin failed with error -2
Oct 24 14:32:30 fozzy kernel: [1.1256
I just upgraded to 15.10. The provided kernel, 4.2.0-16-generic, works
fine so far. If the warning happens to come, it must come very rarely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505242
Titl
11 matches
Mail list logo
