faster booting?

Baris Erbas

5 Oct 2002 5 Oct '02

19:56

how can i make my linux get faster? For instance, booting time and logging into my account takes almost a minute and a half, where as same process takes about 45 seconds in Windows XP. I am almost always using linux lately and want to use it all the time and get rid of Windows, but speed is an issue for me since I am running some time consuming(mathematical) programs. Can you point me to some document or give me some advice? -- Baris

Show replies by date

tabanna

5 Oct 5 Oct

19:33

New subject: [SLE] faster booting?

On Saturday 05 October 2002 07:56 pm, Baris Erbas wrote:

...

am almost always using linux lately and want to use it all the time

~ maybe then you have no problem, as you may need to re-boot after a couple of months :) -- best wishes ____________ sent on Linux ____________

Carlos E. R.

7 Oct 7 Oct

00:17

New subject: [SLE] faster booting?

El 02.10.05 a las 19:33, tabanna escribió:

...

Date: Sat, 5 Oct 2002 19:33:16 +0000 From: tabanna To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

On Saturday 05 October 2002 07:56 pm, Baris Erbas wrote:

...
am almost always using linux lately and want to use it all the time

~ maybe then you have no problem, as you may need to re-boot after a couple of months :)

Ugh. I run suse 7.3 with kernel 2.4.16, and it hangs now and then: there is a memory issue somewhere with swap, and I'm not sure it has been solved in kernel 2.4.19. Kernel 2.2.x would run for months. But not 2.4.x. Not yet. :-( -- Cheers, Carlos Robinson

kathee

00:44

New subject: [SLE] faster booting?

strange -- I have several 2.4 kernels -- one up for 356 days without a reboot.. they others are close behind... On Sun, 2002-10-06 at 20:17, Carlos E. R. wrote:

...

El 02.10.05 a las 19:33, tabanna escribió:

...
Date: Sat, 5 Oct 2002 19:33:16 +0000 From: tabanna To: suse-linux-e@suse.com

Carlos E. R.

00:59

New subject: [SLE] faster booting?

Then it most be some combination of kernel and hardware. When it happens, both NumLock and CapsLock leds blink alternatively, and I have to pull the power cord. I have heard (read) of several people with exactly the same problem... -- Cheers, Carlos Robinson El 02.10.06 a las 20:44, kathee escribió:

...

Date: 06 Oct 2002 20:44:32 -0400 From: kathee To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

strange -- I have several 2.4 kernels -- one up for 356 days without a reboot.. they others are close behind...

On Sun, 2002-10-06 at 20:17, Carlos E. R. wrote:

...
El 02.10.05 a las 19:33, tabanna escribió:

...
Date: Sat, 5 Oct 2002 19:33:16 +0000 From: tabanna To: suse-linux-e@suse.com

Ben Rosenberg

01:07

New subject: [SLE] faster booting?

Weird. This issue has happened to me 3 times in the last 24 hours. The LED's start blinking and the box freezes up. This is a new occurance since going to 8.1. It's been about 4 hours since it happened. I thought it might have had something to do with apm and apci so they are disabled and I nixed my .kde directory because it happened only when in X. I thought for some odd reason it was a config issue even though I had 3.0.3 on SuSE 8.0 which is the same as the KDE version on 8.1. If anyone has a clue to a fix..please post it. This freezing isn't going to do at all. * Carlos E. R. (robin1.listas@tiscali.es) [021006 18:03]: :: ::Then it most be some combination of kernel and hardware. When it happens, ::both NumLock and CapsLock leds blink alternatively, and I have to pull the ::power cord. I have heard (read) of several people with exactly the same ::problem... :: ::-- ::Cheers, :: Carlos Robinson :: :: ::El 02.10.06 a las 20:44, kathee escribió: :: ::> Date: 06 Oct 2002 20:44:32 -0400 ::> From: kathee ::> To: suse-linux-e@suse.com ::> Subject: Re: [SLE] faster booting? ::> ::> strange -- I have several 2.4 kernels -- one up for 356 days without a -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.

dep

01:28

New subject: [SLE] faster booting?

begin Ben Rosenberg's quote: | If anyone has a clue to a fix..please post it. This freezing isn't | going to do at all. start unloading modules, probably beginning with your nic driver. see if it fixes things. if it does, start loading 'em back up and see which one is doing the dirty. i've seen this a few times, and it's always been the nic module. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.

Carlos E. R.

01:34

New subject: [SLE] faster booting?

lsmod|grep nic shows nothing here. -- Cheers, Carlos Robinson El 02.10.06 a las 21:28, dep escribió:

...

Date: Sun, 6 Oct 2002 21:28:29 -0400 From: dep To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

begin Ben Rosenberg's quote: | If anyone has a clue to a fix..please post it. This freezing isn't | going to do at all.

start unloading modules, probably beginning with your nic driver. see if it fixes things. if it does, start loading 'em back up and see which one is doing the dirty. i've seen this a few times, and it's always been the nic module.

dep

01:47

New subject: [SLE] faster booting?

begin Carlos E. R.'s quote: | lsmod|grep nic shows nothing here. no. nor would it be. sorry. "nic" means network interface card -- your ethernet card, if you have one; but you might well unload other drivers as well, to the extent that you can. then see if the lockup occurs. if it doesn't, then add 'em back, one by one, until the bad guy rear's his ugly head. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.

Carlos E. R.

02:07

New subject: [SLE] faster booting?

El 02.10.06 a las 21:47, dep escribió:

...

Date: Sun, 6 Oct 2002 21:47:48 -0400 From: dep To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

begin Carlos E. R.'s quote: | lsmod|grep nic shows nothing here.

no. nor would it be. sorry. "nic" means network interface card -- your ethernet card, if you have one; but you might well unload other drivers as well, to the extent that you can. then see if the lockup occurs. if it doesn't, then add 'em back, one by one, until the bad guy rear's his ugly head.

Ah, of course. Well, I could do that, but I would have to wait a long time, my crashes are scarce - maybe loading a few large apps would force it. Perhaps Ben could try, he gets them trice a day :-? However, in my case, I think it is related to kswap. Ah! I remember, once I managed to get a log; first one to crash is klogd, then cron, then syslogd: all complain of not being able to page. Jul 27 00:09:37 nimrodel gdm[1129]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 (this one is normal, happens every time I log of X - what happened later is not) Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted EFLAGS: 00010006 eax: c54a9dc4 ebx: 00000000 ecx: 00000001 edx: 00000001 esi: c7d7f014 edi: c4313a80 ebp: c577fee4 esp: c577fec8 ds: 0018 es: 0018 ss: 0018 Process klogd (pid: 493, stackpage=c577f000) Stack: c54a9dc0 c4313a80 c4313a80 c54a9dc4 00000001 00000286 00000001 c577ff20 c01ed14e 7fffffff cfeaa580 c0227029 c4313a80 0000003a c577ff48 c577ff80 c577ff48 c5fec080 00000000 00000000 ffffffe0 c51e7d80 c5c29624 c01ea898 Call Trace: [<c01ed14e>] [<c0227029>] [<c01ea898>] [<c01eaabe>] [<c01315fb>] [<c0106d4b>] Code: 8b 03 85 45 fc 74 56 31 c0 9c 5f fa c7 03 00 00 00 00 83 7b <6>NVRM: AGPGART: allocated 16 pages Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c0113fc4 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted EFLAGS: 00010006 eax: c54a9dc4 ebx: 00000000 ecx: 00000001 edx: 00000001 esi: c7d7f014 edi: c4313a80 ebp: c5789e30 esp: c5789e14 ds: 0018 es: 0018 ss: 0018 Process cron (pid: 31926, stackpage=c5789000) Stack: c54a9dc0 c4313a80 c4313a80 c54a9dc4 00000001 00000286 00000001 c5789e6c c01ed14e 7fffffff ce861880 c0227029 c4313a80 0000004f c5789e94 c5789ed4 c5789e94 c6509080 00000000 00000000 ffffffe0 c0289a30 c6494da4 c01ea898 Call Trace: [<c01ed14e>] [<c0227029>] [<c01ea898>] [<c01eb5d5>] [<c011324c>] [<c011342b>] [<c011324c>] [<c0121f8d>] [<c01241e5>] [<c01eb612>] [<c01ebdb1>] [<c0106e3c>] [<c0106d4b>] Code: 8b 03 85 45 fc 74 56 31 c0 9c 5f fa c7 03 00 00 00 00 83 7b <1>Unable to handle kernel paging request at virtual address 206b725d printing eip: c013dcf9 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c013dcf9>] Not tainted EFLAGS: 00010203 eax: c5521f6c ebx: 206b7249 ecx: c5521f6c edx: c6d56e04 esi: c7d7f000 edi: c7d7f008 ebp: c5521f74 esp: c5521f34 ds: 0018 es: 0018 ss: 0018 Process syslogd (pid: 488, stackpage=c5521000) Stack: 00000000 c1676c00 00000001 c013e018 c5521f6c 00000004 00000001 c6d56e18 00000345 00000001 c5520000 7fffffff 00000001 00000000 00000000 c7d7f000 00000000 c013e390 00000001 c5521fa8 c5521fa4 c5520000 00000000 00000000 Call Trace: [<c013e018>] [<c013e390>] [<c0106d4b>] Code: 8b 43 14 8d 53 04 e8 68 70 fd ff 8b 03 e8 ad 42 ff ff 39 fb output of ps at the time: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 002 0 7 0 9 0 0 0 kupdat SW ? 0:02 [kupdated] 002 0 6 0 9 0 0 0 bdflus SW ? 0:03 [bdflush] 022 0 5 0 9 0 0 0 kswapd SW ? 0:14 [kswapd] 002 0 4 0 19 19 0 0 ksofti SWN ? 0:00 [ksoftirqd_CPU0] 004 0 1 0 9 0 448 88 do_sel S ? 0:04 init [5] 002 0 2 1 9 0 0 0 contex SW ? 0:01 [keventd] 002 0 3 1 9 0 0 0 apm_ma SW ? 0:00 [kapm-idled] 002 0 8 1 -1 -20 0 0 md_thr SW< ? 0:00 [mdrecoveryd] 002 0 14 1 9 0 0 0 end SW ? 0:00 [kreiserfsd] 002 0 33 1 -1 -20 0 0 md_thr SW< ? 0:00 [raid1d] 002 0 64 1 9 0 0 0 end SW ? 0:00 [kjournald] 002 0 268 1 9 0 0 0 end SW ? 0:00 [eth0] 002 0 296 1 9 0 0 0 end SW ? 0:00 [khubd] 004 0 462 1 9 0 6216 4 wait_f S ? 0:00 /usr/sbin/snort -D -c /etc/snort/snort.conf 006 0 489 1 9 0 2304 4 do_sel S ? 0:00 /usr/sbin/sshd 006 1 549 1 9 0 1332 4 do_pol S ? 0:00 /sbin/portmap 004 65 594 1 9 0 3456 448 do_sel S ? 0:00 /usr/sbin/amavis-milter -p local:/var/run/amavis/amavis-milter.sock 002 65 595 594 9 0 3456 448 do_pol S ? 0:00 \_ /usr/sbin/amavis-milter -p local:/var/run/amavis/amavis-milter.sock 002 65 596 595 9 0 3456 448 rt_sig S ? 0:00 \_ /usr/sbin/amavis-milter -p local:/var/run/amavis/amavis-milter.sock 006 0 607 1 9 0 1304 4 do_sel S ? 0:00 /usr/sbin/apmd -w 10 -v -P /usr/sbin/apmd_proxy 002 25 629 1 9 0 1444 332 nanosl S ? 0:00 /usr/sbin/atd 005 0 17867 629 9 0 0 0 do_exi Z ? 0:00 \_ [sendmail <defunct>] 006 65534 693 1 9 0 5680 28 wait_f S ? 0:00 /usr/sbin/in.identd -e 002 65534 694 693 9 0 5680 28 do_pol S ? 0:00 \_ /usr/sbin/in.identd -e 002 65534 695 694 9 0 5680 28 rt_sig S ? 0:00 \_ /usr/sbin/in.identd -e 002 65534 696 694 9 0 5680 28 rt_sig S ? 0:00 \_ /usr/sbin/in.identd -e 002 4 773 1 9 0 1948 4 do_sel S ? 0:00 lpd Waiting 002 0 810 1 9 0 11464 2512 rt_sig S ? 0:00 /usr/sbin/named 002 0 811 810 9 0 11464 2512 do_pol S ? 0:00 \_ /usr/sbin/named 006 0 812 811 9 0 11464 2512 rt_sig S ? 0:00 \_ /usr/sbin/named 002 0 813 811 9 0 11464 2512 nanosl S ? 0:00 \_ /usr/sbin/named 002 0 815 811 9 0 11464 2512 do_sel S ? 0:00 \_ /usr/sbin/named 002 41 913 1 9 0 1556 4 wait_f S ? 0:00 /usr/sbin/scanlogd 006 65534 1022 1 9 0 3880 104 do_sel S ? 0:00 proftpd (accepting connections) 006 0 1031 1 9 0 4000 580 do_sel S ? 0:00 sendmail: accepting connections 004 0 1034 1 9 0 6160 608 do_pol S ? 0:00 /opt/gnome/bin/gdm 006 0 31909 1034 9 0 6216 1436 pipe_w S ? 0:00 \_ /opt/gnome/bin/gdm 004 0 31910 31909 9 0 275080 9236 do_sel S ? 0:00 \_ /usr/bin/X11/X :0 vt7 -auth /var/lib/gdm/:0.Xauth 004 50 31924 31909 9 0 7172 3884 do_pol S ? 0:00 \_ /opt/gnome/bin/gdmlogin --disable-sound --disable-crash-dialog 002 0 1070 1 9 0 1464 168 nanosl S ? 0:00 /usr/sbin/cron 003 0 31949 1070 9 0 0 0 do_exi Z ? 0:00 \_ [cron <defunct>] 002 0 1125 1 9 0 11800 376 do_pol S ? 0:00 /usr/sbin/nscd 002 0 1130 1125 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 002 0 1131 1130 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 002 0 1132 1130 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 002 0 1133 1130 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 002 0 1134 1130 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 002 0 1135 1130 9 0 11800 376 do_pol S ? 0:00 \_ /usr/sbin/nscd 000 0 1128 1 9 0 2864 28 do_sel S ? 0:00 /usr/sbin/smpppd 006 0 1151 1 9 0 1348 152 do_sel S ? 0:00 /usr/sbin/gpm -t imps2 -m /dev/mouse 006 0 1170 1 9 0 1348 4 do_sel S ? 0:00 /usr/sbin/inetd 004 0 1298 1 9 0 1296 4 read_c S tty1 0:00 /sbin/mingetty --noclear tty1 004 0 1299 1 9 0 2084 4 wait4 S tty2 0:00 login -- cer 004 500 16910 1299 9 0 2708 4 wait4 S tty2 0:00 \_ -bash 000 500 17067 16910 11 0 1972 560 do_sel S tty2 0:13 \_ top 004 0 1300 1 9 0 1296 4 read_c S tty3 0:00 /sbin/mingetty tty3 004 0 1303 1 9 0 2080 4 wait4 S tty6 0:00 login -- root 004 0 1668 1303 9 0 2716 692 read_c S tty6 0:00 \_ -bash 006 0 1304 1 9 0 52004 56 do_sel S ? 0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf 006 30 1305 1304 9 0 52076 4 wait_f S ? 0:00 \_ /usr/sbin/httpd -f /etc/httpd/httpd.conf 004 0 31900 1 9 0 2080 1188 wait4 S tty5 0:00 login -- root 004 0 31927 31900 16 0 2716 1544 wait4 S tty5 0:00 \_ -bash 004 0 31975 31927 17 0 2996 1984 - R tty5 0:00 \_ ps afxlll 004 0 31901 1 9 0 1300 500 read_c S tty4 0:00 /sbin/mingetty tty4 004 0 31923 1 9 0 3396 1744 pipe_w S ? 0:00 /usr/X11R6/bin/xconsole -notify -nostdin -verbose -exitOnFail -- Cheers, Carlos Robinson

Graham Murray

05:58

New subject: [SLE] faster booting?

"Carlos E. R." writes:

...

(this one is normal, happens every time I log of X - what happened later is not)

Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted [snip]

That is a kernel oops. Input all that data (either from a log file if it has been written, or enter by hand) through 'ksymoops' which will decode it and indicate where the problem is occurring.

Radule Soskic

15:37

New subject: [SLE] faster booting?

Hi, I noted something like this when upgraded from 7.3 to 8.0. I found out that I have to switch off something named "scanning new HW" (or similar to it, I am not positive that the name is quite exact) which was active during boot. Well, after I removed it from my list of services, my boot time got shortened significantly. Hope this helps. Best regards, Radule Soskic On Mon, 2002-10-07 at 07:58, Graham Murray wrote:

...

"Carlos E. R." writes:

...
(this one is normal, happens every time I log of X - what happened later is not)

Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted [snip]

That is a kernel oops. Input all that data (either from a log file if it has been written, or enter by hand) through 'ksymoops' which will decode it and indicate where the problem is occurring.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Jeric

10 Oct 10 Oct

22:43

New subject: turning off "scanning new hardware" [was: faster booting?]

As I have now put 8.1 on the first of my systems, I too have noticed that the boot time (from power on to the console - init 2) is *significantly* slower then 7.2. However, the longest part is the "scanning new hardware" during boot. What is the downside to turning this off? I can see where it /might/ not matter on a desktop or server where the hardware doesn't change often, but how about a laptop? If I turn this off will it break the "hotswap" component of Linux? thanks, Jeric : -----Original Message----- : From: Radule Soskic [mailto:rms@telekom.yu] : Sent: Monday, October 07, 2002 10:37 AM : To: SuSE Mailing List : Subject: Re: [SLE] faster booting? : : : Hi, : : I noted something like this when upgraded from 7.3 to 8.0. I found out : that I have to switch off something named "scanning new HW" (or similar : to it, I am not positive that the name is quite exact) which was active : during boot. Well, after I removed it from my list of services, my boot : time got shortened significantly. : : Hope this helps. : : Best regards, : : Radule Soskic : :

Christopher Mahmood

22:46

New subject: [SLE] turning off "scanning new hardware" [was: faster booting?]

* Jeric (jeric@sbcglobal.net) [021010 15:40]:

...

As I have now put 8.1 on the first of my systems, I too have noticed that the boot time (from power on to the console - init 2) is *significantly* slower then 7.2. However, the longest part is the "scanning new hardware" during boot. What is the downside to turning this off?

New hardware won't be automatically detected. You can turn it off with insserv -r hwscan -- -ckm

zentara

11 Oct 11 Oct

06:39

New subject: [SLE] turning off "scanning new hardware" [was: faster booting?]

On Thu, 10 Oct 2002 17:43:09 -0500 "Jeric" wrote:

...

As I have now put 8.1 on the first of my systems, I too have noticed that the boot time (from power on to the console - init 2) is *significantly* slower then 7.2. However, the longest part is the "scanning new hardware" during boot. What is the downside to turning this off? I can see where it /might/ not matter on a desktop or server where the hardware doesn't change often, but how about a laptop? If I turn this off will it break the "hotswap" component of Linux?

I like the list from the console version of yast2->system->run level editor->run level properties -- use Perl; #powerful programmable prestidigitation

Carlos E. R.

7 Oct 7 Oct

20:14

New subject: [SLE] faster booting?

Ah! Bad luck that I did not know this at the time: I recompiled the kernel sometime after that log. It was the only time the system remained running enough time for me to save the log. In any case, I get this: ksymoops 2.4.2 on i686 2.4.16-4GB. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.16-4GB/ (default) -m /boot/System.map-2.4.16-4GB (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c01e53a0, System.map says c0151e6Warning (compare_maps): mismatch on symbol __nvsym03120 , NVdriver says c74da780, /lib/modules/2.4.16-4GB/vid Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010006 eax: c54a9dc4 ebx: 00000000 ecx: 00000001 edx: 00000001 esi: c7d7f014 edi: c4313a80 ebp: c577fee4 esp: c577fec8 ds: 0018 es: 0018 ss: 0018 Process klogd (pid: 493, stackpage=c577f000) Stack: c54a9dc0 c4313a80 c4313a80 c54a9dc4 00000001 00000286 00000001 c577ff20 c01ed14e 7fffffff cfeaa580 c0227029 c4313a80 0000003a c577ff48 c577ff80 c577ff48 c5fec080 00000000 00000000 ffffffe0 c51e7d80 c5c29624 c01ea898 Call Trace: [<c01ed14e>] [<c0227029>] [<c01ea898>] [<c01eaabe>] [<c01315fb>] [<c0106d4b>] Code: 8b 03 85 45 fc 74 56 31 c0 9c 5f fa c7 03 00 00 00 00 83 7b

...

...
EIP; c0113fc4 <__wake_up+2c/a0> <===== Trace; c01ed14e Trace; c0227028 Trace; c01ea898 Trace; c01eaabe Trace; c01315fa Trace; c0106d4a Code; c0113fc4 <__wake_up+2c/a0> 00000000 <_EIP>: EIP; c0113fc4 <__wake_up+2c/a0> <===== Trace; c01ed14e Trace; c0227028 Trace; c01ea898 Trace; c01eaabe Trace; c01315fa Trace; c0106d4a Code; c0113fc4 <__wake_up+2c/a0> 00000000 <_EIP>: Code; c0113fc4 <__wake_up+2c/a0> <===== 0: 8b 03 mov (%ebx),%eax <===== Code; c0113fc6 <__wake_up+2e/a0> 2: 85 45 fc test %eax,0xfffffffc(%ebp) Code; c0113fc8 <__wake_up+30/a0> 5: 74 56 je 5d <_EIP+0x5d> c0114020 <__wake_up+88/a0> Code; c0113fca <__wake_up+32/a0> 7: 31 c0 xor %eax,%eax Code; c0113fcc <__wake_up+34/a0> 9: 9c pushf Code; c0113fce <__wake_up+36/a0> a: 5f pop %edi Code; c0113fce <__wake_up+36/a0> b: fa cli Code; c0113fd0 <__wake_up+38/a0> c: c7 03 00 00 00 00 movl $0x0,(%ebx) Code; c0113fd6 <__wake_up+3e/a0> 12: 83 7b 00 00 cmpl $0x0,0x0(%ebx)

Unable to handle kernel NULL pointer dereference at virtual address 00000000 c0113fc4 *pde = 00000000 Oops: 0000 But I can not understand almost any of it, I'm not a kernel speciallist. -- Cheers, Carlos Robinson El 02.10.07 a las 06:58, Graham Murray escribió:

...

Date: Mon, 07 Oct 2002 06:58:09 +0100 From: Graham Murray To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

"Carlos E. R." writes:

...
(this one is normal, happens every time I log of X - what happened later is not)

Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted [snip]

That is a kernel oops. Input all that data (either from a log file if it has been written, or enter by hand) through 'ksymoops' which will decode it and indicate where the problem is occurring.

Carlos E. R.

01:32

New subject: [SLE] faster booting?

No, it's not new to suse 8.1, because I have 7.3. I also suspect kde (the stock one), so much so that I switched to use gdm as login manager, and I use gnome unless I need kde for something. A person reported the problem almost everytime he logged of kde; I had it perhaps once every two weeks, and now once every month or two; but this is a home computer, it is rare that it stays on for more than 8 hours on a run. But if I make use of large applications that force swaping memory, then I have a 30% chance of crashing when powering off (halt) the machine. On milder cases, it is just daemons stoping, like cron or something. I have the feeling that if enable both apic and acpi the machine runs faster and more stable; however, then I can not power it off (suse 7.3 is not prepared for acpi, it lacks the daemons for it). With the default settings of apic and apm it crashes as soon as I switch from X to a console, but that is documented: I have to disable apic (it is the safe setting in lilo). -- Cheers, Carlos Robinson El 02.10.06 a las 18:07, Ben Rosenberg escribió:

...

Date: Sun, 6 Oct 2002 18:07:02 -0700 From: Ben Rosenberg To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

Weird. This issue has happened to me 3 times in the last 24 hours. The LED's start blinking and the box freezes up. This is a new occurance since going to 8.1. It's been about 4 hours since it happened. I thought it might have had something to do with apm and apci so they are disabled and I nixed my .kde directory because it happened only when in X. I thought for some odd reason it was a config issue even though I had 3.0.3 on SuSE 8.0 which is the same as the KDE version on 8.1.

If anyone has a clue to a fix..please post it. This freezing isn't going to do at all.

* Carlos E. R. (robin1.listas@tiscali.es) [021006 18:03]: :: ::Then it most be some combination of kernel and hardware. When it happens, ::both NumLock and CapsLock leds blink alternatively, and I have to pull the ::power cord. I have heard (read) of several people with exactly the same ::problem... :: ::-- ::Cheers, :: Carlos Robinson :: :: ::El 02.10.06 a las 20:44, kathee escribió: :: ::> Date: 06 Oct 2002 20:44:32 -0400 ::> From: kathee ::> To: suse-linux-e@suse.com ::> Subject: Re: [SLE] faster booting? ::> ::> strange -- I have several 2.4 kernels -- one up for 356 days without a

Mads Martin Joergensen

12:09

New subject: [SLE] faster booting?

* Ben Rosenberg [Oct 07. 2002 03:07]:

...

Weird. This issue has happened to me 3 times in the last 24 hours. The LED's start blinking and the box freezes up. This is a new occurance

The LED's are morsing the oops to you :-) -- Mads Martin Jørgensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort?" -- A. P. J.

Peter B Van Campen

15:58

New subject: [SLE] faster booting?

Hi, Your h/w is trying to tell you something. The blinking LEDs are the BIOS's way of notifying you of a serious H/W prob. Just what prob is signaled in the blink pattern and those patterns are Manuf. specific. Look in your MotherBoard info, or search the makers web tech supp. My first guess? Overheating. PeterB On Monday 07 October 2002 07:09, Mads Martin Joergensen wrote:

...

* Ben Rosenberg [Oct 07. 2002 03:07]:

...
Weird. This issue has happened to me 3 times in the last 24 hours. The LED's start blinking and the box freezes up. This is a new occurance

The LED's are morsing the oops to you :-)

Carlos E. R.

19:59

New subject: [SLE] faster booting?

No, no, it is not the bios, it is the kernel. I saw the message log from the kernel showing crash dumps just before the crash, about not being able to page some memory request. Several makers, different hardware and CPUs, different everything, but all running suse (different versions), show that sympton. -- Cheers, Carlos Robinson El 02.10.07 a las 10:58, Peter B Van Campen escribió:

...

Date: Mon, 7 Oct 2002 10:58:20 -0500 From: Peter B Van Campen To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting?

Hi, Your h/w is trying to tell you something. The blinking LEDs are the BIOS's way of notifying you of a serious H/W prob. Just what prob is signaled in the blink pattern and those patterns are Manuf. specific. Look in your MotherBoard info, or search the makers web tech supp.

My first guess? Overheating.

PeterB

On Monday 07 October 2002 07:09, Mads Martin Joergensen wrote:

...
* Ben Rosenberg [Oct 07. 2002 03:07]:

...
Weird. This issue has happened to me 3 times in the last 24 hours. The LED's start blinking and the box freezes up. This is a new occurance

The LED's are morsing the oops to you :-)

dep

8 Oct 8 Oct

10:51

New subject: [SLE] faster booting?

begin Peter B Van Campen's quote: | Your h/w is trying to tell you something. The blinking LEDs are the | BIOS's way of notifying you of a serious H/W prob. Just what prob | is signaled in the blink pattern and those patterns are Manuf. | specific. Look in your MotherBoard info, or search the makers web | tech supp. | | My first guess? Overheating. good point. if the chip fan dies, it does not necessarily scream on its way out. and nowadays, even memory can get warm enough to turn from chip to flake. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.

Ali Naddaf

5 Oct 5 Oct

20:26

New subject: [SLE] faster booting?

Baris, Are you using any Desktop (such as KDE)? Is it the boot up process which is taking long or is it the login process (after boot up, till your desktop come up, if you are using any desktop at all) which is long? If it is the latter, then try to login to something light-weight like twm or fvwm to see if it is the KDE stuff that are slowing down or something else. If it is boot up, then look at the boot log to see if during the boot up there is any device which is taking too long to respond. We need more info to be able to make a hopefully useful suggestion :-) Ali. On Saturday 05 October 2002 2:56 pm, Baris Erbas wrote:

...

how can i make my linux get faster? For instance, booting time and logging into my account takes almost a minute and a half, where as same process takes about 45 seconds in Windows XP. I am almost always using linux lately and want to use it all the time and get rid of Windows, but speed is an issue for me since I am running some time consuming(mathematical) programs. Can you point me to some document or give me some advice?

7875

Age (days ago)

7881

Last active (days ago)

List overview

Download

21 comments

14 participants

participants (14)

Ali Naddaf
Baris Erbas
Ben Rosenberg
Carlos E. R.
Christopher Mahmood
dep
Graham Murray
Jeric
kathee
Mads Martin Joergensen
Peter B Van Campen
Radule Soskic
tabanna
zentara

faster booting?

Baris Erbas

tabanna

Carlos E. R.

kathee

Carlos E. R.

Ben Rosenberg

dep

Carlos E. R.

dep

Carlos E. R.

Graham Murray

Radule Soskic

Jeric

Christopher Mahmood

zentara

Carlos E. R.

Carlos E. R.

Mads Martin Joergensen

Peter B Van Campen

Carlos E. R.

dep

Ali Naddaf

tags

participants (14)