Re: 2.4.18-686 freezes on a Dell Inspiron 4100 (and also 2.4.18-bf2.4)
Jean Pierre LeJacq writes:
> On Mon, 10 Jun 2002, Svante Signell wrote:
>
> > Upgrading to BIOS version A08 did not help, the problem remains. It
> > seems that the kernel (2.4.18-686) reenables the APIC:
> > (this is in accordance with the reported bahaviour in bug #139617)
> > ...
> > kernel: Local APIC disabled by BIOS -- reenabling.
> > kernel: Found and enabled local APIC!
> > kernel: Kernel command line: BOOT_IMAGE=2418 ro root=303 noapic
> > ...
> > kernel: Using local APIC timer interrupts.
> > kernel: calibrating APIC timer ...
> >
> > Seems that I have to compile a custom kernel to see if APIC can be
> > turned off, and resolve the problem this way.
>
> I have an Inspiron 7500 which has been running 2.4.18 for quite a
> while with no problem. I did compile a custom kernel, with the
> following set:
>
> CONFIG_X86_GOOD_APIC=y
> # CONFIG_X86_UP_APIC is not set
> # CONFIG_X86_UP_IOAPIC is not set
I compiled a custom kernel with the above settings and this one seems
to work, at least not freezing (more later).
However, after install of the pcmcia kernel modules to the previously
fully functional iso-cd kernel, the newer (Apr 14) 2.4.18-bf2.4
(2.4.18-5 based) was installed (not the kernel supplied with trial
iso-cd, Mar 30) showing the _same_ problems with apic as -686
(2.4.18-5). A diff between the log messages of the iso-cd imge and the
-bf2.4 image boot messages are given below. Sorry that I don't have
the config file of the older (iso-cd) kernel anymore, it has been
overwritten.
A few questions remain:
1. Which configuration settings to use to get the 'noapic' kernel
option to work? No sucess with any on the stock kernels,
2.4.18-bf.2.4 and 2.4.18-686 which are both set up with:
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
aln 2.4.18-686 also with:
CONFIG_X86_GOOD_APIC=y
2. Using the custom kernel (2.4.18-10.0.0.Custom) After for example a
suspend and when running in X, the mouse (touchpad) goes nuts :(
Switching back and forth to a virtual terminal does _not_ help,
neither does an exit from X. A reboot is the only way out. Can this
be due to problems with gpm interaction? Anything else?
diff boot.2.4.18-bf2.4 boot.2418-bf2.4:
1c1
< Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002
---
> Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Sam Mär 30 00:56:06 CET 2002
13,15c13
< Local APIC disabled by BIOS -- reenabling.
< Found and enabled local APIC!
< Kernel command line: BOOT_IMAGE=2418bf ro root=303 noapic
---
> Kernel command line: BOOT_IMAGE=2418bf ro root=303
17c15
< Detected 996.690 MHz processor.
---
> Detected 730.912 MHz processor.
19,20c17,18
< Calibrating delay loop... 1985.74 BogoMIPS
< Memory: 125564k/130952k available (1783k kernel code, 5000k reserved, 549k data, 280k init, 0k highmem)
---
> Calibrating delay loop... 1458.17 BogoMIPS
> Memory: 125608k/130952k available (1775k kernel code, 4956k reserved, 538k data, 260k init, 0k highmem)
26c24
< CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
---
> CPU: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor = 0
29c27
< CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
---
> CPU: After vendor init, caps: 0383f9ff 00000000 00000000 00000000
32,33c30,31
< CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
< CPU: Common caps: 0383fbff 00000000 00000000 00000000
---
> CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
> CPU: Common caps: 0383f9ff 00000000 00000000 00000000
40,48d37
< enabled ExtINT on CPU#0
< ESR value before enabling vector: 00000000
< ESR value after enabling vector: 00000000
< Using local APIC timer interrupts.
< calibrating APIC timer ...
< ..... CPU clock speed is 996.7194 MHz.
< ..... host bus clock speed is 132.8958 MHz.
< cpu: 0, clocks: 1328958, slice: 664479
< CPU0<T0:1328944,T1:664464,D:1,S:664479,C:1328958>
112c101
< Red Hat/Adaptec aacraid driver, Apr 14 2002
---
> Red Hat/Adaptec aacraid driver, Mar 30 2002
125a115,116
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
126a118
> EXT3-fs: recovery complete.
129c121
< Freeing unused kernel memory: 280k freed
---
> Freeing unused kernel memory: 260k freed
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: