Re: Problem booting FBSD 5.4-stable..
On 2 Oct 2005, at 05:12, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 20:09: On 1 Oct 2005, at 14:29, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 17:45: On 1 Oct 2005, at 14:01, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 17:04: Specs: Amd Thunderbird 800 Abit KT7-raid (VIA KT133) 256 MB 30 GB IDE Cdrom Floppy Problem: The computer just prints three rows... 'Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX' ...and then reboots. Did you try disabling fancy options like BIOS Shadowing, Power Options, etc? Are you running the latest release of BIOS from your mo'bo' manufacturer? Is the HDD and the CDROM on the same cable? If yes, then what is the way they are attached? Running the latest BIOS version yes. Also running Fail safe options with the exception on that I've but the cdrom on first boot device. The cable setup is IDE1 <- HD0 (M) <- Cdrom (S). So yes, they're on the same cable with manual M/S-setup. // Sebastian Holmqvist Great. FreeBSD, unlike Linux and Windowz is very very fusy about hardware. As per the IDE specs, the master drive should always be at the end of the cable. The middle is occupied by the slave drive, which is not your case. For a start, I would try fixing that. Also it is recommended not to mix drive types on a single bus. Therefore it would be highly recommended to move the optical drive to the secondary bus. Also do not rely on CS. Ecplicitly jumper them as master and slave. Thanks S. Alright. I've tried putting IDE <- CDrom (S) <- HD0 (M) and it didn't work. Then I tried IDE1 <- HD0 (M) and IDE2 <- CDrom (M) and that didn't work EITHER. This is feeling ridiculous. I'm trying the boot diskettes to test my luck. // Sebastian Holmqvist Sebastian, Don't worry, the boot diskettes wont work either. The basic problem is some kind of conflict with some existing hardware in the box. I can see an ABit RAID inside the box. What is it doing there and what kind of configuration is it following? Also could you point us to some sites describing your hardware? Could you please tell us about all the devices which are present in your system? Include the onboard devices as well. Thanks S. -- -+- | Subhro Sankha Kar \ / |GSM: +919831064613 -- Fax: +919831832913 \./ |MSN:[EMAIL PROTECTED] -- Yahoo: subhro82 (0Y0) |ICQ: 203567534 -- AIM: bsdboy1982 --ooO--(_)--Ooo--+- The abit raid unit is disabled at the moment. I've got a Promise SATAII150 TX4 controller card with two harddrives connected to it currently. Otherwise, it's standard. You gave me some ideas now, I'm gonna try without the Promise-card and if that works, on another PCI-port. Wish me good luck :) // Sebastian Holmqvist ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting FBSD 5.4-stable..
On 2 Oct 2005, at 13:07, Sebastian Holmqvist wrote: On 2 Oct 2005, at 05:12, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 20:09: On 1 Oct 2005, at 14:29, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 17:45: On 1 Oct 2005, at 14:01, Subhro wrote: Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 17:04: Specs: Amd Thunderbird 800 Abit KT7-raid (VIA KT133) 256 MB 30 GB IDE Cdrom Floppy Problem: The computer just prints three rows... 'Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX' ...and then reboots. Did you try disabling fancy options like BIOS Shadowing, Power Options, etc? Are you running the latest release of BIOS from your mo'bo' manufacturer? Is the HDD and the CDROM on the same cable? If yes, then what is the way they are attached? Running the latest BIOS version yes. Also running Fail safe options with the exception on that I've but the cdrom on first boot device. The cable setup is IDE1 <- HD0 (M) <- Cdrom (S). So yes, they're on the same cable with manual M/S-setup. // Sebastian Holmqvist Great. FreeBSD, unlike Linux and Windowz is very very fusy about hardware. As per the IDE specs, the master drive should always be at the end of the cable. The middle is occupied by the slave drive, which is not your case. For a start, I would try fixing that. Also it is recommended not to mix drive types on a single bus. Therefore it would be highly recommended to move the optical drive to the secondary bus. Also do not rely on CS. Ecplicitly jumper them as master and slave. Thanks S. Alright. I've tried putting IDE <- CDrom (S) <- HD0 (M) and it didn't work. Then I tried IDE1 <- HD0 (M) and IDE2 <- CDrom (M) and that didn't work EITHER. This is feeling ridiculous. I'm trying the boot diskettes to test my luck. // Sebastian Holmqvist Sebastian, Don't worry, the boot diskettes wont work either. The basic problem is some kind of conflict with some existing hardware in the box. I can see an ABit RAID inside the box. What is it doing there and what kind of configuration is it following? Also could you point us to some sites describing your hardware? Could you please tell us about all the devices which are present in your system? Include the onboard devices as well. Thanks S. -- -+- | Subhro Sankha Kar \ / |GSM: +919831064613 -- Fax: +919831832913 \./ |MSN:[EMAIL PROTECTED] -- Yahoo: subhro82 (0Y0) |ICQ: 203567534 -- AIM: bsdboy1982 --ooO--(_)--Ooo--+- The abit raid unit is disabled at the moment. I've got a Promise SATAII150 TX4 controller card with two harddrives connected to it currently. Otherwise, it's standard. You gave me some ideas now, I'm gonna try without the Promise-card and if that works, on another PCI-port. Wish me good luck :) // Sebastian Holmqvist Ok. The problem was solved by disconnecting the harddrives out of the controller card. I think it might be that they are FAT32. Almost everything is installed now. Sweet! Thanks for all the help! // Sebastian Holmqvist ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB keyboard problems with Freebsd 5.4 Release
Hello! We are having problems bootig the server runing FreeBSD 5.4 RELEASE (GENERIC kernell) via Belkin Components KVM console. The console is emuating a USB keyboard and the keyboard works fine while in BIOS, up until the boot options screen - regardless of wearher the option "Boot with USB keyboard" or "Normal bot" is selected, the keybard stops responding after the system loads. The usbd demon is loaded at startup, and keyboard & mouse are detected. .. ukbd0: Belkin Components KVM USB Keyboard/Mouse, rev 1.00/2.01, addr 2, iclass 3/1 kbd1 at ukbd0 ums0: Belkin Components KVM USB Keyboard/Mouse, rev 1.00/2.01, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. .. Interesting thing is that the console worked fine ubder FreeBSD 5.2 Release. Thank you for you help! Jurij Kovacic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Stability problems vith FreeBSD 5.2.1-RELEASE-p14
Hello! We are running FreeBSD 5.2.1-RELEASE-p14 with SMP kernell on one of our servers and are experiencing stability problems; the server has the tendency to reboot itself for no apparent reason at least once per month. Dmesg: Copyright (c) 1992-2004 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 5.2.1-RELEASE-p14 #0: Tue May 10 18:06:08 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM_521 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a3f000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a3f294. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 246 (1993.80-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe050 real memory = 4227268608 (4031 MB) avail memory = 4109025280 (3918 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00fdf00 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 unknown: I/O range not supported unknown: I/O range not supported acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pcib0: could not get PCI interrupt routing table for \\_SB_.PCI0 - AE_NOT_FOUND pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfc10-0xfc100fff irq 19 at device 0.0 on pci1 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ukbd0: Belkin Components KVM USB Keyboard/Mouse, rev 1.00/2.01, addr 2, iclass 3/1 kbd1 at ukbd0 ums0: Belkin Components KVM USB Keyboard/Mouse, rev 1.00/2.01, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. ohci1: mem 0xfc101000-0xfc101fff irq 19 at device 0.1 on pci1 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfe00-0xfe00,0xfe01-0xfe01 irq 24 at device 1.0 on pci2 bge0: Ethernet address: 00:0d:60:14:86:16 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: mem 0xfe02-0xfe02,0xfe03-0xfe03 irq 25 at device 1.1 on pci2 bge1: Ethernet address: 00:0d:60:14:86:17 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 3.0 on pci3 pci4: on pcib4 pcib4: slot 8 INTA is routed to irq 28 ips0: mem 0xfe10-0xfe100fff irq 28 at device 8.0 on pci4 pci0: at device 11.1 (no driver attached) sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A orm0: at iomem 0xc9800-0xcafff,0xc8000-0xc97ff on isa0 pmtimer0 on isa0 fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acd0: CDROM at ata1-master PIO4 ips0: adapter type: ServeRAID 6M (marco) ips0: logical drives: 1 ips0: Logical Drive 0: RAID1 sectors: 143372288, state OK ipsd0: on ips0 GEOM: create disk ipsd0 dp=0xc7418790 ipsd0: Logical Drive (70006MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a bge1: gigabit link up netsmb_dev: loaded Memtest reveales no problems with RAM. One sure way to crash the server is to delete a large number of files - /usr/ports for example. The panic message is ussually somewhere along these lines: panic: kmem_malloc(4096) kmem map too small: 48496066400 total allocated cpuid =0 boot() called on cpu#0 ... Has anyone experienced similar problems? Would upgrading to FreeBSD 5.4 fix the prob
Re: Stability problems vith FreeBSD 5.2.1-RELEASE-p14
On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote: > Hello! > > We are running FreeBSD 5.2.1-RELEASE-p14 with SMP kernell on one of our > servers and are experiencing stability problems; the server has the > tendency to reboot itself for no apparent reason at least once per month. As you may know, 5.2.1 was an "early adopter release" not intended for production use. It's not surprising you have encountered one of the bugs in it. Update to a supported, production-quality release like 5.4. Kris pgpAZxAqXUSmn.pgp Description: PGP signature
Re: Stability problems vith FreeBSD 5.2.1-RELEASE-p14
On 10/2/05, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote: > > Hello! > > > > We are running FreeBSD 5.2.1-RELEASE-p14 with SMP kernell on one of our > > servers and are experiencing stability problems; the server has the > > tendency to reboot itself for no apparent reason at least once per month. > > As you may know, 5.2.1 was an "early adopter release" not intended for > production use. It's not surprising you have encountered one of the > bugs in it. Update to a supported, production-quality release like > 5.4. > > Kris Also note that 5.4-RELEASE has a severe crash bug related when you use PAE and 4GB+ RAM (which may be what the OP is running in to, actually) so if you want to be able to use all of your memory without crashes, you'll need to either upgrade to 5-STABLE or apply a small patch (search the mail archive for PAE and pmap.c). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with snd_ich
I've got a K8WE, and up until a few days ago, snd_ich worked just fine under 6.0-BETA3: pcm0: port 0x1800-0x18ff,0x1400-0x14ff mem 0xc8002000-0xc8002fff irq 22 at device 4.0 on pci0 pcm0: [GIANT-LOCKED] pcm0: Then suddenly, anything playing sound started to hang, and no sound would come out. I don't remember doing anything at that point in time -- I came back from work, and it just wasn't working. This message appeared in dmesg: pcm0: ac97 link rate calibration timed out after 1795248 us When it happened, I could unload snd_ich, but not sound. And the problem's been plaguing me ever since: as soon as I load the module, I get the link rate calibration error. I've since updated to BETA5, but am still seeing the problem. Additionally, when I tried to kldunload sound earlier today, my kernel panicked: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa0 fault code = supervisor read, page not present instruction pointer = 0x8:0x8025155b stack pointer = 0x10:0xa7bf79d0 frame pointer = 0x10:0x0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 53790 (kldunload) trap number = 12 panic: page fault Uptime: 9m45s I didn't have a kernel with debugging symbols handy, unfortunately, but I've got another one built and ready to go, and I'll see if I can reproduce the panic later today. - Damian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
