hello,
2.6.0-test9-mm4 doesn't boot for me ... oops followed by
kernel panic - attempted to kill init (2.6.0-test9 works fine).
it crashes right after initialising PNP bios. The (undecoded) oops doesn't
seem to make a lot of sense (i wrote the oops down and i typed it in), and
ksymoops doesn't show a lot too.
Someone has an idea what this could be, or a hint to improve oops
output ? (i can reproduce it as much as i want to)
------------------- oops output
general protection fault: 0000 [#1]
PREEMPT SMP
CPU: 0
EIP: 0098:[<00002d6c>] Not tainted VLI
EFLAGS: 00010097
EIP is at 0x2d6c
eax: 00003410 ebx: 00000082 ecx: 00020000 edx: 00000002
esi: 00002630 edi: c1a4004d ebp: c1a40000 esp: c1a47ee2
ds: 0060 es: 0060 ss:0068
Process swapper (PID:1 threadinfo=c1a46000 task=c1a5f980)
Stack: 00000410 341026de 00000000 836d004d 0004cfea 00020002 7f28830c cfeacff2
64090909 01090109 007b6264 6000007b 00a00246 622000b0 00a861e6 00000086
000b0000 00010090 00a80000 00b00000 00a00002 bee90000 0060c02b 00820000
Call Trace:
Code:
bad EIP Value
------------------ ksymoops -V -K -L -o /lib/modules/2.6.0-test9-mm4/ -m /boot/System.map-2.6.0-test9-mm4 < /root/oops.txt
Warning (Oops_read): Code line not seen, dumping what data is available
>>EIP; 00002d6c Before first symbol <=====
>>edi; c1a4004d <__crc_unregister_chrdev+112bbc/1668b5>
>>ebp; c1a40000 <__crc_unregister_chrdev+112b6f/1668b5>
>>esp; c1a47ee2 <__crc_unregister_chrdev+11aa51/1668b5>
----------------
op Wednesday 19 November 2003 07:52 , schreef Andrew Morton in <[email protected]> :
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/
>
>
> . Several fixes against patches which are only in -mm at present.
>
> . Minor fixes which we'll queue for post-2.6.0.
>
> . The interactivity problems which the ACPI PM timer patch showed up
> should be fixed here - please sing out if not.
--
Frank Dekervel - [email protected]
Mechelsestraat 88
3000 Leuven (Belgium)
Frank Dekervel <[email protected]> wrote:
>
> 2.6.0-test9-mm4 doesn't boot for me ... oops followed by
> kernel panic - attempted to kill init (2.6.0-test9 works fine).
> it crashes right after initialising PNP bios.
Please make sure that you have CONFIG_KALLSYMS set.
It would help to add `initcall_debug' to the kernel boot command line.
That way you will find out the address of the final initcall which was
invoked before the kernel crashed. Please look that up in System.map.
Thanks.
hello,
Op Thursday 20 November 2003 01:59, schreef Andrew Morton:
> > 2.6.0-test9-mm4 doesn't boot for me ... oops followed by
> > kernel panic - attempted to kill init (2.6.0-test9 works fine).
> > it crashes right after initialising PNP ?bios.
>
> Please make sure that you have CONFIG_KALLSYMS set.
it is set ... but no decoded output. probably something is messed up
kervel@bakvis:~$ cat /boot/config-2.6.0-test9-mm4 | grep -i kall
CONFIG_KALLSYMS=y
>
> It would help to add `initcall_debug' to the kernel boot command line.
> That way you will find out the address of the final initcall which was
> invoked before the kernel crashed. ?Please look that up in System.map.
kervel@bakvis:~$ cat /boot/System.map-2.6.0-test9-mm4 | grep c052ed91
c052ed91 T pnpbios_init
pnpbios says something like this:
found installation structure 0xc00f5560
version 1.0 entry 0xf0000:0x6149 dseg 0xf0000
i'm going to try without pnpbios i think.
my working 2.6.0test9 also has pnpbios setup:
kervel@bakvis:~$ cat /boot/config-2.6.0-test9 | grep -i pnpbios
CONFIG_PNPBIOS=y
greetings,
frank
--
Frank Dekervel - [email protected]
Mechelsestraat 88
3000 Leuven (Belgium)
Op Thursday 20 November 2003 11:34, schreef Frank Dekervel:
> pnpbios says something like this:
> ?found installation structure 0xc00f5560
> ?version 1.0 entry 0xf0000:0x6149 dseg 0xf0000
>
> i'm going to try without pnpbios i think.
>
> my working 2.6.0test9 also has pnpbios setup:
> kervel@bakvis:~$ cat /boot/config-2.6.0-test9 | grep -i pnpbios
> CONFIG_PNPBIOS=y
ok, replying to myself to be more specific:
working pnpbios gives this:
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00f5560
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x614a, dseg 0xf0000
PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
SCSI subsystem initialized
mm4 pnpbios gives the same numbers, but never says
PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
instead it says general protection fault
sorry,
greetings,
frank
--
Frank Dekervel - [email protected]
Mechelsestraat 88
3000 Leuven (Belgium)
Frank Dekervel <[email protected]> wrote:
>
> Op Thursday 20 November 2003 11:34, schreef Frank Dekervel:
> > pnpbios says something like this:
> > ?found installation structure 0xc00f5560
> > ?version 1.0 entry 0xf0000:0x6149 dseg 0xf0000
> >
> > i'm going to try without pnpbios i think.
> >
> > my working 2.6.0test9 also has pnpbios setup:
> > kervel@bakvis:~$ cat /boot/config-2.6.0-test9 | grep -i pnpbios
> > CONFIG_PNPBIOS=y
>
> ok, replying to myself to be more specific:
>
> working pnpbios gives this:
> ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> PnPBIOS: Scanning system for PnP BIOS support...
> PnPBIOS: Found PnP BIOS installation structure at 0xc00f5560
> PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x614a, dseg 0xf0000
> PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
> SCSI subsystem initialized
>
> mm4 pnpbios gives the same numbers, but never says
> PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
> instead it says general protection fault
>
There are three pnpbios patches in -mm:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-1.patch
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-2.patch
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-3.patch
It would help if you could determine which (if any) of these are causing
the problem. You can remove the patches with
cd /usr/src/linux
patch -p1 -R < ~/pnp-fix-3.patch
etcetera.
Thanks.
hello,
> mm4 pnpbios gives the same numbers, but never says
> PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
> instead it says general protection fault
>
> There are three pnpbios patches in -mm:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-1.patch
"With this patch, the PnPBIOS driver will read static resources
initially and then switch to dynamic mode when allocating
resources for specific nodes."
-> this one causes the trouble (general protection fault -> kernel panic) for me... without this patch
my system boots (and recognises pnpbios) fine.
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-2.patch
"this patch provides an option for PnPBIOS calls to be
managed by the PnPBIOS driver exclusively" (no /proc support)
-> cannot be this one, since i enabled /proc support
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-3.patch
-> not pnpbios related (isapnp)
greetings,
frank
--
Frank Dekervel - [email protected]
Mechelsestraat 88
3000 Leuven (Belgium)
hello
something similar:
catting /proc/bus/pnp/devices makes my system oops, doing it twice makes my
system crash :p
the oops looks very much like the oops (also bad EIP value, also no stack
trace) i get on boot with the first patch (below) applied. As i already
mailed, i need to revert that patch to make my system boot.
this oops happens with all 3 patches below reverted, so i guess it'll happen
too with stock test9.
would the -mm5 pnp-fix-4.patch be worth a try ? it seems related
thanks,
greetings,
frank
Op Thursday 20 November 2003 16:22, schreef Andrew Morton:
> There are three pnpbios patches in -mm:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2
>.6.0-test9-mm4/broken-out/pnp-fix-1.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2
>.6.0-test9-mm4/broken-out/pnp-fix-2.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2
>.6.0-test9-mm4/broken-out/pnp-fix-3.patch
>
> It would help if you could determine which (if any) of these are causing
> the problem. ?You can remove the patches with
>
> ????????cd /usr/src/linux
> ????????patch -p1 -R < ~/pnp-fix-3.patch
--
Frank Dekervel - [email protected]
Mechelsestraat 88
3000 Leuven (Belgium)
On Sat, Nov 22, 2003 at 06:50:36PM +0100, Frank Dekervel wrote:
> hello
>
> something similar:
>
> catting /proc/bus/pnp/devices makes my system oops, doing it twice makes my
> system crash :p
>
> the oops looks very much like the oops (also bad EIP value, also no stack
> trace) i get on boot with the first patch (below) applied. As i already
> mailed, i need to revert that patch to make my system boot.
>
> this oops happens with all 3 patches below reverted, so i guess it'll happen
> too with stock test9.
>
> would the -mm5 pnp-fix-4.patch be worth a try ? it seems related
>
> thanks,
> greetings,
> frank
Hi,
Thanks for the testing. I don't think pnp-fix-4.patch should affect this problem.
I will probably be creating a blacklist for PnPBIOS systems that have this bug.
Currently, I'm waiting to see if reading static resources has any positive affects
on some additional systems. If not then I may switch back to the the original
behavior. DMI information for your system would be helpful.
Thanks,
Adam