Hi There, forget to answer your question, the system seems working fine even I'm getting this kernel failure.
Gonghua On Mon, Apr 20, 2009 at 2:21 PM, Dong <aquino.d...@gmail.com> wrote: > Thanks for replying. > > I didn't get anything by using "dmesg | grep Corrupted", I was trying > "dmesg | grep -i corr" and got below info: > > *gong...@thinkatmsft:~$ dmesg | grep -i corr > [ 0.000000] Scanning 2 areas for low memory corruption > [ 0.004000] Scanning for low memory corruption every 60 seconds > gong...@thinkatmsft:~$ * > > also attached four files per your instructions. > > Thanks! > > Gonghua > > > > On Mon, Apr 20, 2009 at 9:14 AM, Paul Dufresne <dufres...@gmail.com>wrote: > >> >I'm getting this Kernel Failure every time i start the computer. >> Even on normal boot (not after suspend, or hibernate)? >> >> The computer continue to works fine after that? >> >> Could you do a "dmesg | grep Corrupted" after the oops >> and copy the result here? >> >> Also, please attach the minimum requested information by >> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies: >> >> As a last resort, you may manually file your kernel bug, but at a >> minimum it should contain the output of the following commands: >> >> $ uname -a > uname-a.log >> $ cat /proc/version_signature > version.log >> $ dmesg > dmesg.log >> $ sudo lspci -vvnn > lspci-vvnn.log >> >> These four files should be attached separately to the bug report (not >> pasted into comments or tar and zipped, as it makes things harder to >> read, and formatting is completely broken). Please note the comment >> about dmesg output below. >> >> In this particular case, I guess it could be usefull to attache the result >> file of: >> $ sudo dmidecode > dmidecode.log >> >> But you may want to erase the serial numbers, and/or UUID before >> attaching the file. >> >> -- >> WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 >> check_for_bios_corruption+0xdd/0xe0() >> https://bugs.launchpad.net/bugs/350704 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in “linux” source package in Ubuntu: Confirmed >> Status in “linux” source package in Guadalinex Edu: Fix Released >> >> Bug description: >> Before a restart with kerneloops >> >> ProblemType: KernelOops >> Annotation: Your system might become unstable now and might need to be >> restarted. >> Architecture: amd64 >> DistroRelease: Ubuntu 9.04 >> Failure: oops >> MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC >> NonfreeKernelModules: nvidia >> Package: linux-image-2.6.28-11-generic 2.6.28-11.38 >> ProcCmdLine: root=UUID=38814f2f-9f17-43c2-8b1b-73b474164ed4 ro quiet >> splash >> ProcVersionSignature: Ubuntu 2.6.28-11.38-generic >> SourcePackage: linux >> Title: WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 >> check_for_bios_corruption+0xdd/0xe0() >> > > > > -- > Regards > > Dong Gonghua > > -- Regards Dong Gonghua -- WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() https://bugs.launchpad.net/bugs/350704 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
