Page 1 of 1
Kernel 3.1.5-porteus i486 ready for testing
Posted: 17 Dec 2011, 10:36
by kalo86
Hello dear Community,
about 1 month ago I bought a new netbook, the Acer Aspire One 522.
It has the AMD C-50 processor with the integrated AMD Radeon HD 6250 GPU and I had a lot of freezes with 3.0.X and 3.1.X kernels.
I had freezes with and without ati proprietary graphical drivers.
Yetserday I compiled the linux
kernel 3.1.5 for Porteus v1.1 rc2 i486 (
without ndiswrapper) and with this new release I am not having freezes.
Maybe the problem is solved? I hope!
I uploaded a RAR archive containing 4 files:
- vmlinuz
- initrd.xz
- 000-kernel-3.1.5.xzm
- crippled_3.1.5.xzm
This is a vanilla kernel compiled with the config of Porteus v1.1 rc2 i486 and with aufs patch.
Download:
http://www.mediafire.com/?y3sk1slj938haej
Please post here your experience with this new kernel, thanks.
Regards,
kalo86
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 17 Dec 2011, 14:33
by Hamza
Is it possible to post some details of this wonderful works
?
Example :
Patch Used:
-Zen Kernel 2.6.32
Kernel config:
-No ndiswrapper
etc..
Thanks.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 17 Dec 2011, 15:01
by kalo86
I used only the aufs patch.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 17 Dec 2011, 15:37
by Hamza
Ok, It appear, this is related to an issue reported in ChangeLog of Kernel 3.1.5
I am sure the issue is related to this..KVM is mostly used for Remote Control on Dedicated Servers
Code: Select all
commit 3e31d12fa35d8328128ef672a933ab6b8e09e10b
Author: Robert Richter <robert.richter@amd.com>
Date: Fri Oct 7 16:31:46 2011 +0200
oprofile: Fix crash when unloading module (hr timer mode)
commit 87121ca504fd1d963a66b3fb0c72054b0fd9a177 upstream.
Oprofile may crash in a KVM guest while unlaoding modules. This
happens if oprofile_arch_init() fails and oprofile switches to the hr
timer mode as a fallback. In this case oprofile_arch_exit() is called,
but it never was initialized properly which causes the crash. This
patch fixes this.
oprofile: using timer interrupt.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
PGD 41da3f067 PUD 41d80e067 PMD 0
Oops: 0002 [#1] PREEMPT SMP
CPU 5
Modules linked in: oprofile(-)
Pid: 2382, comm: modprobe Not tainted 3.1.0-rc7-00018-g709a39d #18 Advanced Micro Device Anaheim/Anaheim
RIP: 0010:[<ffffffff8123c226>] [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
RSP: 0018:ffff88041de1de98 EFLAGS: 00010296
RAX: 0000000000000000 RBX: ffffffffa00060e0 RCX: dead000000200200
RDX: 0000000000000000 RSI: dead000000100100 RDI: ffffffff8178c620
RBP: ffff88041de1dea8 R08: 0000000000000001 R09: 0000000000000082
R10: 0000000000000000 R11: ffff88041de1dde8 R12: 0000000000000080
R13: fffffffffffffff5 R14: 0000000000000001 R15: 0000000000610210
FS: 00007f9ae5bef700(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000008 CR3: 000000041ca44000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 2382, threadinfo ffff88041de1c000, task ffff88042db6d040)
Stack:
ffff88041de1deb8 ffffffffa0006770 ffff88041de1deb8 ffffffffa000251e
ffff88041de1dec8 ffffffffa00022c2 ffff88041de1ded8 ffffffffa0004993
ffff88041de1df78 ffffffff81073115 656c69666f72706f 0000000000610200
Call Trace:
[<ffffffffa000251e>] op_nmi_exit+0x15/0x17 [oprofile]
[<ffffffffa00022c2>] oprofile_arch_exit+0xe/0x10 [oprofile]
[<ffffffffa0004993>] oprofile_exit+0x13/0x15 [oprofile]
[<ffffffff81073115>] sys_delete_module+0x1c3/0x22f
[<ffffffff811bf09e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff8148070b>] system_call_fastpath+0x16/0x1b
Code: 20 c6 78 81 e8 c5 cc 23 00 48 8b 13 48 8b 43 08 48 be 00 01 10 00 00 00 ad de 48 b9 00 02 20 00 00 00 ad de 48 c7 c7 20 c6 78 81
89 42 08 48 89 10 48 89 33 48 89 4b 08 e8 a6 c0 23 00 5a 5b
RIP [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
RSP <ffff88041de1de98>
CR2: 0000000000000008
---[ end trace 06d4e95b6aa3b437 ]---
Signed-off-by: Robert Richter <robert.richter@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This can also be related to this report
Code: Select all
commit a6ff8af2ed1af704e400b558b2811ce7a350d2eb
Author: Robert Richter <robert.richter@amd.com>
Date: Mon Oct 10 16:21:10 2011 +0200
oprofile, x86: Fix crash when unloading module (nmi timer mode)
commit 97f7f8189fe54e3cfe324ef9ad35064f3d2d3bff upstream.
If oprofile uses the nmi timer interrupt there is a crash while
unloading the module. The bug can be triggered with oprofile build as
module and kernel parameter nolapic set. This patch fixes this.
oprofile: using NMI timer interrupt.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
PGD 42dbca067 PUD 41da6a067 PMD 0
Oops: 0002 [#1] PREEMPT SMP
CPU 5
Modules linked in: oprofile(-) [last unloaded: oprofile]
Pid: 2518, comm: modprobe Not tainted 3.1.0-rc7-00019-gb2fb49d #19 Advanced Micro Device Anaheim/Anaheim
RIP: 0010:[<ffffffff8123c226>] [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
RSP: 0018:ffff88041ef71e98 EFLAGS: 00010296
RAX: 0000000000000000 RBX: ffffffffa0017100 RCX: dead000000200200
RDX: 0000000000000000 RSI: dead000000100100 RDI: ffffffff8178c620
RBP: ffff88041ef71ea8 R08: 0000000000000001 R09: 0000000000000082
R10: 0000000000000000 R11: ffff88041ef71de8 R12: 0000000000000080
R13: fffffffffffffff5 R14: 0000000000000001 R15: 0000000000610210
FS: 00007fc902f20700(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000008 CR3: 000000041cdb6000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 2518, threadinfo ffff88041ef70000, task ffff88041d348040)
Stack:
ffff88041ef71eb8 ffffffffa0017790 ffff88041ef71eb8 ffffffffa0013532
ffff88041ef71ec8 ffffffffa00132d6 ffff88041ef71ed8 ffffffffa00159b2
ffff88041ef71f78 ffffffff81073115 656c69666f72706f 0000000000610200
Call Trace:
[<ffffffffa0013532>] op_nmi_exit+0x15/0x17 [oprofile]
[<ffffffffa00132d6>] oprofile_arch_exit+0xe/0x10 [oprofile]
[<ffffffffa00159b2>] oprofile_exit+0x1e/0x20 [oprofile]
[<ffffffff81073115>] sys_delete_module+0x1c3/0x22f
[<ffffffff811bf09e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff8148070b>] system_call_fastpath+0x16/0x1b
Code: 20 c6 78 81 e8 c5 cc 23 00 48 8b 13 48 8b 43 08 48 be 00 01 10 00 00 00 ad de 48 b9 00 02 20 00 00 00 ad de 48 c7 c7 20 c6 78 81
89 42 08 48 89 10 48 89 33 48 89 4b 08 e8 a6 c0 23 00 5a 5b
RIP [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58
RSP <ffff88041ef71e98>
CR2: 0000000000000008
---[ end trace 43a541a52956b7b0 ]---
Signed-off-by: Robert Richter <robert.richter@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Thanks.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 18 Dec 2011, 12:50
by wread
@kalo86
I tried to experiment your 3.1.5 kernel in Porteus v-1.1-rc2 and the boot process couldn't find the .sgn file.
What is the name of the .sgn file you are using? I am using exactly "porteus-v1.1-i486.sgn"
Regards!
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 18 Dec 2011, 13:29
by kalo86
Of course Porteus could not boot!
I have "porteus-v1.1.sgn"
Anyway I have a negative news: I am having freezes again.
The strange thing is that the freeze can appear only when the desktop is ready to use (just loaded).
The mouse's icon is blocked, no keyboard, no action, no Alt+F4, no Alt+F3, no Power button.
Maybe the problem is xorg module or core module...
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 18 Dec 2011, 14:52
by beny
kalo86, well done with the new kernel, but 1.1-rc2 have an initrd compiled against other libs and have a size to small i think you have to tweak initrd for to start new kernel,btw it is only my opinion,you have to asking brokenman or fanthom to explaine the new entry into the rc2 kernel and script.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 21 Dec 2011, 23:07
by brokenman
Please post (after boot) on pastebin the output of:
The latest rc2 was released with:
aspm patch (for saving power) patch for kernel
Kde4 is rebuilt with new gcc flags
Stuff from initrd was compiled against uClibc insted of glibc
A caching function was added which means you must first boot with one extra module ... and then run a developers script that fanthom generated (prob on server) which will create your new 002 module. If you don't do this you may get funkiness with your desktop.
If i were to try the new kernel i would apply the aufs patch and the aspm patch against the kernel (using kernel config from rc2) and then update 000-kernel as per the thread showing how to upgrade a kernel. I have seen the same freeze after loading to desktop and it was usually because of a bad kernel config or wrong kernel modules being loaded.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 22 Dec 2011, 01:33
by kalo86
But the absence of applying the aspm patch can cause a freeze?
"A caching function was added which means you must first boot with one extra module ... and then run a developers script that fanthom generated (prob on server) which will create your new 002 module. If you don't do this you may get funkiness with your desktop." ---> This could be a different problem because I am having the same kind of freezes since 3.0.X kernels.
Anyway, I am having regular freezes with the stock kernel of rc2.... this means that there is a problem with my hardware and not with the kernel.
Posted after 2 hours 2 minutes 54 seconds:
@ brokenman
dmidecode -q ---->
http://pastebin.com/vdfLhmk4
uname -a ---->
http://pastebin.com/BpuBfnrp
Posted after 4 minutes 31 second:
There is a sort of "rule" for obtaining a freeze on Linux Porteus.
When you reboot my netbook from Windows 7 and you boot directly on the USB thumb, Porteus doesn't freeze;
if you shutdown the system (launching the poweroff command from Windows or Linux) and start from zero the netbook, then Porteus will freeze when the desktop is ready, exaclty Porteus will freeze when the mouse icon is loaded, and if you are very fast with your fingers, you can only move the mouse only for some pixel in the monitor, then it freezes.
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 23 Dec 2011, 00:09
by fanthom
what about using 'changes=' cheatcode -> invoking the hang -> uploading whole /var/log for review?
Re: Kernel 3.1.5-porteus i486 ready for testing
Posted: 23 Dec 2011, 14:48
by kalo86
I have a great news: I have read something on the web about the same problem of freeze with my netbook Acer Aspire One 522 (or 722 model too, with the same AMD C-50 CPU+GPU).
If I blacklist the atl1c module, I never get freezes on Porteus.
Now I am trying with the 3.1.6 kernel, still in compilation phase....
I will try without the blacklist of atl1c module, hoping that the new kernel solves this problem.
Regards