GNU patch relative to 2.5.59:
http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5.59-20030122-gnupatch.gz
BK send and tarball distributions:
http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.4-20030122.bksend.gz
http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5-20030122.bksend.gz
http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.4-20030122-tar.gz
http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5-20030122-tar.gz
Driver update diskettes for most distributions:
http://people.FreeBSD.org/~gibbs/linux/DUD/aic7xxx/
http://people.FreeBSD.org/~gibbs/linux/DUD/aic79xx/
RPMs for most distributions:
http://people.FreeBSD.org/~gibbs/linux/RPM/aic7xxx/
http://people.FreeBSD.org/~gibbs/linux/RPM/aic79xx/
Changes since the driver versions incorperated in 2.5.59:
[email protected], 2003-01-22 15:09:24-07:00, [email protected]
Bump aic79xx driver version number to 1.3.0, now that it has
passed functional test.
[email protected], 2003-01-22 14:44:51-07:00, [email protected]
Update Aic7xxx and Aic79xx driver documentation.
[email protected], 2003-01-20 16:46:37-07:00, [email protected]
Aic7xxx Driver Update 6.2.28
o Add some more DV diagnostic code
o Fix bug that caused sequencer debug code to be
downloaded always.
Aic79xx Driver Update 1.3.0.RC2
o Correct a regression in RC1 that effectively limited DV to just ID 0.
o Add some more DV diagnostic code
o Misc code cleanups.
[email protected], 2003-01-17 14:49:42-07:00, [email protected]
Aic7xxx and Aic79xx Driver Update
Force an SDTR after a rejected WDTR if the syncrate is unkonwn.
[email protected], 2003-01-17 13:20:53-07:00, [email protected]
Bump aic7xxx driver version to 6.2.27.
[email protected], 2003-01-17 13:17:49-07:00, [email protected]
Aic7xxx Driver Update:
o Determine more conclusively that a BIOS has initialized the
adapter before using "left over BIOS settings".
o Adapt to upcoming removal of cmd->target/channel/lun/host in 2.5.X
o Fix a memory leak on driver unload.
o Enable the pci_parity command line option and default to pci parity
error detection *disabled*. There are just too many broken VIA
chipsets out there.
o Move more functionality into aiclib to share with the aic79xx driver.
o Correct a few negotiation regressions.
o Don't bother doing full DV on devices that only support async transfers.
This should fix a few more of the reported problems with DV.
Aic79xx Driver Update
o Add abort and bus device reset handlers.
o Fix a memory leak on driver unload.
o Adapt to upcoming removal of cmd->target/channel/lun/host in 2.5.X.
o Correct a few negotiation regressions.
[email protected], 2003-01-17 12:18:22-07:00, [email protected]
Aic79xx Driver Update
Enable abort and bus device reset handlers for both legacy
and packetized connections.
[email protected], 2003-01-17 12:10:23-07:00, [email protected]
Aic7xxx and Aic79xx DV Fix:
Don't bother with DV if the device can only do async
On 23 January 2003 00:50, Justin T. Gibbs wrote:
> GNU patch relative to 2.5.59:
>
> http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5.59-20030
>122-gnupatch.gz
I didn't track your development efforts too closely...
does this mean that latest 2.4 (2.4.20?) will detect my oldie 7782?
On 24 October 2002 15:45, Denis Vlasenko wrote:
> > > The problem is that it does not see its disks when I boot Linux.
> > > Currently I'm running it in NFS root mode, but 16MB RAM is not
> > > much fun without swap :(
> > >
> > > I'd like to stick printks here and there in driver source,
> > > thought you may have some advice.
> >
> > Since you seem to have enabled the EISA/VLB probe in your config,
> > I don't know why your controller is not probed.
>
> I sticked some printks in the code, here is a new syslog output
> (diff with printks is at the end).
--
vda
> On 23 January 2003 00:50, Justin T. Gibbs wrote:
>> GNU patch relative to 2.5.59:
>>
>> http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5.59-20030
>> 122-gnupatch.gz
>
> I didn't track your development efforts too closely...
> does this mean that latest 2.4 (2.4.20?) will detect my oldie 7782?
The Olvetti EISA IDs have been included since 6.2.24?? or so.
--
Justin
Justin T. Gibbs on Thu 23/01 08:08 -0700:
> > I didn't track your development efforts too closely... does this
> > mean that latest 2.4 (2.4.20?) will detect my oldie 7782?
>
> The Olvetti EISA IDs have been included since 6.2.24?? or so.
Which means that they won't be detected with the 2.4 mainline tree,
which appears to have 6.2.8 in 21-pre3.
FWIW, I can't run my NFS server without Justin's patches; it blows up
easily under load (even a simple resync of the RAID array running off it
causes all kinds of errors after only a few minutes). This is a 7892.
With Justin's 6.2.24 driver it works great even when I beat the hell out
of it.
On Wed, 2003-01-22 at 14:50, Justin T. Gibbs wrote:
> GNU patch relative to 2.5.59:
> http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5.59-20030122-gnupatch.gz
Justin, I haven't checked, but have you deleted my change
again to include asm/io.h in aix7xxx_osm.h?
You keep doing this, I wish you'd stop :-)
More seriously, you really need to look at the build etc.
fixes people put into your driver in 2.5.x, it is rude to
keep deleting such changes over and over again.
From: "Justin T. Gibbs" <[email protected]>
Date: Thu, 23 Jan 2003 20:45:05 -0700
> You keep doing this, I wish you'd stop :-)
I wish you'd actually look at the changes before assuming
what they do and don't contain.
You deleted my change on at least two occaisions.
If you've stopped doing that, great.
> On Wed, 2003-01-22 at 14:50, Justin T. Gibbs wrote:
>> GNU patch relative to 2.5.59:
>> http://people.FreeBSD.org/~gibbs/linux/SRC/aic79xx-linux-2.5.59-2003012
>> 2-gnupatch.gz
>
> Justin, I haven't checked, but have you deleted my change
> again to include asm/io.h in aix7xxx_osm.h?
>
> You keep doing this, I wish you'd stop :-)
I wish you'd actually look at the changes before assuming
what they do and don't contain.
--
Justin
> From: "Justin T. Gibbs" <[email protected]>
> Date: Thu, 23 Jan 2003 20:45:05 -0700
>
> > You keep doing this, I wish you'd stop :-)
>
> I wish you'd actually look at the changes before assuming
> what they do and don't contain.
>
> You deleted my change on at least two occaisions.
> If you've stopped doing that, great.
And when it happened the first time, you didn't bother to tell
me? Why? So you could act slighted later?
If you really care to have an update *stick* to a piece of externally
maintained software, pass your changes through the maintainer. That is
only reasonable.
There have been lots of changes to the driver that I have merged back
manually and lots that I have tossed as incorrect and should never have
been accepted by Linus in the first place. In your case, the change was
small *and* incomplete (you didn't update the aic79xx driver), so it was
missed during a few of my merges. If you had simply bothered to send me
email when you submitted the change to Linus (you seem to know my email
address and that I maintain the driver) both drivers would have had this
change long ago.
And yes, both drivers, as of this drop, now include asm/io.h.
--
Justin
From: "Justin T. Gibbs" <[email protected]>
Date: Thu, 23 Jan 2003 20:56:38 -0700
And when it happened the first time, you didn't bother to tell
me? Why? So you could act slighted later?
Because it is your duty as maintainer to watch what changes
(especially build fixes) go into Linus's and Marcelo's tree.
> From: "Justin T. Gibbs" <[email protected]>
> Date: Thu, 23 Jan 2003 20:56:38 -0700
>
> And when it happened the first time, you didn't bother to tell
> me? Why? So you could act slighted later?
>
> Because it is your duty as maintainer to watch what changes
> (especially build fixes) go into Linus's and Marcelo's tree.
That's like saying that its Linus's or Marcelo's responsibility
to catch whether you or anyone else submits a bogus/broken change
to their tree. Nobody catches everything all the time and mistakes,
bugs, etc. get merged into 2.4.X and 2.5.X every day. Such is life,
especially in a volunteer project where nobody has a duty or
reponsibility to do anything at all.
If a change or bugfix to my driver is important to you, send it to
me and it will not get missed. That's what everyone except you does,
and interestingly enough, you are the only one complaining. 8-)
--
Justin
From: "Justin T. Gibbs" <[email protected]>
Date: Thu, 23 Jan 2003 21:26:36 -0700
> Because it is your duty as maintainer to watch what changes
> (especially build fixes) go into Linus's and Marcelo's tree.
That's like saying that its Linus's or Marcelo's responsibility
to catch whether you or anyone else submits a bogus/broken change
to their tree.
Your driver update broke the build of Linus's tree, so I sent Linus
a change that fixed the build.
And in fact, you are describing exactly what Linus and Marcelo's
jobs are, to reject bogus/broken changes.
> And in fact, you are describing exactly what Linus and Marcelo's
> jobs are, to reject bogus/broken changes.
I think you missed the subtely of what I said. It's not "their duty"
to never make a mistake, and it is not expected that they will catch
everything. When they do miss something, or make a mistake you probably
tell them in a straight forward fashion. In this case, what you
effectively said to me was:
"Hey. I would appreciate it if you would stop not
noticing this change that I made to your code through
Linus without telling you. *Twice* no less. Wake up!
Wasn't it obvious? It is *your duty* to notice these
one line changes that happen to break the build on
a platform that I care about but doesn't have any
consequences on the platforms you are probably testing.
Oh, and the aic79xx driver... well I didn't bother to
look at that because it's not in my configuration.
Oh well."
And I get all of this grief *after* I already included the change
instead of after the first time I missed it. You really make me
laugh!
--
Justin
From: "Justin T. Gibbs" <[email protected]>
Date: Thu, 23 Jan 2003 21:54:37 -0700
You really make me laugh!
I'm glad that we've established that we both provide endless amounts
of comedy for each other.
Look Justin, the fact remains that you get paid top dollar to maintain
the Linux Adaptec driver. If you can't be bothered to reliably
integrate fixes that show up in Linus's and Marcelo's tree, then
that's regretfully sad given your circumstances.
Now that is what makes me laugh!
On Thu, 23 Jan 2003, David S. Miller wrote:
> I'm glad that we've established that we both provide endless amounts
> of comedy for each other.
>
> Look Justin, the fact remains that you get paid top dollar to maintain
> the Linux Adaptec driver. If you can't be bothered to reliably
> integrate fixes that show up in Linus's and Marcelo's tree, then
> that's regretfully sad given your circumstances.
>
> Now that is what makes me laugh!
David,
this is not how distributed development can work. The communication
clearly is broken here.
Regardless of whether Linus' tree is broken or no, ALWAYS Cc: the fixes
-- even if trivial -- to the driver maintainer. It's as simple as that.
Same about complaints. If a tree breaks, complaining to the maintainer
in addition to Linus/Marcelo/Alan may yield a "Linus' merge is
incomplete, here's the missing bit" message from the maintainer.
It's all about communication. If maintainers drown in messages, they'll
tell this (Linus for example is notorious for dropping messages).
I don't mean to offend anyone, but what you expect looks like
clairvoyance to me, regardless of whether Justin gets paid or not, this
is simply not reasonable to expect.
Unless someone comes up with a "watchmydriver" script that checks the
ChangeSet figures of a set of files after every bk pull and complains if
Linus' tree complains unauthorized ChangeSets. I'm not sure if there is
an invariant tag that remains across getting bk patches applied or if
real diffs are needed. Larry or other BK experts might know more.
--
Matthias Andree
On Sun, Jan 26, 2003 at 06:09:27PM +0100, Matthias Andree wrote:
> Regardless of whether Linus' tree is broken or no, ALWAYS Cc: the fixes
> -- even if trivial -- to the driver maintainer. It's as simple as that.
That is not how things works out.
Doing trivial changes to 10+ Makefiles does not require to bother
10+ arch maintaners. Same goes for trivial fixes for any subsystem.
Linus pointed out what to do:
Keep a copy of the kernel used for last sync.
Take a copy of latest kernel.
Do a diff of all relevant files, and apply that before submitting.
When it was brought up last time, someone came with a small script to
do so.
No bk magic or other stuff needed, and I see that used by many arch
maintainers - otherwise they would loose to many trivial changes.
Sam
I bought an Adaptec 2940UW card about a month ago and I've had three
kernel panics spaced more than a week apart (2.4.19). After the 2nd
crash I hooked up a serial console and it registered the following
messages,
Kernel panic: HOST_MSG_LOOP with invalid SCB 2
In interrupt handler - not syncing
the only messages before those two were bootup and ppp messages.
After reading some older kernel list e-mails about write combining
(this is a old VIA chipset) I installed
aic79xx-linux-2.4-20030122-tar.gz into a fresh 2.4.21-pre4 tree
compiled and rebooted I haven't had any problems, I'll just have to
wait a couple weeks and see what happens. Now I'm getting some error
messages on bootup I didn't get previously and I would like to know if
I should ignore them or not. I have one IDE harddrive, one IDE cdrom,
one SCSI harddrive, and one SCSI cdrom.
Current boot messages
============================================================
Linux version 2.4.21-pre4 (root@SpacedOut) (gcc version 2.95.4 20011002 (Debian prerelease)) #27 Sat Feb 8 23:16:01 CST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff0800 (ACPI NVS)
BIOS-e820: 000000000fff0800 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=2.4.21 ro root=302 console=ttyS0,115200
Initializing CPU#0
Detected 300.689 MHz processor.
Console: colour VGA+ 80x60
Calibrating delay loop... 599.65 BogoMIPS
Memory: 256760k/262080k available (1290k kernel code, 4936k reserved, 375k data, 220k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: AMD-K6(tm) 3D processor stepping 00
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch ([email protected])
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xfb360, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class.
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c586b (rev 41) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLP LM15, ATA DISK drive
hda: DMA disabled
hdc: PLEXTOR CD-R PX-W4012A, ATAPI CD/DVD-ROM drive
hdc: DMA disabled
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 29336832 sectors (15020 MB) w/1900KiB Cache, CHS=29104/16/63
Partition check:
hda: hda1 hda2
SCSI subsystem driver Revision: 1.00
PCI: Assigned IRQ 10 for device 00:08.0
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.28
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Vendor: IBM Model: DGHS09U Rev: 0350
Type: Direct-Access ANSI SCSI revision: 03
(scsi0:A:3:0): refuses WIDE negotiation. Using 8bit transfers
scsi0:0:3:0: Attempting to queue an ABORT message
>>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
scsi0: Dumping Card State in Data-in phase, at SEQADDR 0x7d
Card was paused
ACCUM = 0xf4, SINDEX = 0xb8, DINDEX = 0xa8, ARG_2 = 0x0
HCNT = 0xf4 SCBPTR = 0x0
SCSISIGI[0x44]:(BSYI|IOI) ERROR[0x0] SCSIBUSL[0x20]
LASTPHASE[0x40]:(IOI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI)
SBLKCTL[0x2]:(SELWIDE) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE)
SEQ_FLAGS[0x20]:(DPHASE) SSTAT0[0x0] SSTAT1[0x2]:(PHASECHG)
SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x0] SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO)
SXFRCTL0[0x80]:(DFON) DFCNTRL[0x78]:(HDMAEN|SDMAEN|SCSIEN|WIDEODD)
DFSTATUS[0x40]:(DFCACHETH)
STACK: 0x0 0x16c 0x19c 0x6f
SCB count = 4
Kernel NEXTQSCB = 3
Card NEXTQSCB = 3
QINFIFO entries:
Waiting Queue entries:
Disconnected Queue entries:
QOUTFIFO entries:
Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Sequencer SCB Info:
0 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x37] SCB_LUN[0x0]
SCB_TAG[0x2]
1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
3 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
4 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
5 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
6 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
7 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
8 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
9 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
10 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
11 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
12 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
13 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
14 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
15 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
SCB_LUN[0xff]:(LID) SCB_TAG[0xff]
Pending list:
2 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x37] SCB_LUN[0x0]
Kernel Free SCB list: 1 0
Untagged Q(3): 2
DevQ(0:0:0): 0 waiting
DevQ(0:3:0): 0 waiting
<<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>>
scsi0:0:3:0: Device is active, asserting ATN
Recovery code sleeping
Recovery code awake
Timer Expired
aic7xxx_abort returns 0x2003
scsi0:0:3:0: Attempting to queue a TARGET RESET message
aic7xxx_dev_reset returns 0x2003
Recovery SCB completes
(scsi0:A:3): 8.333MB/s transfers (8.333MHz, offset 15)
Vendor: YAMAHA Model: CRW4416S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)
sda: sda1 sda2
Linux video capture interface: v1.00
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 220k freed
INIT: version 2.84 booting
============================================================
previous 2.4.19 boot message
============================================================
Linux version 2.4.19 (root@SpacedOut) (gcc version 2.95.4 20011002 (Debian prerelease)) #24 Tue Oct 29 14:30:22 CST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff0800 (ACPI NVS)
BIOS-e820: 000000000fff0800 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
Advanced speculative caching feature not present
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=2.4.19 ro root=302 console=ttyS0
Initializing CPU#0
Detected 300.688 MHz processor.
Console: colour VGA+ 80x60
Calibrating delay loop... 599.65 BogoMIPS
Memory: 257060k/262080k available (1106k kernel code, 4636k reserved, 274k data, 208k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: AMD-K6(tm) 3D processor stepping 00
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch ([email protected])
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xfb360, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class.
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: detected chipset, but driver not compiled in!
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
hda: QUANTUM FIREBALLP LM15, ATA DISK drive
hdc: PLEXTOR CD-R PX-W4012A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 29336832 sectors (15020 MB) w/1900KiB Cache, CHS=29104/16/63
Partition check:
hda: hda1 hda2
Linux video capture interface: v1.00
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: ide0(3,2): orphan cleanup on readonly fs
EXT3-fs: ide0(3,2): 25 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 208k freed
INIT: version 2.84 booting
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Vendor: IBM Model: DGHS09U Rev: 0350
Type: Direct-Access ANSI SCSI revision: 03
hub.c: USB new device connect on bus1/2, assigned device number 3
Manufacturer: Logitech
Product: USB Mouse
input0: USB HID v1.10 Mouse [Logitech USB Mouse] on usb1:3.0
(scsi0:A:3): 8.333MB/s transfers (8.333MHz, offset 15)
Vendor: YAMAHA Model: CRW4416S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
sg sd_mod Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)
sda: sda1 sda2
isofs sr_mod Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
ide-scsi scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: PLEXTOR Model: CD-R PX-W4012A Rev: 1.02
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 0
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
============================================================
SCSI AIC config options,
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC79XX is not set
/proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT82C597 [Apollo VP3] (rev 4).
Master Capable. Latency=16.
Prefetchable 32 bit memory at 0xe0000000 [0xe3ffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (rev 0).
Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 65).
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 6).
Master Capable. Latency=64.
I/O at 0xe400 [0xe40f].
Bus 0, device 7, function 2:
USB Controller: VIA Technologies, Inc. USB (rev 2).
IRQ 9.
Master Capable. Latency=64.
I/O at 0xe000 [0xe01f].
Bus 0, device 7, function 3:
PCI bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 16).
IRQ 9.
Bus 0, device 8, function 0:
SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 0).
IRQ 10.
Master Capable. Latency=64. Min Gnt=8.Max Lat=8.
I/O at 0xe800 [0xe8ff].
Non-prefetchable 32 bit memory at 0xea000000 [0xea000fff].
Bus 0, device 9, function 0:
Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 17).
IRQ 12.
Master Capable. Latency=64. Min Gnt=16.Max Lat=40.
Prefetchable 32 bit memory at 0xea001000 [0xea001fff].
Bus 0, device 9, function 1:
Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 17).
IRQ 12.
Master Capable. Latency=64. Min Gnt=4.Max Lat=255.
Prefetchable 32 bit memory at 0xea002000 [0xea002fff].
Bus 0, device 10, function 0:
Multimedia audio controller: Trident Microsystems 4DWave DX (rev 2).
IRQ 7.
Master Capable. Latency=64. Min Gnt=2.Max Lat=5.
I/O at 0xec00 [0xecff].
Non-prefetchable 32 bit memory at 0xea003000 [0xea003fff].
Bus 1, device 0, function 0:
VGA compatible controller: Matrox Graphics, Inc. MGA G200 AGP (rev 1).
IRQ 10.
Master Capable. Latency=64. Min Gnt=16.Max Lat=32.
Prefetchable 32 bit memory at 0xe8000000 [0xe8ffffff].
Non-prefetchable 32 bit memory at 0xe4000000 [0xe4003fff].
Non-prefetchable 32 bit memory at 0xe5000000 [0xe57fffff].
/proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DGHS09U Rev: 0350
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: YAMAHA Model: CRW4416S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: PLEXTOR Model: CD-R PX-W4012A Rev: 1.02
Type: CD-ROM ANSI SCSI revision: 02
/proc/scsi/aic7xxx/0
Adaptec AIC7xxx driver version: 6.2.28
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
Serial EEPROM:
0xc178 0xc178 0xc178 0xc158 0xc178 0xc178 0xc178 0xc378
0xc178 0xc178 0xc178 0xc178 0xc178 0xc178 0xc178 0xc178
0x18a6 0x001b 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x5a2d
Channel A Target 0 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Goal: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Curr: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Channel A Target 0 Lun 0 Settings
Commands Queued 17048
Commands Active 0
Command Openings 64
Max Tagged Openings 253
Device Queue Frozen Count 0
Channel A Target 1 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 2 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 3 Negotiation Settings
User: 20.000MB/s transfers (20.000MHz, offset 255)
Goal: 8.333MB/s transfers (8.333MHz, offset 15)
Curr: 8.333MB/s transfers (8.333MHz, offset 15)
Channel A Target 3 Lun 0 Settings
Commands Queued 5
Commands Active 0
Command Openings 1
Max Tagged Openings 0
Device Queue Frozen Count 0
Channel A Target 4 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 5 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 6 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 7 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 8 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 9 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 10 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 11 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 12 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 13 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 14 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
Channel A Target 15 Negotiation Settings
User: 40.000MB/s transfers (20.000MHz, offset 255, 16bit)
--
David Fries <[email protected]>
http://fries.net/~david/pgpkey.txt