Package: kernel-image-2.4.27-1-386
Version: 2.4.27-1
Severity: important
Tags: d-i
I have a pair of oopses using this kernel image to install on my test
laptop using d-i. At boot, I get this one, copied down by hand, in the
middle of usb setup:
ehci_hcd 00:1d.7: BIOS handoff failed (104, 1010001)
ehci_hcd 00:1d.7: remove state 0
Unable to handle kernel NULL pointer dereference at virtual address 00000048
printing eip:
e082774e
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<e082774e>] Not tainted
EFLAGS: 00010002
eax: 00000000 ebx: c15a3200 ecx: c15a3334 edx: c02a52ec
esi: 00000000 edi: c15a3200 ebp: 00000000 esp: dee33e14
ds: 0018 es: 0018 ss: 0018
Process insmod (pid: 149, stackpage=dee33000)
Stack: 00000000 c15a3200 00000000 c15a3264 de49b3e0 e0828ff3 c15a3200 00000000
c15a3200 c15a3264 e0828e85 c15a3200 00000000 0000252a c01165e6 0000252a
0000252a 00000286 00000246 00000286 00000001 c029f4e4 00000246 00000024
Call Trace: [<e0828ff3>] [<e0828385>] [<c01165e6>] [<c0116749>] [<e081a995>]
[<e081a921>] [<e0829500>] [<e08298a0>] [<c019dd69>] [<e0829500>] [<e08298a0>]
[<c019ddc6>] [<e08298a0>] [<e082942e>] [<e08298a0>] [<c01172fb>] [<e0829858>]
[<e0826060>] [<c01081fb>]
Code: 8b 70 48 85 f6 74 6f 8d 46 4c 39 46 4c 74 2f 8b 87 44 01 00
<6>usb.c: registered new driver usbkbd
usb.c: null device being checked!!!
The second oops happens whenever I run kbd-chooser in d-i. The first
time this happens, kbd-chooser exits nonzero. If I run it again, I don't
get an oops, and kbd-chooser hangs in state D.
Unable to handle kernel NULL pointer dereference at virtual address 000000c4
printing eip:
e0819d88
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<e0819d88>] Not tainted
EFLAGS: 00010286
eax: df1e2000 ebx: 00000000 ecx: 1f1e2000 edx: 00000000
esi: e081eae0 edi: 00000000 ebp: df1e2000 esp: dfcf5f3c
ds: 0018 es: 0018 ss: 0018
Process kbd-chooser (pid: 1950, stackpage=dfcf5000)
Stack: 00000073 00000000 00000000 00000000 de49b404 e081eae0 00000000 df1e7140
e081a05f dfcf5fa4 dfcf5fa8 dfcf5f84 df1e7140 00000000 de49b3e0 00000000
00000000 00000000 00000000 00000000 00000000 df1e7120 ffffffea 00001000
Call Trace: [<e081eae0>] [<e081a05f>] [<c0131570>] [<c01081fb>]
Code: 8b 82 c4 00 00 00 85 c0 c7 09 8b 00 83 f8 ff 74 02 89 c3 8b
This is followed by insmod yenta_socket hanging in D state later on.
That happens whether or not I avoid the kbd-chooser oops by not running
kbd-chooser. This makes it impossible to install debian on this laptop
with the 2.4 kernel.
I've never had any particular problems with this laptop and older
kernels. Perhaps 2.4.27 is not as ready for prime time use in the
installer as you assured us it was?
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages kernel-image-2.4.27-1-386 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
ii initrd-tools 0.1.74 tools to create initrd image for p
ii modutils 2.4.26-1 Linux module utilities
-- no debconf information
--
see shy jo
Attachment:
signature.asc
Description: Digital signature