Linux-Development-Sys Digest #405, Volume #6 Tue, 16 Feb 99 21:14:18 EST
Contents:
getting inode information (Marx Rajangam)
2.2.1: strange SMP (dual celeron) startup msgs (BL)
Re: "No Available PTYS" with 2.2.0 (H. Peter Anvin)
Re: Ncurses with g++ (Bryan Hackney)
Re: "No Available PTYS" with 2.2.0 (Chun-Chung Chen)
Errors with 2.2.1 (Brian J King)
Re: how to create new ptys and ttys? (Robert Hamilton)
Re: kernel 2.2.1 spurious APIC interrupt, ayiee, should never happen (David Fox)
Re: ATAPI ZIP drive problem.... (Joe Radkowski)
Re: ATAPI ZIP drive problem.... (Julian Robert Yon)
Re: 2.2.1: strange SMP (dual celeron) startup msgs (BL)
----------------------------------------------------------------------------
From: Marx Rajangam <[EMAIL PROTECTED]>
Subject: getting inode information
Date: 16 Feb 1999 05:09:46 GMT
Hi,
I am trying to get the inode number given a file name. I need to
implement a system call the finds it.
I looked into the system calls like open, stat and they are using a
kernel function namei() for getting the inode for a given file name.
I wrote a system call that looks like,
asmlinkage unsigned long assoc(void)
{
struct inode *in;
unsigned long i;
int j;
j = namei("/root/junk", &in);
if (j >= 0){
i = in->i_ino;
return i;
}
else{
return -1000;
}
}
I dont know why my system call is not working when I almost
replicated the code from functions like stat and open.. Is there any
special condition that I need to take care of?
I would greatly appreciate any help that you can do..
Thanks a lot for your time and effort.
--
Marx Rajangam
Fisher 227, CS Dept,
Michigan Tech. Univ.
------------------------------
From: BL <[EMAIL PROTECTED]>
Subject: 2.2.1: strange SMP (dual celeron) startup msgs
Date: 16 Feb 1999 05:41:12 GMT
Reply-To: no.spambots.please
is this exerpt from my startup log normal for SMP? (excerpt included below).
(kernel is 2.2.1 built for SMP)
the sytem is a bit overclocked (75mhz bus instead of 66). 83 wasn't stable and
100 didn't boot long ;-) but what's that about "not connected"? did I botch
the hole-drilling and green-wiring? ;-)
motherboard is Asus p2bd (assumed very compatible and stable - every asus has
been good to me).
both cpu's were bought OEM pack at the same time (300a chips). interesting that
stepping shows "00" here; but /proc/cpu shows:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 6
model name : Celeron (Mendocino)
stepping : unknown <<< *** really? ***
cpu MHz : 337.506524
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 mmx osfxsr
bogomips : 336.69
startup log info:
$ cat /var/log/messages
[...]
Feb 15 20:15:19 linux95 syslogd 1.3-3: restart.
Feb 15 20:15:19 linux95 kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb 15 20:15:19 linux95 kernel: Loaded 6202 symbols from /usr/src/linux/System.map.
Feb 15 20:15:19 linux95 kernel: Symbols match kernel version 2.2.1.
Feb 15 20:15:19 linux95 kernel: Error seeking in /dev/kmem
Feb 15 20:15:19 linux95 kernel: Error adding kernel module table entry.
Feb 15 20:15:19 linux95 kernel: Linux version 2.2.1 ([EMAIL PROTECTED]) (gcc
version 2.7.2.3) #3 SMP Mon Feb 15 20:00:16 PST 1999
Feb 15 20:15:19 linux95 kernel: Intel MultiProcessor Specification v1.1
Feb 15 20:15:19 linux95 kernel: Virtual Wire compatibility mode.
Feb 15 20:15:19 linux95 kernel: OEM ID: OEM00000 Product ID: PROD00000000 APIC at:
0xFEE00000
Feb 15 20:15:19 linux95 kernel: Processor #1 Pentium(tm) Pro APIC version 17
Feb 15 20:15:19 linux95 kernel: Processor #0 Pentium(tm) Pro APIC version 17
Feb 15 20:15:19 linux95 kernel: I/O APIC #2 Version 17 at 0xFEC00000.
Feb 15 20:15:19 linux95 kernel: Processors: 2
Feb 15 20:15:19 linux95 kernel: mapped APIC to ffffe000 (fee00000)
Feb 15 20:15:19 linux95 kernel: mapped IOAPIC to ffffd000 (fec00000)
Feb 15 20:15:19 linux95 kernel: Detected 337506524 Hz processor.
Feb 15 20:15:19 linux95 kernel: Console: colour VGA+ 80x25
Feb 15 20:15:19 linux95 kernel: Calibrating delay loop... 336.69 BogoMIPS
Feb 15 20:15:19 linux95 kernel: Memory: 128168k/131008k available (856k kernel code,
420k reserved, 151 6k data, 48k init)
Feb 15 20:15:19 linux95 kernel: Checking 386/387 coupling... OK, FPU using exception
16 error reporting.
Feb 15 20:15:19 linux95 kernel: Checking 'hlt' instruction... OK.
Feb 15 20:15:19 linux95 kernel: POSIX conformance testing by UNIFIX
Feb 15 20:15:19 linux95 kernel: mtrr: v1.26 (19981001) Richard Gooch
([EMAIL PROTECTED])
Feb 15 20:15:19 linux95 kernel: per-CPU timeslice cutoff: 25.03 usecs.
Feb 15 20:15:19 linux95 kernel: CPU1: Intel Celeron (Mendocino) stepping 00
Feb 15 20:15:19 linux95 kernel: calibrating APIC timer ...
Feb 15 20:15:19 linux95 kernel: ..... CPU clock speed is 337.5143 MHz.
Feb 15 20:15:19 linux95 kernel: ..... system bus clock speed is 75.0030 MHz.
Feb 15 20:15:19 linux95 kernel: Booting processor 0 eip 2000
Feb 15 20:15:19 linux95 kernel: Calibrating delay loop... 336.69 BogoMIPS
Feb 15 20:15:19 linux95 kernel: OK.
Feb 15 20:15:19 linux95 kernel: CPU0: Intel Celeron (Mendocino) stepping 00
Feb 15 20:15:19 linux95 kernel: Total of 2 processors activated (673.38 BogoMIPS).
Feb 15 20:15:19 linux95 kernel: enabling symmetric IO mode... ...done.
Feb 15 20:15:19 linux95 kernel: ENABLING IO-APIC IRQs
Feb 15 20:15:19 linux95 kernel: init IO_APIC IRQs
v*** what does this line mean? **v
Feb 15 20:15:19 linux95 kernel: IO-APIC pin 0, 3, 10, 11, 13, 15, 20, 21, 22, 23 not
connected.
Feb 15 20:15:19 linux95 kernel: number of MP IRQ sources: 15.
Feb 15 20:15:19 linux95 kernel: number of IO-APIC registers: 24.
Feb 15 20:15:19 linux95 kernel: testing the IO APIC.......................
Feb 15 20:15:19 linux95 kernel: .... register #00: 02000000
Feb 15 20:15:19 linux95 kernel: ....... : physical APIC id: 02
Feb 15 20:15:19 linux95 kernel: .... register #01: 00170011
Feb 15 20:15:19 linux95 kernel: ....... : max redirection entries: 0017
Feb 15 20:15:19 linux95 kernel: ....... : IO APIC version: 0011
Feb 15 20:15:19 linux95 kernel: .... register #02: 00000000
Feb 15 20:15:19 linux95 kernel: ....... : arbitration: 00
v** what's this table about? **v
Feb 15 20:15:19 linux95 kernel: .... IRQ redirection table:
Feb 15 20:15:19 linux95 kernel: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
Feb 15 20:15:19 linux95 kernel: 00 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 01 000 00 0 0 0 0 0 1 1 59
Feb 15 20:15:19 linux95 kernel: 02 0FF 0F 0 0 0 0 0 1 1 51
Feb 15 20:15:19 linux95 kernel: 03 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 04 000 00 0 0 0 0 0 1 1 61
Feb 15 20:15:19 linux95 kernel: 05 000 00 0 0 0 0 0 1 1 69
Feb 15 20:15:19 linux95 kernel: 06 000 00 0 0 0 0 0 1 1 71
Feb 15 20:15:19 linux95 kernel: 07 000 00 0 0 0 0 0 1 1 79
Feb 15 20:15:19 linux95 kernel: 08 000 00 0 0 0 0 0 1 1 81
Feb 15 20:15:19 linux95 kernel: 09 000 00 0 0 0 0 0 1 1 89
Feb 15 20:15:19 linux95 kernel: 0a 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 0b 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 0c 000 00 0 0 0 0 0 1 1 91
Feb 15 20:15:19 linux95 kernel: 0d 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 0e 000 00 0 0 0 0 0 1 1 99
Feb 15 20:15:19 linux95 kernel: 0f 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 10 0FF 0F 1 1 0 1 0 1 1 A1
Feb 15 20:15:19 linux95 kernel: 11 0FF 0F 1 1 0 1 0 1 1 A9
Feb 15 20:15:19 linux95 kernel: 12 0FF 0F 1 1 0 1 0 1 1 B1
Feb 15 20:15:19 linux95 kernel: 13 0FF 0F 1 1 0 1 0 1 1 B9
Feb 15 20:15:19 linux95 kernel: 14 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 15 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 16 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: 17 000 00 1 0 0 0 0 0 0 00
Feb 15 20:15:19 linux95 kernel: .................................... done.
v** should I be concerned with these msgs? **v
Feb 15 20:15:19 linux95 kernel: mtrr: your CPUs had inconsistent fixed MTRR settings
Feb 15 20:15:19 linux95 kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Feb 15 20:15:19 linux95 kernel: mtrr: probably your BIOS does not setup all CPUs
--
AntiSpam: For email, change all 'zero' chars to letter 'o' chars.
------------------------------
From: [EMAIL PROTECTED] (H. Peter Anvin)
Subject: Re: "No Available PTYS" with 2.2.0
Date: 16 Feb 1999 05:51:13 GMT
Reply-To: [EMAIL PROTECTED] (H. Peter Anvin)
Followup to: <[EMAIL PROTECTED]>
By author: Chun-Chung Chen <[EMAIL PROTECTED]>
In newsgroup: comp.os.linux.development.system
>
> On 16 Feb 1999, H. Peter Anvin wrote:
>
> > Most likely, the fellow has /dev/pmtx but not /dev/pts. Delete
> > /dev/ptmx; some early versions of glibc tried to use /dev/ptmx with
> > BSD ptys; this never worked right, and newer versions of glibc
> > fortunately don't even try.
>
> The newest version of glibc (2.1) does support ptmx/pts. It works
> well with 2.2 kernels. It's just that you'll need to recompile
> almost everything. And, till now, i still couldn't get "xterm" to
> use the new Unix98 ptys. It insists on using the old style tty/pty.
> However, rxvt works just fine after fooling it with SVR4. Without
> the old [pt]ty my /dev looks a lot cleaner now.
>
> For David, i guess the obsoleted major 4 pty/tty is the problem.
> Recreating the pty[pqrs][0-f] and tty[pqrs][0-f] with new
> major/minor number as described in
>
That's a possibility; but there *were* some glibc versions that had
problems if /dev/ptmx existed because it was trying to do this funny
BSD/Unix98 hybrid (basically, it was trying to emulate Unix98 PTYs
based on BSD ones; there was some early support in the 2.1 series for
that, and it got ripped out.)
-hpa
--
"Linux is a very complete and sophisticated operating system. There
are, and will be, large numbers of applications available for it."
-- Paul Maritz, Group Vice President for Platforms And Applications,
Microsoft Corporation [Reference at: http://www.kernel.org/~hpa/ms.html]
------------------------------
From: Bryan Hackney <[EMAIL PROTECTED]>
Subject: Re: Ncurses with g++
Date: Tue, 16 Feb 1999 05:57:04 +0000
Reply-To: [EMAIL PROTECTED]
And also,
Since my response sounded a little harsh toward the curses APIs,
I did not intend to dis anyone who over the years has helped to
make Unix terminal mode (vi mode) what it is. Terminal mode will
be around for a long time, and it works well.
--
Bryan Hackney / BHC / bhackneyatexpress-news.net
*
------------------------------
From: Chun-Chung Chen <[EMAIL PROTECTED]>
Subject: Re: "No Available PTYS" with 2.2.0
Date: Mon, 15 Feb 1999 20:41:08 -0800
On 16 Feb 1999, H. Peter Anvin wrote:
> Most likely, the fellow has /dev/pmtx but not /dev/pts. Delete
> /dev/ptmx; some early versions of glibc tried to use /dev/ptmx with
> BSD ptys; this never worked right, and newer versions of glibc
> fortunately don't even try.
The newest version of glibc (2.1) does support ptmx/pts. It works
well with 2.2 kernels. It's just that you'll need to recompile
almost everything. And, till now, i still couldn't get "xterm" to
use the new Unix98 ptys. It insists on using the old style tty/pty.
However, rxvt works just fine after fooling it with SVR4. Without
the old [pt]ty my /dev looks a lot cleaner now.
For David, i guess the obsoleted major 4 pty/tty is the problem.
Recreating the pty[pqrs][0-f] and tty[pqrs][0-f] with new
major/minor number as described in
/usr/src/linux/Documentation/devices.txt
might help.
. Chung .
------------------------------
From: [EMAIL PROTECTED] (Brian J King)
Subject: Errors with 2.2.1
Date: 16 Feb 1999 04:08:20 GMT
Since switching to the 2.2.1 kernel I've noticed that now I will
ocassionally get kernel error messages spitting out /dev/tty1, which is my
first console. Shouldn't they just get dumped into /var/log/messages? I
tend to get errors about my EtherExpress ethernet card not having a
carrier. Is there a way to turn this off without hacking the code for the
EtherExpress driver? I really don't care 90% of the time that there is no
carrier, because my card it only actually hooked up to another machine
once in a while. I have also gotten X errors to come out on /dev/tty1, but
found a hack to shut that up. Its just rather annoying when you switch to
the first virtual console and there a bunch of errors sitting there
instead of a clean login prompt.
Any ideas?
Thanks,
Brian King
--
___________________________________________________________________________
Brian King
North Dakota State University
Linux System Administrator
Electrical Engineering Department
------------------------------
From: [EMAIL PROTECTED] (Robert Hamilton)
Subject: Re: how to create new ptys and ttys?
Date: 16 Feb 1999 03:05:20 GMT
Reply-To: [EMAIL PROTECTED]
On Mon, 15 Feb 1999 15:25:45 -0500, Bob Berman <[EMAIL PROTECTED]> wrote:
>According to the documentation with the new 2.2.1 kernel, support for
>major 4 ttyp and ptys is gone. Now you need major 3 tty and major 2 ptys.
>How exactly do I go about creating them? Do I just do a mknod /dev/ptyp0-f
>c 2 or what? Is there a shell script around I could download? Does this mean
>my old kernel 2.0.35 will definitely not work anymore? I don't trust 2.2.1
>yet (especially since I've yet to have a succesful boot!) and would like to
>be able to boot back into 2.0.35 if necessary.
You will need the new ptyp's mostly for X.
Well, this is what I did - (stripped down/modified from a slackware script)
standard disclaimers - test it beforehand, etc .......
To make the old ones again, just see the old MAKEDEV script
-- Robert Hamilton
======================================================================
#! /bin/bash -
tty=" root tty 666"
makedev () { # usage: makedev name [bcu] major minor owner group mode
rm -f $1
mknod $1- $2 $3 $4 &&
chown $5:$6 $1- &&
chmod $7 $1- &&
mv $1- $1
}
for bank in p q r s
do
base=`expr \( pqrs : ".*$bank" - 1 \) \* 16`
for i in 0 1 2 3 4 5 6 7 8 9 a b c d e f
do
j=`expr 0123456789abcdef : ".*$i" - 1`
makedev pty$bank$i c 2 `expr $base + $j` $tty
makedev tty$bank$i c 3 `expr $base + $j` $tty
done
done
exit 0
------------------------------
From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Subject: Re: kernel 2.2.1 spurious APIC interrupt, ayiee, should never happen
Date: 15 Feb 1999 19:31:19 -0800
[EMAIL PROTECTED] (Buffat Marc) writes:
> Hello,
> I have tried to compile the new Linux kernel 2.2.1 on a dual Dell PPRO
> and I got the following kernel message (SMP kernel enable)
> "spurious APIC interrupt, ayiee, should never happen"
> Is it a bug of the PPRO or of the kernel ?
> I was running the kernel 2.1.43 in SMP mode without problem
> Thanks in advance
> Marc BUFFAT
Fixed in the "ac" series of pre-2.2.2 patches.
--
David Fox http://hci.ucsd.edu/dsf xoF divaD
UCSD HCI Lab baL ICH DSCU
------------------------------
From: Joe Radkowski <[EMAIL PROTECTED]>
Subject: Re: ATAPI ZIP drive problem....
Date: Tue, 16 Feb 1999 01:44:46 -0500
Peter J. de Vrijer wrote:
> On Fri, 12 Feb 1999, Gyepi Sam wrote:
> >How are you using fdisk?
> >How are you calling mount?
> >If you have any fstab entries for the drive, please post that.
> >
> >The Iomega zip drives actually show up as the last partition on the drive. I don't
> >know why.
> >In your case, you'd probably find it at
> >
> > /dev/hdd4
> Well that must be because Iomega partitioned them that way. I can see no
> technical reason. In fact you can use fdisk to create an primary partition
> as the first one (/dev/hdd1). And then put a ext2 fs on it with mkfs.
> I tried that once. Works perfectly.
They did this for a very good technical reason. Zips are cross platform -- Mac
or x86. Macs only reconize the 4th partition therefore their disks are setup that way.
Joe
------------------------------
From: Julian Robert Yon <[EMAIL PROTECTED]>
Subject: Re: ATAPI ZIP drive problem....
Date: Tue, 16 Feb 1999 13:40:00 +0000
Carlos Antunes dos Santos wrote:
> The problem is not in the ZIP disks, I've used it with
> other ZIP drives
> (internal scsi) in linux with no problems.
>
> Is it a hardware problem? I don't think so, in
> windows98 it works fine.
I've had (what appears to be) the same problem. A zip disk can work fine
in a ppa zip drive under linux and windows, and in an atapi zip under
win98, but not in an atapi zip under linux - neither on the same (win98)
machine, nor on another, dedicated linux box.
Again, the partition table comes up as junk and the disk is unreadable.
Until I take it back to one of the other set-ups, that is. So I would
say it's not the hardware, and it's not the media. So it's probably the
driver.
It might be relevant that both the ATAPI drives I tried were connected
to PIIX4 interfaces on a 440BX motherboard as well.
Julian
~~~~~~~~~~~~~~~~~~~~
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: BL <[EMAIL PROTECTED]>
Subject: Re: 2.2.1: strange SMP (dual celeron) startup msgs
Date: 16 Feb 1999 15:06:23 GMT
Reply-To: no.spambots.please
Marc Elvery <[EMAIL PROTECTED]> wrote:
: as far as i know, smp is not supported at all with celeron's not under
: win-nt not under linux,
: you should have bought normal pentium-II's
hey man, have you actually READ my posting? get a clue - you CAN modify the
chips so they work. mendocino is mendocino - PERIOD.
check out this link to educate yourself ;-)
http://kikumaru.w-w.ne.jp/pc/celeron/index_e.html
and btw, why would linux say I have 2 cpus if it didn't work? do you think I
typed all this in myself and faked the console log? ;-)
: Marc
: BL wrote in message <7ab0do$19u$[EMAIL PROTECTED]>...
: >
: >is this exerpt from my startup log normal for SMP? (excerpt included
: below).
: >(kernel is 2.2.1 built for SMP)
: >
: >the sytem is a bit overclocked (75mhz bus instead of 66). 83 wasn't stable
: and
: >100 didn't boot long ;-) but what's that about "not connected"? did I
: botch
: >the hole-drilling and green-wiring? ;-)
: >
: >motherboard is Asus p2bd (assumed very compatible and stable - every asus
: has
: >been good to me).
: >
: >both cpu's were bought OEM pack at the same time (300a chips). interesting
: that
: >stepping shows "00" here; but /proc/cpu shows:
: >
: >processor : 0
: >vendor_id : GenuineIntel
: >cpu family : 6
: >model : 6
: >model name : Celeron (Mendocino)
: >stepping : unknown <<< *** really? ***
: >cpu MHz : 337.506524
: >cache size : 128 KB
: >fdiv_bug : no
: >hlt_bug : no
: >sep_bug : no
: >f00f_bug : no
: >fpu : yes
: >fpu_exception : yes
: >cpuid level : 2
: >wp : yes
: >flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
: cmov
: >pat pse36 mmx osfxsr
: >bogomips : 336.69
: >
: >
: >
: >startup log info:
: >
: >$ cat /var/log/messages
: >
: >[...]
: >
: >Feb 15 20:15:19 linux95 syslogd 1.3-3: restart.
: >Feb 15 20:15:19 linux95 kernel: klogd 1.3-3, log source = /proc/kmsg
: started.
: >Feb 15 20:15:19 linux95 kernel: Loaded 6202 symbols from
: /usr/src/linux/System.map.
: >Feb 15 20:15:19 linux95 kernel: Symbols match kernel version 2.2.1.
: >Feb 15 20:15:19 linux95 kernel: Error seeking in /dev/kmem
: >Feb 15 20:15:19 linux95 kernel: Error adding kernel module table entry.
: >Feb 15 20:15:19 linux95 kernel: Linux version 2.2.1
: ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #3 SMP Mon Feb 15 20:00:16
: PST 1999
: >Feb 15 20:15:19 linux95 kernel: Intel MultiProcessor Specification v1.1
: >Feb 15 20:15:19 linux95 kernel: Virtual Wire compatibility mode.
: >Feb 15 20:15:19 linux95 kernel: OEM ID: OEM00000 Product ID: PROD00000000
: APIC at: 0xFEE00000
: >Feb 15 20:15:19 linux95 kernel: Processor #1 Pentium(tm) Pro APIC version
: 17
: >Feb 15 20:15:19 linux95 kernel: Processor #0 Pentium(tm) Pro APIC version
: 17
: >Feb 15 20:15:19 linux95 kernel: I/O APIC #2 Version 17 at 0xFEC00000.
: >Feb 15 20:15:19 linux95 kernel: Processors: 2
: >Feb 15 20:15:19 linux95 kernel: mapped APIC to ffffe000 (fee00000)
: >Feb 15 20:15:19 linux95 kernel: mapped IOAPIC to ffffd000 (fec00000)
: >Feb 15 20:15:19 linux95 kernel: Detected 337506524 Hz processor.
: >Feb 15 20:15:19 linux95 kernel: Console: colour VGA+ 80x25
: >Feb 15 20:15:19 linux95 kernel: Calibrating delay loop... 336.69 BogoMIPS
: >Feb 15 20:15:19 linux95 kernel: Memory: 128168k/131008k available (856k
: kernel code, 420k reserved, 151 6k data, 48k init)
: >Feb 15 20:15:19 linux95 kernel: Checking 386/387 coupling... OK, FPU using
: exception 16 error reporting.
: >Feb 15 20:15:19 linux95 kernel: Checking 'hlt' instruction... OK.
: >Feb 15 20:15:19 linux95 kernel: POSIX conformance testing by UNIFIX
: >Feb 15 20:15:19 linux95 kernel: mtrr: v1.26 (19981001) Richard Gooch
: ([EMAIL PROTECTED])
: >Feb 15 20:15:19 linux95 kernel: per-CPU timeslice cutoff: 25.03 usecs.
: >Feb 15 20:15:19 linux95 kernel: CPU1: Intel Celeron (Mendocino) stepping 00
: >Feb 15 20:15:19 linux95 kernel: calibrating APIC timer ...
: >Feb 15 20:15:19 linux95 kernel: ..... CPU clock speed is 337.5143 MHz.
: >Feb 15 20:15:19 linux95 kernel: ..... system bus clock speed is 75.0030
: MHz.
: >Feb 15 20:15:19 linux95 kernel: Booting processor 0 eip 2000
: >Feb 15 20:15:19 linux95 kernel: Calibrating delay loop... 336.69 BogoMIPS
: >Feb 15 20:15:19 linux95 kernel: OK.
: >Feb 15 20:15:19 linux95 kernel: CPU0: Intel Celeron (Mendocino) stepping 00
: >Feb 15 20:15:19 linux95 kernel: Total of 2 processors activated (673.38
: BogoMIPS).
: >Feb 15 20:15:19 linux95 kernel: enabling symmetric IO mode... ...done.
: >Feb 15 20:15:19 linux95 kernel: ENABLING IO-APIC IRQs
: >Feb 15 20:15:19 linux95 kernel: init IO_APIC IRQs
: >
: >
: >v*** what does this line mean? **v
: >
: >Feb 15 20:15:19 linux95 kernel: IO-APIC pin 0, 3, 10, 11, 13, 15, 20, 21,
: 22, 23 not connected.
: >
: >
: >Feb 15 20:15:19 linux95 kernel: number of MP IRQ sources: 15.
: >Feb 15 20:15:19 linux95 kernel: number of IO-APIC registers: 24.
: >Feb 15 20:15:19 linux95 kernel: testing the IO APIC.......................
: >Feb 15 20:15:19 linux95 kernel: .... register #00: 02000000
: >Feb 15 20:15:19 linux95 kernel: ....... : physical APIC id: 02
: >Feb 15 20:15:19 linux95 kernel: .... register #01: 00170011
: >Feb 15 20:15:19 linux95 kernel: ....... : max redirection entries: 0017
: >Feb 15 20:15:19 linux95 kernel: ....... : IO APIC version: 0011
: >Feb 15 20:15:19 linux95 kernel: .... register #02: 00000000
: >Feb 15 20:15:19 linux95 kernel: ....... : arbitration: 00
: >
: >
: >v** what's this table about? **v
: >
: >Feb 15 20:15:19 linux95 kernel: .... IRQ redirection table:
: >Feb 15 20:15:19 linux95 kernel: NR Log Phy Mask Trig IRR Pol Stat Dest
: Deli Vect:
: >Feb 15 20:15:19 linux95 kernel: 00 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 01 000 00 0 0 0 0 0 1 1
: 59
: >Feb 15 20:15:19 linux95 kernel: 02 0FF 0F 0 0 0 0 0 1 1
: 51
: >Feb 15 20:15:19 linux95 kernel: 03 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 04 000 00 0 0 0 0 0 1 1
: 61
: >Feb 15 20:15:19 linux95 kernel: 05 000 00 0 0 0 0 0 1 1
: 69
: >Feb 15 20:15:19 linux95 kernel: 06 000 00 0 0 0 0 0 1 1
: 71
: >Feb 15 20:15:19 linux95 kernel: 07 000 00 0 0 0 0 0 1 1
: 79
: >Feb 15 20:15:19 linux95 kernel: 08 000 00 0 0 0 0 0 1 1
: 81
: >Feb 15 20:15:19 linux95 kernel: 09 000 00 0 0 0 0 0 1 1
: 89
: >Feb 15 20:15:19 linux95 kernel: 0a 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 0b 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 0c 000 00 0 0 0 0 0 1 1
: 91
: >Feb 15 20:15:19 linux95 kernel: 0d 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 0e 000 00 0 0 0 0 0 1 1
: 99
: >Feb 15 20:15:19 linux95 kernel: 0f 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 10 0FF 0F 1 1 0 1 0 1 1
: A1
: >Feb 15 20:15:19 linux95 kernel: 11 0FF 0F 1 1 0 1 0 1 1
: A9
: >Feb 15 20:15:19 linux95 kernel: 12 0FF 0F 1 1 0 1 0 1 1
: B1
: >Feb 15 20:15:19 linux95 kernel: 13 0FF 0F 1 1 0 1 0 1 1
: B9
: >Feb 15 20:15:19 linux95 kernel: 14 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 15 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 16 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: 17 000 00 1 0 0 0 0 0 0
: 00
: >Feb 15 20:15:19 linux95 kernel: .................................... done.
: >
: >
: >v** should I be concerned with these msgs? **v
: >
: >Feb 15 20:15:19 linux95 kernel: mtrr: your CPUs had inconsistent fixed MTRR
: settings
: >Feb 15 20:15:19 linux95 kernel: mtrr: your CPUs had inconsistent variable
: MTRR settings
: >Feb 15 20:15:19 linux95 kernel: mtrr: probably your BIOS does not setup all
: CPUs
: >
: >
: >--
: >AntiSpam: For email, change all 'zero' chars to letter 'o' chars.
: >
--
AntiSpam: For email, change all 'zero' chars to letter 'o' chars.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
