Welcome to WebmasterWorld Guest from 54.166.46.226

Forum Moderators: bakedjake

Message Too Old, No Replies

System freeze at apm init

   
8:01 pm on Sep 17, 2002 (gmt 0)

10+ Year Member



My system freezes at APM init during boot, well sometimes. I can't really tell why and when.

It is something that happens every few weeks, the only way to solve it is to boot without APM support.

Anybody has an idea what's happening?

11:37 pm on Sep 18, 2002 (gmt 0)

WebmasterWorld Senior Member littleman is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Do you think it is a hardware specific issue? I'd try doing some news group searches for APM and your laptop.
1:31 pm on Sep 19, 2002 (gmt 0)

10+ Year Member



I don't use a laptop at all.

I guess PM is enough for a desktop machine, right? I've added that because of my experience with Windows which says it uses APM.

8:19 pm on Sep 19, 2002 (gmt 0)

WebmasterWorld Senior Member littleman is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Sorry, I'm not sure why I assumed you were using a laptop. I've never had a problems with APM.

What hardware, distro and kernel are you using? It might trigger help someone come up with a helpful suggestion.

10:30 am on Sep 20, 2002 (gmt 0)

10+ Year Member



My CPU is:

Intel Pentium III, model 8, stepping 6, 733MHz
fdiv_bug: no, hlt_bug: no, f00f_bug: no, coma_bug: no,
fpu_exception: yes, cpuid level: 2, wp: yes,
flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse

with an Intel D815EEA desktop board.

Slackware Linux 8.1, upgraded from 8.0.

I run a custom kernel: 2.4.18.

2:33 pm on Sep 20, 2002 (gmt 0)

10+ Year Member



My wifes machine does that. It started after I upgraded to rh 7.3 kernel 2.4.18. Its a intel 850gb board. I use Grub as the boot loader and if I hit enter to load the kernel it will freeze every time. If I just let it boot by it's self it never happens.
I have just figured its a kernel bug.
6:58 pm on Sep 20, 2002 (gmt 0)

10+ Year Member



I don't think it is a kernel bug in my case.

It has happened only 3 times for over a month.

I think it began after I compiled ramdisk support inline and turned on initrd support.