Re: ATAng no good for me
Is atapicam a kernel config option? I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi cdrw locks my system and then reboots immediately after a burning program, (i've tried several) initializes the drive. It worked several weeks ago just fine. Any suggestions would be greatly appreciated. Thanks in advance. David R. Colyer On Saturday 20 September 2003 01:55 am, Soren Schmidt wrote: > It seems Daniel Eischen wrote: > > On a kernel built just a few hours ago, it hangs on boot > > right after: > > > > acd0: CDROM at ata0-master PIO4 > > Get atapicam out and see if that helps.. > > -Søren > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- > ActivatorMail(tm) ver.00811031 Scanned for all viruses by > www.activatormail.com intelligent anti-virus anti-spam service ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng related panic
Sir, I noticed in your dmesg that you have hyperthreading support on a 3 ghz p4 like mine. Could you email me and/or post your kernel config file and/or whatever else you did to get this to compile and work. Please dave On Monday 25 August 2003 01:06 am, Shin-ichi Yoshimoto wrote: > Subject: Re: ATAng related panic, > > On Mon, 25 Aug 2003 08:59:44 +0200 (CEST), Soren Schmidt wrote: > > OK, could you mail me your dmesg please ? > > OK, following: > > /boot/kernel/acpi.ko text=0x393bc data=0x170c+0xec0 > syms=[0x4+0x5b90+0x4+0x79ee] Copyright (c) 1992-2003 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.1-CURRENT #49: Mon Aug 25 08:42:22 JST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DAEMON > Preloaded elf kernel "/boot/kernel/kernel" at 0xc051b000. > Preloaded elf module "/boot/kernel/linux.ko" at 0xc051b244. > Preloaded elf module "/boot/kernel/ipfw.ko" at 0xc051b2f0. > Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc051b39c. > Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc051b448. > Preloaded elf module "/boot/kernel/radeon.ko" at 0xc051b4f4. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc051b5a0. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.52-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 1072889856 (1023 MB) > avail memory = 1036828672 (988 MB) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 > cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 > io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 12 entries at 0xc00f3310 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > IOAPIC #0 intpin 16 -> irq 2 > IOAPIC #0 intpin 19 -> irq 16 > IOAPIC #0 intpin 18 -> irq 17 > IOAPIC #0 intpin 23 -> irq 18 > IOAPIC #0 intpin 17 -> irq 19 > agp0: mem 0xf800-0xfbff at device > 0.0 on pci0 pcib1: at device 1.0 on pci0 > pci1: on pcib1 > drm0: port 0xa800-0xa8ff mem > 0xff7f-0xff7f,0xf000-0xf3ff irq 2 at device 0.0 on pci1 > info: [drm] AGP at 0xf800 64MB > info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 > pci1: at device 0.1 (no driver attached) > pcib2: at device 3.0 on pci0 > pci2: on pcib2 > em0: port > 0xbc00-0xbc1f mem 0xff8e-0xff8f irq 17 at device 1.0 on pci2 em0: > Speed:N/A Duplex:N/A > uhci0: port 0xcc00-0xcc1f irq 2 > at device 29.0 on pci0 usb0: on > uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq > 16 at device 29.1 on pci0 usb1: > on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xd400-0xd41f irq > 17 at device 29.2 on pci0 usb2: > on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > uhci3: port 0xd800-0xd81f irq 2 > at device 29.3 on pci0 usb3: on > uhci3 > usb3: USB revision 1.0 > uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub3: 2 ports with 2 removable, self powered > ehci0: mem 0xffaffc00-0xffaf irq 18 > at device 29.7 on pci0 ehci_pci_attach: companion usb0 > ehci_pci_attach: companion usb1 > ehci_pci_attach: companion usb2 > ehci_pci_attach: companion usb3 > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: (0x8086) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub4: 8 ports with 8 removable, self powered > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > fwohci0: mem 0xff9ff000-0xff9f irq 19 at device 7.0 > on pci3 fwohci0: OHCI version 1.0 (ROM=0) > fwohci0: No. of Isochronous channel is 8. > fwohci0: EUI64 00:07:e9:00:00:70:f9:c4 > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > sbp0: on firewire0 > if_fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:07:e9:70:f9:c4 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode >
Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...
No doubt this has been answered before, but I have an asus p4pe with a 3.06 p4. Naturally, it is enabled in the bios. To enable hyperthreading do I need to recompile my kernel with smp support, and if so...does this apply to freebsd 5.1 release as well? (my friend wants to know). Additionally does changing the machdep.cpu_idle_hlt to zero make it faster? Thanks in advance. David R. Colyer On Wednesday 13 August 2003 10:52 am, John Baldwin wrote: > On 13-Aug-2003 Dr. Richard E. Hawkins wrote: > > On Wed, Aug 13, 2003 at 11:35:14AM -0400, John Baldwin wrote: > >> On 13-Aug-2003 Dr. Richard E. Hawkins wrote: > >> > On Tue, Aug 12, 2003 at 08:33:57PM -0500, Cagle, John (ISS-Houston) wrote: > >> >> I think the valid settings are only 0 or 1, with the default being 1 > >> >> which will disable all logical CPUs. If you want to enable the extra > >> >> logical CPUS, then set it to 0 (zero). They will come online > >> >> immediately. > >> > > >> > That can't be right. I've never done anything to configure the > >> > logical cpus on mine; they just showed up unexpectedly when i switched > >> > from stable to current. Now I have: > >> > > >> > slytherin ttyp1:hawk>sysctl -a | grep cpu > >> > kern.threads.virtual_cpu: 4 > >> > kern.ccpu: 1948 > >> > kern.smp.cpus: 4 > >> > hw.ncpu: 4 > >> > machdep.cpu_idle_hlt: 1 > >> > machdep.hlt_cpus: 10 > >> > machdep.hlt_logical_cpus: 1 > >> > machdep.logical_cpus_mask: 10 > >> > > >> > It launches four logical cpus all on it's own. It did panic during > >> > shutdown yesterday; If I read the messages right as it flashed by, it > >> > was because cpu#2 got the shutdown order. > >> > >> Your logical CPU's aren't doing anything though, even though they are > >> started up. John's explanation is correct. > > > > I've also got the report in dmesg, > > > > SMP: AP CPU #1 Launched! > > SMP: AP CPU #2 Launched! > > SMP: AP CPU #3 Launched! > > > > > > Doesn't this mean that they *are* active? > > No, it means the kernel has started them up. CPU's whose bits are set > in machdep.hlt_cpus don't execute any user tasks. Instead, they just > sit in a loop executing the 'hlt' instruction doing nothing but servicing > interrupts. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...
No doubt this has been answered before, but I have an asus p4pe with a 3.06 p4. Naturally, it is enabled in the bios. To enable hyperthreading do I need to recompile my kernel with smp support, and if so...does this apply to freebsd 5.1 release as well? (my friend wants to know). Additionally does changing the machdep.cpu_idle_hlt to zero make it faster? Thanks in advance. David R. Colyer On Wednesday 13 August 2003 10:52 am, John Baldwin wrote: > On 13-Aug-2003 Dr. Richard E. Hawkins wrote: > > On Wed, Aug 13, 2003 at 11:35:14AM -0400, John Baldwin wrote: > >> On 13-Aug-2003 Dr. Richard E. Hawkins wrote: > >> > On Tue, Aug 12, 2003 at 08:33:57PM -0500, Cagle, John (ISS-Houston) wrote: > >> >> I think the valid settings are only 0 or 1, with the default being 1 > >> >> which will disable all logical CPUs. If you want to enable the extra > >> >> logical CPUS, then set it to 0 (zero). They will come online > >> >> immediately. > >> > > >> > That can't be right. I've never done anything to configure the > >> > logical cpus on mine; they just showed up unexpectedly when i switched > >> > from stable to current. Now I have: > >> > > >> > slytherin ttyp1:hawk>sysctl -a | grep cpu > >> > kern.threads.virtual_cpu: 4 > >> > kern.ccpu: 1948 > >> > kern.smp.cpus: 4 > >> > hw.ncpu: 4 > >> > machdep.cpu_idle_hlt: 1 > >> > machdep.hlt_cpus: 10 > >> > machdep.hlt_logical_cpus: 1 > >> > machdep.logical_cpus_mask: 10 > >> > > >> > It launches four logical cpus all on it's own. It did panic during > >> > shutdown yesterday; If I read the messages right as it flashed by, it > >> > was because cpu#2 got the shutdown order. > >> > >> Your logical CPU's aren't doing anything though, even though they are > >> started up. John's explanation is correct. > > > > I've also got the report in dmesg, > > > > SMP: AP CPU #1 Launched! > > SMP: AP CPU #2 Launched! > > SMP: AP CPU #3 Launched! > > > > > > Doesn't this mean that they *are* active? > > No, it means the kernel has started them up. CPU's whose bits are set > in machdep.hlt_cpus don't execute any user tasks. Instead, they just > sit in a loop executing the 'hlt' instruction doing nothing but servicing > interrupts. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
