Re: Kernel not booting....Immediate crash
On Sat, 9 Nov 2002, David Schultz wrote: Thus spake Mitsuru IWASAKI [EMAIL PROTECTED]: Hmmm, I didn't notice that there is a BIOS which requires memory area below 640K even when calling INT 15H/E820. We cannot trust that today's BOISes have INT 12H, so it's difficult to determine base memory size w/o INT 15H/E820. You keep saying this, which really surprises me, because the int 12h interface has been standard for over two decades. I have not heard any great clammoring that DOS and NetBSD fail to boot on modern machines, and yet they both use int 12h. Are you *sure* int 12h is really broken, or do you think perhaps the breakage you're seeing is a side-effect of another bug? Does int 12h work in real mode? Exactly what hardware has this problem? Perhaps the problem with int 0x12 is the same as the one with int 0x15. Old implementations of int 0x12 just read the word at 0x40:0x13 in real or vm86 mode. This only requires physical page 0 to be mapped readable to work in vm86 calls. New implementations might want more. They could reasonably expect all of the first MB of physical memory to be mapped r/w into vm86 space. It's not clear that any BIOS call works in vm86 mode. BIOS calls could unreasonably expect to access all of memory as if in real mode (e.g., they could stash their variables in extended memory and use the himem hack or a switch to protected mode to access them). Also, you mentioneded earlier that Linux doesn't use int 12h anymore. But notice that they call 15:E820 in real mode, rather than turning on virtual memory and then temporarily mapping an arbitrary chunk of the first 640K of RAM. Why don't you just put the memory size detection code in locore.s? I'd be happy to help out with this, although my time is constrained after Monday. locore.s runs entirely in protected mode. It could switch between real and protected mode like the boot code does, but that would defeat the point of the (not very well designed) division of labour between the boot code and locore -- the complications for real mode are supposed to be limited to the boot code. Of course, they have been replaced by larger complications and bugs for vm86 mode :-(. More in another reply. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Thus spake Bruce Evans [EMAIL PROTECTED]: Perhaps the problem with int 0x12 is the same as the one with int 0x15. Old implementations of int 0x12 just read the word at 0x40:0x13 in real or vm86 mode. This only requires physical page 0 to be mapped readable to work in vm86 calls. New implementations might want more. They could reasonably expect all of the first MB of physical memory to be mapped r/w into vm86 space. It's not clear that any BIOS call works in vm86 mode. BIOS calls could unreasonably expect to access all of memory as if in real mode (e.g., they could stash their variables in extended memory and use the himem hack or a switch to protected mode to access them). Could be. I would hope that mapping page 0, the BIOS data segment, and the EBDA would solve the problem, but there's still a chicken-and-egg problem with doing this in vm86 mode. I haven't heard any additional details from Iwasaki-san, but making the memory determination in vm86 mode seems fundamentally broken regardless. Also, you mentioneded earlier that Linux doesn't use int 12h anymore. But notice that they call 15:E820 in real mode, rather than turning on virtual memory and then temporarily mapping an arbitrary chunk of the first 640K of RAM. Why don't you just put the memory size detection code in locore.s? I'd be happy to help out with this, although my time is constrained after Monday. locore.s runs entirely in protected mode. It could switch between real and protected mode like the boot code does, but that would defeat the point of the (not very well designed) division of labour between the boot code and locore -- the complications for real mode are supposed to be limited to the boot code. Of course, they have been replaced by larger complications and bugs for vm86 mode :-(. More in another reply. That is why I'm surprised by your earlier post where you say that it's a bad idea to take the basemem value from the boot code. As it is, the kernel duplicates much of the memory determination code of the boot loader. I would think it could at least rely on bootinfo.bi_basemem when that field is nonzero. If these values in bootinfo are going to remain unused, they should be removed, but I think a far better solution is to start using them. In fact, the interface could be extended to pass the int 15h:e820h memory map to the kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Fri, 8 Nov 2002 11:05:32 -0800 (PST), Nate Lawson [EMAIL PROTECTED] said: Nate Try disabling acpi: Nate echo hint.acpi.0.disable=1 /boot/device.hints Nate My IBM laptop does not work with ACPI yet. Hi, I don't think acpi has got anything to do with his. I still had this problem even after removing the acpi module. Regards Sid -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Fri, 08 Nov 2002 16:14:06 -0800, Terry Lambert [EMAIL PROTECTED] said: Terry Or look in the -current archives; Mitsuru IWASAKI posted a patch Terry yesterday at 11:29 PM. Terry http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1206362+0+current/freebsd-current Hi, I have applied this patch and my machine finally boots up fine without a prob. Will this patch go into -current ? Mitsuru ? TIA Regards Sid -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Thus spake Mitsuru IWASAKI [EMAIL PROTECTED]: Hmmm, I didn't notice that there is a BIOS which requires memory area below 640K even when calling INT 15H/E820. We cannot trust that today's BOISes have INT 12H, so it's difficult to determine base memory size w/o INT 15H/E820. You keep saying this, which really surprises me, because the int 12h interface has been standard for over two decades. I have not heard any great clammoring that DOS and NetBSD fail to boot on modern machines, and yet they both use int 12h. Are you *sure* int 12h is really broken, or do you think perhaps the breakage you're seeing is a side-effect of another bug? Does int 12h work in real mode? Exactly what hardware has this problem? Also, you mentioneded earlier that Linux doesn't use int 12h anymore. But notice that they call 15:E820 in real mode, rather than turning on virtual memory and then temporarily mapping an arbitrary chunk of the first 640K of RAM. Why don't you just put the memory size detection code in locore.s? I'd be happy to help out with this, although my time is constrained after Monday. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Fri, 08 Nov 2002 16:29:43 +0900 (JST), Mitsuru IWASAKI [EMAIL PROTECTED] said: Mitsuru Thanks Mitsuru Index: machdep.c Mitsuru === Mitsuru RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v Mitsuru retrieving revision 1.545 Yay, Yay, Thanks so much. My Kernel Compiles and boots too :D of course, I have disabled acpi , since my machine hangs if I boot with the acpi module loaded. Despite the fact that there is a bug registered, no one seems to have looked at it :( Regards Sid -- Any small object that is accidentally dropped will hide under a larger object. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002, David Rhodu wrote: Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Try disabling acpi: echo hint.acpi.0.disable=1 /boot/device.hints My IBM laptop does not work with ACPI yet. Fatal trap 12: page fault while in vm86 mode fault virtual address= 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer= 0x0:0xfb4 frame pointer= 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags= interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message yeah, I've been getting the same thing with 4.7 and 5.0 on a few machines What is the type of machine you are running on? Most of mine were IBM's. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
- Nate Lawson's Original Message - On Thu, 7 Nov 2002, David Rhodu wrote: Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Try disabling acpi: echo hint.acpi.0.disable=1 /boot/device.hints I appear to be having the exact same problem with a new dual Xeon system. It boots 4.7 correctly. The header from a 4.7 dmesg shows: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD RELENG_4_7_0_RELEASE #0: Fri Nov 8 12:08:15 GMT 2002 root@:/usr/src/sys/compile/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium 4 (2791.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,b28,ACC,b31 real memory = 1073676288 (1048512K bytes) avail memory = 1039872000 (1015500K bytes) Preloaded elf kernel kernel at 0xc050e000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 19 entries at 0xc00f30a0 Trying to boot from a 5.0 iso fails immediately after loading the acpi.ko module. It panics with no traceback available. Breaking into the boot sequence and issuing: set hint.acpi.0.disable=1 has no effect. Any other ideas on how to boot and get 5.0 installed onto this hardware? Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Thus spake Sidcarter [EMAIL PROTECTED]: Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 ^^^ That's a region of memory right before the 640K mark, and your BIOS is trying to use it. This used to work, but revision 1.544 of src/sys/i386/i386/machdep.c moved the code that mapped in those pages until *after* they need to be used. I (unsuccessfully) petitioned the committer who made the change to revert it, so for now you'll have to manually remove it, being careful not to step on the changes introduced in revisions 1.545 through 1.547. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
David Schultz wrote: Thus spake Sidcarter [EMAIL PROTECTED]: Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 ^^^ That's a region of memory right before the 640K mark, and your BIOS is trying to use it. This used to work, but revision 1.544 of src/sys/i386/i386/machdep.c moved the code that mapped in those pages until *after* they need to be used. I (unsuccessfully) petitioned the committer who made the change to revert it, so for now you'll have to manually remove it, being careful not to step on the changes introduced in revisions 1.545 through 1.547. Or look in the -current archives; Mitsuru IWASAKI posted a patch yesterday at 11:29 PM. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1206362+0+current/freebsd-current -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb %al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message yeah, I've been getting the same thing with 4.7 and 5.0 on a few machines What is the type of machine you are running on? Most of mine were IBM's. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 07 Nov 2002 10:29:29 -0500, David Rhodu [EMAIL PROTECTED] said: processsor eflags= interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 David yeah, I've been getting the same thing with 4.7 and 5.0 on a few machines David What is the type of machine you are running on? Most of mine were IBM's. Hi, Yes. My machine is an IBM too. It is an IBM Netvista. So, is this problem specific to IBM Machines ? Regards Sid -- A mathematician is a machine for converting coffee into theorems. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code= user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment= base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Try backing out 1.544 of src/sys/i386/i386/machdep.c You'll need to do it as a reversed patch or by hand, as there are some unrelated signal handling things in 1.545 which you'll really need. Drew Michael G. Petry writes: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address= 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer= 0x0:0xfb4 frame pointer= 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags= interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The same is there with 4.7-STABLE The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code= user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? -- Dmitry Valdov mailto:dv;dv.ru CCNP To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002 10:24:23 -0800 (PST), Julian Elischer [EMAIL PROTECTED] said: Julian Are the modules also new? Hi, Yes, the modules are also new. But, I don't think it has anything to do with the modules, cause even if I load the kernel after removing the modules, I get the same crash. Regards Sid -- Anything free is worth what you pay for it. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Hi, Try backing out 1.544 of src/sys/i386/i386/machdep.c You'll need to do it as a reversed patch or by hand, as there are some unrelated signal handling things in 1.545 which you'll really need. Hmmm, I didn't notice that there is a BIOS which requires memory area below 640K even when calling INT 15H/E820. We cannot trust that today's BOISes have INT 12H, so it's difficult to determine base memory size w/o INT 15H/E820. OK, some questions: - What is the size of your base memory (reported by boot loader)? - Does attached patches solve your problem? - Is this problem specific to IBM Netvista? Thanks Index: locore.s === RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v retrieving revision 1.160 diff -u -r1.160 locore.s --- locore.s25 Oct 2002 19:10:56 - 1.160 +++ locore.s8 Nov 2002 04:48:32 - @@ -851,6 +851,11 @@ movl$(KSTACK_PAGES), %ecx fillkptphys($PG_RW) +/* Map base memory */ + movl$0, %eax + movl$0xaPAGE_SHIFT, %ecx + fillkptphys($PG_RW|PG_U) + /* Map ISA hole */ movl$ISA_HOLE_START, %eax movl$ISA_HOLE_LENGTHPAGE_SHIFT, %ecx Drew Michael G. Petry writes: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer= 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process= 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Thus spake Michael G. Petry [EMAIL PROTECTED]: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. I observed the problem on a PPro as well, but it is not specific to PPros. It will occur on any BIOSes (mostly older ones) that use a small amount of memory right before the 640K mark. The problem is that the person who committed the broken change didn't understand that you have to map this region into virtual memory if you're going to call the BIOS in protected mode. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
OK, some questions:
- What is the size of your base memory (reported by boot loader)?
- Does attached patches solve your problem?
- Is this problem specific to IBM Netvista?
Thanks
Index: locore.s
===
RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v
Oops, not this file.
Thanks
Index: machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v
retrieving revision 1.545
diff -u -r1.545 machdep.c
--- machdep.c 25 Oct 2002 19:10:56 - 1.545
+++ machdep.c 8 Nov 2002 04:50:05 -
@@ -1513,6 +1513,7 @@
struct vm86context vmc;
vm_offset_t pa, physmap[PHYSMAP_SIZE];
pt_entry_t *pte;
+ pt_entry_t saved_pte[160];
char *cp;
struct bios_smap *smap;
@@ -1520,6 +1521,14 @@
bzero(physmap, sizeof(physmap));
basemem = 0;
+ for (pa = (4 PAGE_SHIFT); pa ISA_HOLE_START; pa += PAGE_SIZE)
+ pmap_kenter(KERNBASE + pa, pa);
+ pte = (pt_entry_t *)vm86paddr;
+ for (i = 4; i 160; i++) {
+ saved_pte[i] = pte[i];
+ pte[i] |= PG_V | PG_RW | PG_U;
+ }
+
/*
* map page 1 R/W into the kernel page table so we can use it
* as a buffer. The kernel will unmap this page later.
@@ -1629,6 +1638,12 @@
* pmap_mapdev, but since no memory needs to be
* allocated we simply change the mapping.
*/
+ pte = (pt_entry_t *)vm86paddr;
+ for (i = 4; i 160; i++)
+ pte[i] = saved_pte[i];
+ for (pa = (4 PAGE_SHIFT); pa ISA_HOLE_START; pa += PAGE_SIZE)
+ pmap_kremove(KERNBASE + pa);
+
for (pa = trunc_page(basemem * 1024);
pa ISA_HOLE_START; pa += PAGE_SIZE)
pmap_kenter(KERNBASE + pa, pa);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
