Hello all, I got this opps when booting 2.6.0-test9-mm4
It happens consistently every boot.
I had to copy it down by hand, I think I got all of it correctly.
As always flames, additional questions, and patches are welcome.
ksymoops 2.4.9 on i686 2.6.0-test9. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.0-test9-mm4/ (specified)
-m /System.map (specified)
Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
CPU: 0
EIP: 0098:[<00005121>] Not tainted VLI
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010046
esi: 0000a15a edi: 00000000 ebp: c151fe8c esp: c151fe5a
ds: 00a0 es: 00a8 ss: 0068
Stack: 00000cfe 0e5700a0 000b000b 9daba392 9d3a9b03 9ad10001 00000000 007b0001
9ab6007b 00000246 00020082 000bdfdc 00020090 00000002 000100a8 000000a0
9ce70000 0060c025 00020000 00000000 00000000 007b0000 007b0000 02460000
Call Trace:
Code: Bad EIP Value.
>>EIP; 00005121 Before first symbol <=====
>>ebp; c151fe8c <acqseq_lock.7+108bfa4/3fb69118>
>>esp; c151fe5a <acqseq_lock.7+108bf72/3fb69118>
<0>Kernel panic: Attempted to kill init!
1 error issued. Results may not be reliable.
--
*--* Mail: [email protected]
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://www.otak-k.com/~lawrence/
--------------------------------------
- - - - - - O t a k i n c . - - - - -
Lawrence Walton <[email protected]> wrote:
>
> Hello all, I got this opps when booting 2.6.0-test9-mm4
> It happens consistently every boot.
>
> I had to copy it down by hand, I think I got all of it correctly.
> As always flames, additional questions, and patches are welcome.
>
>
>
>
>
> ksymoops 2.4.9 on i686 2.6.0-test9. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.6.0-test9-mm4/ (specified)
> -m /System.map (specified)
>
> Error (regular_file): read_ksyms stat /proc/ksyms failed
> No modules in ksyms, skipping objects
> No ksyms, skipping lsmod
> CPU: 0
> EIP: 0098:[<00005121>] Not tainted VLI
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010046
> esi: 0000a15a edi: 00000000 ebp: c151fe8c esp: c151fe5a
> ds: 00a0 es: 00a8 ss: 0068
> Stack: 00000cfe 0e5700a0 000b000b 9daba392 9d3a9b03 9ad10001 00000000 007b0001
> 9ab6007b 00000246 00020082 000bdfdc 00020090 00000002 000100a8 000000a0
> 9ce70000 0060c025 00020000 00000000 00000000 007b0000 007b0000 02460000
> Call Trace:
> Code: Bad EIP Value.
Looks like it died inside the machine's BIOS.
Please try reverting the three pnp patches:
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
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-1.patch
and let us know?
Other things to do would be:
- Add `initcall_debug' to the kernel boot command line, look up the final
initcall address in System.map
- Disable pnpbios in kernel config
- Upgrade the bios
Thanks.
> Looks like it died inside the machine's BIOS.
>
> Please try reverting the three pnp patches:
>
> 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
> 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-1.patch
>
> and let us know?
>
I reverted these and it works great!
> - Upgrade the bios
The bios is the latest so updating it would not of been a option.
--
*--* Mail: [email protected]
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://www.otak-k.com/~lawrence/
--------------------------------------
- - - - - - O t a k i n c . - - - - -
Lawrence Walton <[email protected]> wrote:
>
> > Looks like it died inside the machine's BIOS.
> >
> > Please try reverting the three pnp patches:
> >
> > 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
> > 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-1.patch
> >
> > and let us know?
> >
> I reverted these and it works great!
>
>
>
> > - Upgrade the bios
> The bios is the latest so updating it would not of been a option.
>
OK, thanks. Adam, those pnp patches are suspect...
On Thu, Nov 20, 2003 at 04:06:01PM -0800, Andrew Morton wrote:
> Lawrence Walton <[email protected]> wrote:
> >
> > > Looks like it died inside the machine's BIOS.
> > >
> > > Please try reverting the three pnp patches:
> > >
> > > 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
> > > 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-1.patch
> > >
> > > and let us know?
> > >
> > I reverted these and it works great!
> >
> >
> >
> > > - Upgrade the bios
> > The bios is the latest so updating it would not of been a option.
> >
>
> OK, thanks. Adam, those pnp patches are suspect...
Hmm, well it couldn't be patch 3 because it relates to isapnp. Patch
1 is the only patch that changes the PnPBIOS calls, and it has been
known to fix problems for some systems. Also it does what the actual
specifications recommend. You may just have a buggy system that's
triggered by the static resource calls. If so, we could use dynamic
instead resources when the DMI scan matches with this system. Patch
2 provides an option to disable the PnPBIOS proc interface, but it
should not affect PnPBIOS calls.
Lawrence, could you please test this again, only this time excluding
patch 1 and no others. If that doesn't work try excluding patch 2.
Thanks,
Adam
P.S.
Andrew, could you please review this patch for your tree.
# --------------------------------------------
# 03/11/15 [email protected] 1.1447
# [PnP] reserve resources specified by the PnPBIOS properly
#
# A bug prevents the PnP layer from reserving some of the resources
# specified by the PnPBIOS. As a result some systems will have
# unpredicable (random crashes etc.) problems because of resource
# conflicts, especially when PCMCIA support is enabled. This patch
# fixes the problem by ensuring that the proper resource data is
# reserved.
# --------------------------------------------
#
diff -Nru a/drivers/pnp/system.c b/drivers/pnp/system.c
--- a/drivers/pnp/system.c Sun Nov 16 00:25:14 2003
+++ b/drivers/pnp/system.c Sun Nov 16 00:25:14 2003
@@ -54,7 +54,7 @@
int i;
for (i=0;i<PNP_MAX_PORT;i++) {
- if (pnp_port_valid(dev, i))
+ if (!pnp_port_valid(dev, i))
/* end of resources */
continue;
if (pnp_port_start(dev, i) == 0)
Adam Belay [[email protected]] wrote:
> On Thu, Nov 20, 2003 at 04:06:01PM -0800, Andrew Morton wrote:
> > Lawrence Walton <[email protected]> wrote:
> > >
> > > > Looks like it died inside the machine's BIOS.
> > > >
> > > > Please try reverting the three pnp patches:
> > > >
> > > > 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
> > > > 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-1.patch
> > > >
> > > > and let us know?
> > > >
> > > I reverted these and it works great!
> > >
> > >
> > >
> > > > - Upgrade the bios
> > > The bios is the latest so updating it would not of been a option.
> > >
> >
> > OK, thanks. Adam, those pnp patches are suspect...
>
> Hmm, well it couldn't be patch 3 because it relates to isapnp. Patch
> 1 is the only patch that changes the PnPBIOS calls, and it has been
> known to fix problems for some systems. Also it does what the actual
> specifications recommend. You may just have a buggy system that's
> triggered by the static resource calls. If so, we could use dynamic
> instead resources when the DMI scan matches with this system. Patch
> 2 provides an option to disable the PnPBIOS proc interface, but it
> should not affect PnPBIOS calls.
>
> Lawrence, could you please test this again, only this time excluding
> patch 1 and no others. If that doesn't work try excluding patch 2.
>
> Thanks,
> Adam
>
> P.S.
Adam this worked great too.
My guess is that this board is a little different.
It's a Asus A7V333 with fireiwire and the raid.
--
*--* Mail: [email protected]
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://www.otak-k.com/~lawrence/
--------------------------------------
- - - - - - O t a k i n c . - - - - -