RE: SMP problem on E7500 chipset

2002-07-31 Thread igor_dorovskoy 

Looks like you do have hyper threading support on in your BIOS.
Turn it off to disable virtual CPU's in your Xeons

Igor.

-Original Message-
From: Eugene L. Vorokov [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 31, 2002 7:31 AM
To: [EMAIL PROTECTED]
Subject: SMP problem on E7500 chipset


Hi,

I have some strange problem with FreeBSD 4.6 and SMP kernel on a dual CPU
machine. The hardware is:

Motherboard SUPER P4DP6, chipset Intel E7500
2 CPUs: Intel Xeon 2.2Ghz
Adaptec AIC-7899W SCSI controller
2 Intel-82550 Ethernet controllers

When I try to boot an SMP kernel, it tells me that 4 CPUs are found.
Network operation slows down to hell, syslog is full of

Jul 31 14:44:54 superjob /kernel: fxp0: device timeout

Without SMP, everything runs fine.

Syslog output regarding dmesg and kernel config are below.

Regards,
Eugene L. Vorokov


Jul 31 14:40:12 superjob /kernel: FreeBSD 4.6-RELEASE #0: Wed Jul 31 14:35:07 MS
D 2002
Jul 31 14:40:12 superjob /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/maxik
Jul 31 14:40:12 superjob /kernel: Timecounter "i8254"  frequency 1193182 Hz
Jul 31 14:40:12 superjob /kernel: CPU: Pentium 4 (2196.27-MHz 686-class CPU)
Jul 31 14:40:12 superjob /kernel: Origin = "GenuineIntel"  Id = 0xf24  Stepping   
= 4
Jul 31 14:40:12 superjob /kernel: Features=0x3febfbff,ACC>
Jul 31 14:40:12 superjob /kernel: real memory  = 2146959360 (2096640K bytes)
Jul 31 14:40:12 superjob /kernel: avail memory = 2088005632 (2039068K bytes)
Jul 31 14:40:12 superjob /kernel: Programming 24 pins in IOAPIC #0
Jul 31 14:40:12 superjob /kernel: IOAPIC #0 intpin 2 -> irq 0
Jul 31 14:40:12 superjob /kernel: Programming 24 pins in IOAPIC #1
Jul 31 14:40:12 superjob /kernel: Programming 24 pins in IOAPIC #2
Jul 31 14:40:12 superjob /kernel: Programming 24 pins in IOAPIC #3
Jul 31 14:40:12 superjob /kernel: Programming 24 pins in IOAPIC #4
Jul 31 14:40:12 superjob /kernel: FreeBSD/SMP: Multiprocessor motherboard
Jul 31 14:40:12 superjob /kernel: cpu0 (BSP): apic id:  0, version: 0x00050014,
at 0xfee0
Jul 31 14:40:12 superjob /kernel: cpu1 (AP):  apic id:  6, version: 0x00050014,
at 0xfee0
Jul 31 14:40:12 superjob /kernel: cpu2 (AP):  apic id:  1, version: 0x00050014,
at 0xfee0
Jul 31 14:40:12 superjob /kernel: cpu3 (AP):  apic id:  7, version: 0x00050014,
at 0xfee0
Jul 31 14:40:12 superjob /kernel: io0 (APIC): apic id:  2, version: 0x00178020,
at 0xfec0
Jul 31 14:40:12 superjob /kernel: io1 (APIC): apic id:  3, version: 0x00178020,
at 0xfec8
Jul 31 14:40:12 superjob /kernel: io2 (APIC): apic id:  4, version: 0x00178020,
at 0xfec80400
Jul 31 14:40:12 superjob /kernel: io3 (APIC): apic id:  5, version: 0x00178020,
at 0xfec81000
Jul 31 14:40:12 superjob /kernel: io4 (APIC): apic id:  8, version: 0x00178020,
at 0xfec81400
Jul 31 14:40:12 superjob /kernel: Preloaded elf kernel "kernel" at 0xc02f.
ul 31 14:40:12 superjob /kernel: md0: Malloc disk
Jul 31 14:40:12 superjob /kernel: Using $PIR table, 28 entries at 0xc00fde00
Jul 31 14:40:12 superjob /kernel: npx0:  on motherboard
Jul 31 14:40:12 superjob /kernel: npx0: INT 16 interface
Jul 31 14:40:12 superjob /kernel: pcib0:  on motherboard
Jul 31 14:40:12 superjob /kernel: IOAPIC #0 intpin 16 -> irq 2
Jul 31 14:40:12 superjob /kernel: IOAPIC #0 intpin 19 -> irq 5
Jul 31 14:40:12 superjob /kernel: IOAPIC #0 intpin 18 -> irq 10
Jul 31 14:40:12 superjob /kernel: pci0:  on pcib0
Jul 31 14:40:12 superjob /kernel: pci0:  (vendor=0x8086, dev=0x254
1) at 0.1
Jul 31 14:40:12 superjob /kernel: pcib1:  at device 2.0 on pci0
Jul 31 14:40:12 superjob /kernel: pci1:  on pcib1
Jul 31 14:40:12 superjob /kernel: pci1:  (vendor=0x8086, dev=0x146
1) at 28.0
Jul 31 14:40:12 superjob /kernel: pcib2:  at device 29.0 on pci1
Jul 31 14:40:12 superjob /kernel: IOAPIC #2 intpin 4 -> irq 11
Jul 31 14:40:12 superjob /kernel: pci2:  on pcib2
Jul 31 14:40:12 superjob /kernel: pcib3:  at device 2.0 on pci2
Jul 31 14:40:12 superjob /kernel: pci3:  on pcib3
ul 31 14:40:12 superjob /kernel: mly0:  mem 0xfe20-0x
fe201fff irq 11 at device 2.1 on pci2
Jul 31 14:40:12 superjob /kernel: mly0: AcceleRAID 170  , 1 channel, firmware 6.
00-7-00 (20001214), 128MB RAM
Jul 31 14:40:12 superjob /kernel: pci1:  (vendor=0x8086, dev=0x146
1) at 30.0   
Jul 31 14:40:12 superjob /kernel: pcib4:  at device 31.0 on pci1
Jul 31 14:40:12 superjob /kernel: pci4:  on pcib4
Jul 31 14:40:12 superjob /kernel: pcib5:  at device 3.0 on pci0
Jul 31 14:40:12 superjob /kernel: pci5:  on pcib5
Jul 31 14:40:12 superjob /kernel: pci5:  (vendor=0x8086, dev=0x146
1) at 28.0   
Jul 31 14:40:12 superjob /kernel: pcib6:  at device 29.0 on pci5
Jul 31 14:40:12 superjob /kernel: pci6:  on pcib6
Jul 31 14:40:12 superjob /kernel: pci5:  (vendor=0x8086, dev=0x146
1) at 30.0
Jul 31 14:40:12 superjob /kernel: pcib7:  at device 31.0 on pci5
Jul 31 14:40:12 superjob /kernel: pci7:  on pcib7
Jul 31 14:40:12 superjob /kernel: uhci0:  port 0x1400-0x141f irq 2 at device 29.0 on pci0
Jul 31 14:40:12 superjob /ke

FreeBSD 4.6 CDROM installation problem

2002-07-26 Thread igor_dorovskoy 

Please add my CD-ROM drive into 4.6R errata.
This is an NEC CDR-3000A in my old Dell Dimension XPS.
BIOS and dmesg shows drive as "NEC CD-ROM DRIVE:28D"

The workaround works fine, thank you very much.

Regards,
Igor

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: tip problem

2002-07-15 Thread igor_dorovskoy 

That's normal.

Seems yours keystrokes tip successfully delivered to com2 port but no one can
answer back, because com2 is not connected to any other equipment (bwy, I bet
you've added com2 as an alias to real com device in your /etc/remote, right?).

It that case it looks like your system halted (or dead), but it's not true.
If you are working from console, try  or  etc
to switch to next virtual terminal and check/kill tip as an task in task list
or use Terry's advise, - hit ~. to exit from tip (rtfm:).

Regards,
Igor.

-Original Message-
From: Dmitry A. Bondareff [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 15, 2002 7:30 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: tip problem


So.

When I connect with tip to port on which modem connected - server do not
halt.
But on empty port - HALT!

--
#tip -v com2
connected

-
and that's all, no verify messages.

Dmitry.

- Original Message -
From: "Philip Reynolds" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 15, 2002 4:05 PM
Subject: Re: tip problem


> "Dmitry A. Bondareff" <[EMAIL PROTECTED]> 57 lines of wisdom included:
> > Hello, hackers!
> >
> > I have servers with FreeBSD 4.6-RELEASE-p2.
> >
> > And only for one of them I have problem with tip command.
> >
> > # tip com1
> > after this command server halting and only "reset" button may help.
>
> What's connected to com1?
>
> tip -v com1
>
> should generate more information to work with...
>
> Phil.
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: XFree86 4.2.0 & GeForce4 440 Go in Dell Latitude C840

2002-06-03 Thread igor_dorovskoy 

Thank you very much Steve!  I'll try to pick up their cvs changes right now.

Igor.

On Sun, 2 Jun 2002, Matthew N. Dodd wrote:
> On Fri, 31 May 2002 [EMAIL PROTECTED] wrote:
> > Sorry for X off topic...
> >
> > Is anybody here got that combination running?



> > Thanks in advance for any possible help,
> 
> If the 'nv' driver won't deal with it you're out of luck until NVIDIA does
> something about FreeBSD support.
> 

I think the latest (perhaps development) version of XFree86 4.2 has
support for the GeForce 4 (but the FreeBSD port is not yet incorporating
the necessary patches).  I'm sure it was in their changelogs.  I'll have a
look for you .  Yep, it seems to be in number 23 the changelog @
http://www.xfree86.org/cvs/changes.html although the nv driver page
doesn't reflect this at the moment.  You might need to use cvs and check
out the latest code (http://www.xfree86.org/cvs/) or wait until the next
time the port is updated and should have support for your card. 

Steve


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

XFree86 4.2.0 & GeForce4 440 Go in Dell Latitude C840

2002-05-31 Thread igor_dorovskoy 

Sorry for X off topic...

Is anybody here got that combination running?

I've seen that Linux world did that with Nvidia's help.
How to port their solution into freebsd 4.5 box?

Thanks in advance for any possible help,
Igor
ua3qrz

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: A time resolution problem

2002-05-03 Thread igor_dorovskoy 

That's right, agree 100%. I hadn't crash, but this fine granularity hard 
to realize while other parts of system taking apart unpredictably.
More to fix than to use...

Igor,
ua3qrz
-Original Message-
From: Thierry Herbelot [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 5:18 PM
To: Paolo Di Francesco
Cc: [EMAIL PROTECTED]
Subject: Re: A time resolution problem


Paolo Di Francesco wrote:
> 
[SNIP]
> 1 msec. (recompiled the kernel with HZ=10)
> 

in my experience, compiling a kernel with HZ greater than 10.000 (ten
thousand) is uselesss (I even had crash with greater HZ)

TfH

[SNIP]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message