* [crash/panic] Linux-2.6.0-test9 @ 2003-11-03 7:12 Gary Wolfe 2003-11-03 8:52 ` Andrew Morton 2003-11-03 16:37 ` Linus Torvalds 0 siblings, 2 replies; 7+ messages in thread From: Gary Wolfe @ 2003-11-03 7:12 UTC (permalink / raw) To: linux-kernel Greetings, I have: Asus P4C800 Deluxe w/2.4GHz P4 (no HT and not 800Mhz bus) Tried test8 and, now, test9 and both exhibit same problem. The issue seems to be related to the PnPBIOS support under the Plug and Play Kconfig category. When enabled I get a crash of the form: Linux Plug and Play Support v0.97 (c) Adam Belay PnPBIOS: Scanning system for PnP BIOS support... PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350 PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000 general protection fault: 0000 [#1] CPU: 0 EIP: 0098:[<00002b60>] Not tainted EFLAGS: 00010083 EIP is at 0x2b60 eax: 000023d6 ebx: 0000007a ecx: 00010000 edx: 00000001 esi: dfed244e edi: 0000006d ebp: dfed0000 esp: dfed9eda ds: 00b0 es: 00b0 ss: 0068 Process Swapper (pid:1 threadinfo=dfed8000 task=c151b900) Stack: 000003d6 23d629d2 00000000 815d006d 0000d3ff 00010001 9f2c80fc 006dd408 9f2c0000 d3ff9f08 00060001 61f990c0c 010c010c 007b6054 0000007b 00a08000 601000b0 00a85fd6 00000082 000b0000 00010090 00a80000 00b00000 00a00001 Call Trace: Code: Bad EIP value. <0>Kernel panic: Attempted to kill init! ....blinking cursor and nothing else. If I remove the PNPBIOS option I get past this point. I would be happy to email my full .config should anyone wish to look at it. I'd also be happy to test any patches anyone may have for this issue. Thanks, Gary ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 7:12 [crash/panic] Linux-2.6.0-test9 Gary Wolfe @ 2003-11-03 8:52 ` Andrew Morton 2003-11-03 14:53 ` Gary Wolfe 2003-11-03 18:07 ` Manfred Spraul 2003-11-03 16:37 ` Linus Torvalds 1 sibling, 2 replies; 7+ messages in thread From: Andrew Morton @ 2003-11-03 8:52 UTC (permalink / raw) To: Gary Wolfe; +Cc: linux-kernel, Manfred Spraul Gary Wolfe <gpwolfe@cableone.net> wrote: > > Greetings, > > I have: > > Asus P4C800 Deluxe w/2.4GHz P4 (no HT and not 800Mhz bus) > > Tried test8 and, now, test9 and both exhibit same problem. > > The issue seems to be related to the PnPBIOS support under the Plug and > Play Kconfig category. When enabled I get a crash of the form: > > Linux Plug and Play Support v0.97 (c) Adam Belay > PnPBIOS: Scanning system for PnP BIOS support... > PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350 > PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000 > general protection fault: 0000 [#1] > CPU: 0 > EIP: 0098:[<00002b60>] Not tainted > EFLAGS: 00010083 > EIP is at 0x2b60 > eax: 000023d6 ebx: 0000007a ecx: 00010000 edx: 00000001 > esi: dfed244e edi: 0000006d ebp: dfed0000 esp: dfed9eda Your stack pointer became misaligned. I thought Manfred fixed that? You don't have nmi_watchdog enabled on the kernel boot command line do you? > ds: 00b0 es: 00b0 ss: 0068 > Process Swapper (pid:1 threadinfo=dfed8000 task=c151b900) > Stack: 000003d6 23d629d2 00000000 815d006d 0000d3ff 00010001 9f2c80fc > 006dd408 > 9f2c0000 d3ff9f08 00060001 61f990c0c 010c010c 007b6054 0000007b 00a08000 > 601000b0 00a85fd6 00000082 000b0000 00010090 00a80000 00b00000 00a00001 > Call Trace: > > Code: Bad EIP value. > <0>Kernel panic: Attempted to kill init! > > ....blinking cursor and nothing else. > > If I remove the PNPBIOS option I get past this point. I would be happy > to email my full .config should anyone wish to look at it. I'd also be > happy to test any patches anyone may have for this issue. > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 8:52 ` Andrew Morton @ 2003-11-03 14:53 ` Gary Wolfe 2003-11-03 18:07 ` Manfred Spraul 1 sibling, 0 replies; 7+ messages in thread From: Gary Wolfe @ 2003-11-03 14:53 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, Manfred Spraul Andrew Morton wrote: >Gary Wolfe <gpwolfe@cableone.net> wrote: > > >>Greetings, >> >>I have: >> >>Asus P4C800 Deluxe w/2.4GHz P4 (no HT and not 800Mhz bus) >> >>Tried test8 and, now, test9 and both exhibit same problem. >> >>The issue seems to be related to the PnPBIOS support under the Plug and >>Play Kconfig category. When enabled I get a crash of the form: >> >>Linux Plug and Play Support v0.97 (c) Adam Belay >>PnPBIOS: Scanning system for PnP BIOS support... >>PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350 >>PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000 >>general protection fault: 0000 [#1] >>CPU: 0 >>EIP: 0098:[<00002b60>] Not tainted >>EFLAGS: 00010083 >>EIP is at 0x2b60 >>eax: 000023d6 ebx: 0000007a ecx: 00010000 edx: 00000001 >>esi: dfed244e edi: 0000006d ebp: dfed0000 esp: dfed9eda >> >> > >Your stack pointer became misaligned. I thought Manfred fixed that? >You don't have nmi_watchdog enabled on the kernel boot command line >do you? > > I do not. The command line, through grub after the kernel spec is, ro root=/dev/hda5 hdc=ide-scsi By the way I thought of some more information that may, or may not, matter in this case. This is all based on RH90, upgraded based on the Documentation/Changes file of course, and I'm using gcc version 3.2.2 200330222 (Red Hat Linux 3.2.2-5). Thanks for the response, Gary > > >>ds: 00b0 es: 00b0 ss: 0068 >>Process Swapper (pid:1 threadinfo=dfed8000 task=c151b900) >>Stack: 000003d6 23d629d2 00000000 815d006d 0000d3ff 00010001 9f2c80fc >>006dd408 >>9f2c0000 d3ff9f08 00060001 61f990c0c 010c010c 007b6054 0000007b 00a08000 >>601000b0 00a85fd6 00000082 000b0000 00010090 00a80000 00b00000 00a00001 >>Call Trace: >> >>Code: Bad EIP value. >><0>Kernel panic: Attempted to kill init! >> >>....blinking cursor and nothing else. >> >>If I remove the PNPBIOS option I get past this point. I would be happy >>to email my full .config should anyone wish to look at it. I'd also be >>happy to test any patches anyone may have for this issue. >> >> >> > > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 8:52 ` Andrew Morton 2003-11-03 14:53 ` Gary Wolfe @ 2003-11-03 18:07 ` Manfred Spraul 1 sibling, 0 replies; 7+ messages in thread From: Manfred Spraul @ 2003-11-03 18:07 UTC (permalink / raw) To: Andrew Morton; +Cc: Gary Wolfe, linux-kernel Andrew Morton wrote: >Gary Wolfe <gpwolfe@cableone.net> wrote: > > >>Greetings, >> >>I have: >> >>Asus P4C800 Deluxe w/2.4GHz P4 (no HT and not 800Mhz bus) >> >>Tried test8 and, now, test9 and both exhibit same problem. >> >>The issue seems to be related to the PnPBIOS support under the Plug and >>Play Kconfig category. When enabled I get a crash of the form: >> >>Linux Plug and Play Support v0.97 (c) Adam Belay >>PnPBIOS: Scanning system for PnP BIOS support... >>PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350 >>PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000 >>general protection fault: 0000 [#1] >>CPU: 0 >>EIP: 0098:[<00002b60>] Not tainted >>EFLAGS: 00010083 >>EIP is at 0x2b60 >>eax: 000023d6 ebx: 0000007a ecx: 00010000 edx: 00000001 >>esi: dfed244e edi: 0000006d ebp: dfed0000 esp: dfed9eda >> >> > >Your stack pointer became misaligned. I thought Manfred fixed that? >You don't have nmi_watchdog enabled on the kernel boot command line >do you? > > I fixed the double-oops caused by misaligned stack pointers, and the oops if kmem_cache_alloc is called with an misaligned stack pointer. In this case it seem to be an oops in the bios itself. Gary: did it work with 2.4? Are there any bios upgrades you could try? My guess is that the bios is just buggy. -- Manfred ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 7:12 [crash/panic] Linux-2.6.0-test9 Gary Wolfe 2003-11-03 8:52 ` Andrew Morton @ 2003-11-03 16:37 ` Linus Torvalds 2003-11-03 23:25 ` Adam Belay 1 sibling, 1 reply; 7+ messages in thread From: Linus Torvalds @ 2003-11-03 16:37 UTC (permalink / raw) To: Gary Wolfe; +Cc: Kernel Mailing List, Adam Belay On Mon, 3 Nov 2003, Gary Wolfe wrote: > > Tried test8 and, now, test9 and both exhibit same problem. > > The issue seems to be related to the PnPBIOS support under the Plug and > Play Kconfig category. When enabled I get a crash of the form: Yes. The crash happens inside the BIOS itself, and the kernel doesn't really have any control over it. The most Adam could possibly do is to avoid calling the BIOS (or at least avoid _certain_ calls), but that would require knowing what it is that triggers it. Has PnP support ever worked for you on this board? Sometimes the solution is to just say "it's dead, Jim", and just not enable it. There are few enough systems that actually want PnP. Adam, any ideas? Linus ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 16:37 ` Linus Torvalds @ 2003-11-03 23:25 ` Adam Belay 2003-11-08 19:04 ` Gary Wolfe 0 siblings, 1 reply; 7+ messages in thread From: Adam Belay @ 2003-11-03 23:25 UTC (permalink / raw) To: Linus Torvalds; +Cc: Gary Wolfe, Kernel Mailing List On Mon, Nov 03, 2003 at 08:37:30AM -0800, Linus Torvalds wrote: > > On Mon, 3 Nov 2003, Gary Wolfe wrote: > > > > Tried test8 and, now, test9 and both exhibit same problem. > > > > The issue seems to be related to the PnPBIOS support under the Plug and > > Play Kconfig category. When enabled I get a crash of the form: > > Yes. The crash happens inside the BIOS itself, and the kernel doesn't > really have any control over it. The most Adam could possibly do is to > avoid calling the BIOS (or at least avoid _certain_ calls), but that would > require knowing what it is that triggers it. One of the most common triggers is requesting for the dynamic (currently assigned) resource information. This tends to happen with particular device nodes, from what I've seen typically the mouse controller, but I don't have a large enough sample space to make a generalization. I've made some modifications to the PnPBIOS call function in the past and they seem to solve this problem for many of the buggy systems. > > Has PnP support ever worked for you on this board? Sometimes the solution > is to just say "it's dead, Jim", and just not enable it. There are few > enough systems that actually want PnP. > > Adam, any ideas? > > Linus I've included a patch that encourages the PnPBIOS to make more conservative calls and it should help with situations such as this one. I'd like to see a dmi_scan for this system, if it is possible, so I can blacklist certain PnPBIOS features on it. I've also attached a patch that makes the pnpbios proc interface an optional feature. The proc interface allows users to make PnPBIOS calls without restrictions and as a result can cause problems on some buggy systems. (one example is the recent ESCD problems posted on lkml) Finally, the Kconfig help has been updated to better reflect this viewpoint. Please let me know if any of this helps. I'd predict it will boot properly with the first patch applied. Thanks, Adam --- a/drivers/pnp/pnpbios/core.c 2003-10-25 18:42:49.000000000 +0000 +++ b/drivers/pnp/pnpbios/core.c 2003-11-03 20:12:08.000000000 +0000 @@ -353,16 +353,8 @@ for(nodenum=0; nodenum<0xff; ) { u8 thisnodenum = nodenum; - /* eventually we will want to use PNPMODE_STATIC here but for now - * dynamic will help us catch buggy bioses to add to the blacklist. - */ - if (!pnpbios_dont_use_current_config) { - if (pnp_bios_get_dev_node(&nodenum, (char )PNPMODE_DYNAMIC, node)) - break; - } else { - if (pnp_bios_get_dev_node(&nodenum, (char )PNPMODE_STATIC, node)) - break; - } + if (pnp_bios_get_dev_node(&nodenum, (char )PNPMODE_STATIC, node)) + break; nodes_got++; dev = pnpbios_kmalloc(sizeof (struct pnp_dev), GFP_KERNEL); if (!dev) diff -urN a/drivers/pnp/Kconfig b/drivers/pnp/Kconfig --- a/drivers/pnp/Kconfig 2003-10-25 18:43:39.000000000 +0000 +++ b/drivers/pnp/Kconfig 2003-11-03 22:01:26.000000000 +0000 @@ -30,33 +30,9 @@ comment "Protocols" depends on PNP -config ISAPNP - bool "ISA Plug and Play support (EXPERIMENTAL)" - depends on PNP && EXPERIMENTAL - help - Say Y here if you would like support for ISA Plug and Play devices. - Some information is in <file:Documentation/isapnp.txt>. +source "drivers/pnp/isapnp/Kconfig" - If unsure, say Y. - -config PNPBIOS - bool "Plug and Play BIOS support (EXPERIMENTAL)" - depends on PNP && EXPERIMENTAL - ---help--- - Linux uses the PNPBIOS as defined in "Plug and Play BIOS - Specification Version 1.0A May 5, 1994" to autodetect built-in - mainboard resources (e.g. parallel port resources). - - Some features (e.g. event notification, docking station information, - ISAPNP services) are not used. - - Note: ACPI is expected to supersede PNPBIOS some day, currently it - co-exists nicely. - - See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools, - or have a look at /proc/bus/pnp. - - If unsure, say Y. +source "drivers/pnp/pnpbios/Kconfig" endmenu diff -urN a/drivers/pnp/isapnp/Kconfig b/drivers/pnp/isapnp/Kconfig --- a/drivers/pnp/isapnp/Kconfig 1970-01-01 00:00:00.000000000 +0000 +++ b/drivers/pnp/isapnp/Kconfig 2003-11-03 22:01:54.000000000 +0000 @@ -0,0 +1,11 @@ +# +# ISA Plug and Play configuration +# +config ISAPNP + bool "ISA Plug and Play support (EXPERIMENTAL)" + depends on PNP && EXPERIMENTAL + help + Say Y here if you would like support for ISA Plug and Play devices. + Some information is in <file:Documentation/isapnp.txt>. + + If unsure, say Y. diff -urN a/drivers/pnp/pnpbios/Kconfig b/drivers/pnp/pnpbios/Kconfig --- a/drivers/pnp/pnpbios/Kconfig 1970-01-01 00:00:00.000000000 +0000 +++ b/drivers/pnp/pnpbios/Kconfig 2003-11-03 22:13:30.000000000 +0000 @@ -0,0 +1,41 @@ +# +# Plug and Play BIOS configuration +# +config PNPBIOS + bool "Plug and Play BIOS support (EXPERIMENTAL)" + depends on PNP && EXPERIMENTAL + ---help--- + Linux uses the PNPBIOS as defined in "Plug and Play BIOS + Specification Version 1.0A May 5, 1994" to autodetect built-in + mainboard resources (e.g. parallel port resources). + + Some features (e.g. event notification, docking station information, + ISAPNP services) are not currently implemented. + + If you would like the kernel to detect and allocate resources to + your mainboard devices (on some systems they are disabled by the + BIOS) say Y here. Also the PNPBIOS can help prevent resource + conflicts between mainboard devices and other bus devices. + + Note: ACPI is expected to supersede PNPBIOS some day, currently it + co-exists nicely. If you have a non-ISA system that supports ACPI, + you probably don't need PNPBIOS support. + +config PNPBIOS_PROC_FS + bool "Plug and Play BIOS /proc interface" + depends on PNPBIOS && PROC_FS + ---help--- + If you say Y here and to "/proc file system support", you will be + able to directly access the PNPBIOS. This includes resource + allocation, ESCD, and other PNPBIOS services. Using this + interface is potentially dangerous because the PNPBIOS driver will + not be notified of any resource changes made by writting directly. + Also some buggy systems will fault when accessing certain features + in the PNPBIOS /proc interface (e.g. ESCD). + + See the latest pcmcia-cs (stand-alone package) for a nice set of + PNPBIOS /proc interface tools (lspnp and setpnp). + + Unless you are debugging or have other specific reasons, it is + recommended that you say N here. + diff -urN a/drivers/pnp/pnpbios/Makefile b/drivers/pnp/pnpbios/Makefile --- a/drivers/pnp/pnpbios/Makefile 2003-10-25 18:44:35.000000000 +0000 +++ b/drivers/pnp/pnpbios/Makefile 2003-11-03 22:10:53.000000000 +0000 @@ -2,6 +2,6 @@ # Makefile for the kernel PNPBIOS driver. # -pnpbios-proc-$(CONFIG_PROC_FS) = proc.o +pnpbios-proc-$(CONFIG_PNPBIOS_PROC_FS) = proc.o obj-y := core.o bioscalls.o rsparser.o $(pnpbios-proc-y) diff -urN a/drivers/pnp/pnpbios/pnpbios.h b/drivers/pnp/pnpbios/pnpbios.h --- a/drivers/pnp/pnpbios/pnpbios.h 2003-10-25 18:43:17.000000000 +0000 +++ b/drivers/pnp/pnpbios/pnpbios.h 2003-11-03 22:11:38.000000000 +0000 @@ -36,7 +36,7 @@ extern void pnpbios_print_status(const char * module, u16 status); extern void pnpbios_calls_init(union pnp_bios_install_struct * header); -#ifdef CONFIG_PROC_FS +#ifdef CONFIG_PNPBIOS_PROC_FS extern int pnpbios_interface_attach_device(struct pnp_bios_node * node); extern int pnpbios_proc_init (void); extern void pnpbios_proc_exit (void); @@ -44,4 +44,4 @@ static inline int pnpbios_interface_attach_device(struct pnp_bios_node * node) { return 0; } static inline int pnpbios_proc_init (void) { return 0; } static inline void pnpbios_proc_exit (void) { ; } -#endif /* CONFIG_PROC */ +#endif /* CONFIG_PNPBIOS_PROC_FS */ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [crash/panic] Linux-2.6.0-test9 2003-11-03 23:25 ` Adam Belay @ 2003-11-08 19:04 ` Gary Wolfe 0 siblings, 0 replies; 7+ messages in thread From: Gary Wolfe @ 2003-11-08 19:04 UTC (permalink / raw) To: Adam Belay; +Cc: Linus Torvalds, Kernel Mailing List [-- Attachment #1: Type: text/plain, Size: 3709 bytes --] Adam Belay wrote: >On Mon, Nov 03, 2003 at 08:37:30AM -0800, Linus Torvalds wrote: > > >>On Mon, 3 Nov 2003, Gary Wolfe wrote: >> >> >>>Tried test8 and, now, test9 and both exhibit same problem. >>> >>>The issue seems to be related to the PnPBIOS support under the Plug and >>>Play Kconfig category. When enabled I get a crash of the form: >>> >>> >>Yes. The crash happens inside the BIOS itself, and the kernel doesn't >>really have any control over it. The most Adam could possibly do is to >>avoid calling the BIOS (or at least avoid _certain_ calls), but that would >>require knowing what it is that triggers it. >> >> > >One of the most common triggers is requesting for the dynamic (currently >assigned) resource information. This tends to happen with particular device >nodes, from what I've seen typically the mouse controller, but I don't have a >large enough sample space to make a generalization. I've made some >modifications to the PnPBIOS call function in the past and they seem to solve >this problem for many of the buggy systems. > > > >>Has PnP support ever worked for you on this board? Sometimes the solution >>is to just say "it's dead, Jim", and just not enable it. There are few >>enough systems that actually want PnP. >> >>Adam, any ideas? >> >> Linus >> >> > >I've included a patch that encourages the PnPBIOS to make more conservative >calls and it should help with situations such as this one. I'd like to see a >dmi_scan for this system, if it is possible, so I can blacklist certain PnPBIOS >features on it. I've also attached a patch that makes the pnpbios proc >interface an optional feature. The proc interface allows users to make PnPBIOS >calls without restrictions and as a result can cause problems on some buggy >systems. (one example is the recent ESCD problems posted on lkml) Finally, the >Kconfig help has been updated to better reflect this viewpoint. > >Please let me know if any of this helps. I'd predict it will boot properly with >the first patch applied. > >Thanks, >Adam > > > Sorry it took me so long to get back but work is taking up most of my free time as of late. In any event, I applied the patch to a clean test9, enabled the PNP support and the PNPBios sub option. I did not check the sub option, the creation of the /proc interface. It still crashes by the way. Here's the output. Linux Plug and Play Support v0.97 (c) Adam Belay PnPBIOS: Scanning system for PnP BIOS support... PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350 PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000 general protection fault: 0000 [#1] CPU: 0 EIP: 0098:[<00002b60>] Not tainted EFLAGS: 00010087 EIP is at 0x2b60 eax: 000033d8 ebx: 0000007b ecx: 00020000 edx: 00000002 esi: dfed244e edi: 0000004d ebp: dfed0000 esp: dfed9ee6 ds: 00b0 es: 00b0 ss:0068 Process swapper (pid: 1, threadinfo=dfed8000 task=c151b900) Stack: 000003d8 33d829d2 00000000 815d004d 0004cf3a 00020002 9f2c80fc cfeacff2 61f90909 01090109 007b6054 0000007b 00a08000 601000b0 00a85fd6 00000082 000b0000 00010090 00b00000 00a00002 90590000 0060c01b 00020000 Call Trace: Code: Bad EIP value. <0>Kernel panic: Attempted to kill init! I don't know if you need all of that again but I figured it couldn't hurt. Some of the stuff looks different from before. As far as the dmi_dump goes, I'm not certain what you want or how to get that. The best I could find out that sounds reasonable is the dmidecode app. I've attached the output of that command. If this is not what you wanted please let me know how to get what you want and I'll strive to get it to you. Thanks for looking into this, Gary [-- Attachment #2: p4c800_dmidecode.txt --] [-- Type: text/plain, Size: 11254 bytes --] PNP BIOS present. RSD PTR found at 0xF9E60 checksum failed. OEM ACPIAM SMBIOS 2.3 present. DMI 2.3 present. 68 structures occupying 2057 bytes. DMI table at 0x000F04B0. Handle 0x0000 DMI type 0, 20 bytes. BIOS Information Block Vendor: American Megatrends Inc. Version: 080009 Release: 09/02/2003 BIOS base: 0xF0000 ROM size: 448K Capabilities: Flags: 0x000000017F8BDE90 Handle 0x0001 DMI type 1, 25 bytes. System Information Block Vendor: To Be Filled By O.E.M. Product: To Be Filled By O.E.M. Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. Handle 0x0002 DMI type 2, 8 bytes. Board Information Block Vendor: ASUSTeK Computer Inc. Product: P4C800 Version: Rev 1.xx Serial Number: MB-1234567890 Handle 0x0003 DMI type 3, 17 bytes. Chassis Information Block Vendor: Chassis Manufacture Chassis Type: Desktop Version: Chassis Version Serial Number: Chassis Serial Number Asset Tag: Asset-1234567890 Handle 0x0004 DMI type 4, 35 bytes. Processor Socket Designation: CPU 1 Processor Type: Central Processor Processor Family: Processor Manufacturer: Intel Processor Version: Intel(R) Pentium(R) 4 CPU 2.40GHz Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Vendor Part Number: To Be Filled By O.E.M. Handle 0x0005 DMI type 7, 19 bytes. Cache Socket: L1-Cache L1 Internal Cache: L1 Cache Size: 8K L1 Cache Maximum: 8K L1 Cache Type: Pipeline burst Handle 0x0006 DMI type 7, 19 bytes. Cache Socket: L2-Cache L2 Internal Cache: L2 Cache Size: 512K L2 Cache Maximum: 512K L2 Cache Type: Pipeline burst Handle 0x0007 DMI type 7, 19 bytes. Cache Socket: L3-Cache L3 Internal Cache: disabled L3 Cache Size: 0K L3 Cache Maximum: 0K L3 Cache Type: Unknown Handle 0x0008 DMI type 5, 24 bytes. Memory Controller Handle 0x0009 DMI type 6, 12 bytes. Memory Bank Socket: DIMM A1 Banks: 1 0 Type: DIMM SDRAM Installed Size: 512Mbyte (Double sided) Enabled Size: 512Mbyte (Double sided) Handle 0x000A DMI type 6, 12 bytes. Memory Bank Socket: DIMM A2 Banks: 3 2 Type: UNKNOWN Installed Size: Not Installed Enabled Size: Not Installed Handle 0x000B DMI type 6, 12 bytes. Memory Bank Socket: DIMM B1 Banks: 5 4 Type: UNKNOWN Installed Size: Not Installed Enabled Size: Not Installed Handle 0x000C DMI type 6, 12 bytes. Memory Bank Socket: DIMM B2 Banks: 7 6 Type: UNKNOWN Installed Size: Not Installed Enabled Size: Not Installed Handle 0x000D DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port Handle 0x000E DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x000F DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0010 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0011 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB3 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0012 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB4 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0013 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB5 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0014 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB6 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0015 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB7 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0016 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: USB8 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0017 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: LPT 1 External Connector Type: DB-25 pin male Port Type: Parallel Port ECP/EPP Handle 0x0018 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: COM 1 External Connector Type: DB-9 pin male Port Type: Serial Port 16650A Compatible Handle 0x0019 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: COM 2 External Connector Type: DB-9 pin male Port Type: Serial Port 16650A Compatible Handle 0x001A DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: Audio Mic In External Connector Type: Mini-jack (headphones) Port Type: Audio Port Handle 0x001B DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: Audio Line In External Connector Type: Mini-jack (headphones) Port Type: Audio Port Handle 0x001C DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: Audio Line Out External Connector Type: Mini-jack (headphones) Port Type: Audio Port Handle 0x001D DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: LAN External Connector Type: RJ-45 Port Type: Network Port Handle 0x001E DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: FireWire 1 External Connector Type: 1394 Port Type: FireWire (IEEE P1394) Handle 0x001F DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: FireWire 2 External Connector Type: 1394 Port Type: FireWire (IEEE P1394) Handle 0x0020 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: MIDI External Connector Type: DB-15 pin female Port Type: MIDI Port Handle 0x0021 DMI type 8, 9 bytes. Port Connector Internal Designator: Internal Connector Type: None External Designator: Joy Stick External Connector Type: DB-15 pin female Port Type: Joy Stick Port Handle 0x0022 DMI type 8, 9 bytes. Port Connector Internal Designator: AUX Internal Connector Type: On Board Sound Input from CD-ROM External Designator: External Connector Type: None Port Type: Audio Port Handle 0x0023 DMI type 8, 9 bytes. Port Connector Internal Designator: CD Internal Connector Type: On Board Sound Input from CD-ROM External Designator: External Connector Type: None Port Type: Audio Port Handle 0x0024 DMI type 8, 9 bytes. Port Connector Internal Designator: PRI_IDE Internal Connector Type: On Board IDE External Designator: External Connector Type: None Port Type: Other Handle 0x0025 DMI type 8, 9 bytes. Port Connector Internal Designator: SEC_IDE Internal Connector Type: On Board IDE External Designator: External Connector Type: None Port Type: Other Handle 0x0026 DMI type 8, 9 bytes. Port Connector Internal Designator: FLOPPY Internal Connector Type: On Board Floppy External Designator: External Connector Type: None Port Type: Other Handle 0x0027 DMI type 8, 9 bytes. Port Connector Internal Designator: CHA_FAN Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x0028 DMI type 8, 9 bytes. Port Connector Internal Designator: CPU_FAN Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x0029 DMI type 8, 9 bytes. Port Connector Internal Designator: PWR_FAN Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002A DMI type 8, 9 bytes. Port Connector Internal Designator: ATXPWR Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002B DMI type 8, 9 bytes. Port Connector Internal Designator: CHASSIS Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002C DMI type 8, 9 bytes. Port Connector Internal Designator: FP_AUDIO Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002D DMI type 8, 9 bytes. Port Connector Internal Designator: SATA1 Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002E DMI type 8, 9 bytes. Port Connector Internal Designator: SATA2 Internal Connector Type: Other External Designator: External Connector Type: None Port Type: Other Handle 0x002F DMI type 9, 13 bytes. Card Slot Slot: AGP Type: 32bit Long Status: Available. Slot Features: 3.3v Handle 0x0030 DMI type 9, 13 bytes. Card Slot Slot: PCI1 Type: 32bit Long PCI Status: Available. Slot Features: 5v 3.3v Handle 0x0031 DMI type 9, 13 bytes. Card Slot Slot: PCI2 Type: 32bit Long PCI Status: Available. Slot Features: 5v 3.3v Handle 0x0032 DMI type 9, 13 bytes. Card Slot Slot: PCI3 Type: 32bit Long PCI Status: Available. Slot Features: 5v 3.3v Handle 0x0033 DMI type 9, 13 bytes. Card Slot Slot: PCI4 Type: 32bit Long PCI Status: Available. Slot Features: 5v 3.3v Handle 0x0034 DMI type 9, 13 bytes. Card Slot Slot: PCI5 Type: 32bit Long PCI Status: Available. Slot Features: 5v 3.3v Handle 0x0035 DMI type 10, 6 bytes. On Board Devices Information Description: 3COM 3C940 : Enabled Type: Handle 0x0036 DMI type 11, 5 bytes. OEM Data To Be Filled By O.E.M. To Be Filled By O.E.M. To Be Filled By O.E.M. To Be Filled By O.E.M. Handle 0x0037 DMI type 13, 22 bytes. BIOS Language Information Handle 0x0038 DMI type 16, 15 bytes. Physical Memory Array Handle 0x0039 DMI type 19, 15 bytes. Memory Array Mapped Address Handle 0x003A DMI type 17, 27 bytes. Memory Device Handle 0x003B DMI type 20, 19 bytes. Memory Device Mapped Address Handle 0x003C DMI type 17, 27 bytes. Memory Device Handle 0x003D DMI type 20, 19 bytes. Memory Device Mapped Address Handle 0x003E DMI type 17, 27 bytes. Memory Device Handle 0x003F DMI type 20, 19 bytes. Memory Device Mapped Address Handle 0x0040 DMI type 17, 27 bytes. Memory Device Handle 0x0041 DMI type 20, 19 bytes. Memory Device Mapped Address Handle 0x0042 DMI type 32, 20 bytes. System Boot Information Handle 0x0043 DMI type 127, 4 bytes. End-of-Table ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-11-08 19:05 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-11-03 7:12 [crash/panic] Linux-2.6.0-test9 Gary Wolfe 2003-11-03 8:52 ` Andrew Morton 2003-11-03 14:53 ` Gary Wolfe 2003-11-03 18:07 ` Manfred Spraul 2003-11-03 16:37 ` Linus Torvalds 2003-11-03 23:25 ` Adam Belay 2003-11-08 19:04 ` Gary Wolfe
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox