O_DIRECT leaks memory on linux-2.6.0-test9

O_DIRECT leaks memory on linux-2.6.0-test9

[IWAMOTO Toshihiro]

Hi,

recently I noticed that direct IO causes memory leaks with
linux-2.6.0-test9.
The program that causes memory leaks is "fsstress", which is
testcases/kernel/fs/fsstress in ltp-full-20031106.tgz (ftp from
http://sourceforge.net/projects/ltp/).

fsstress does various file operations, and I found that the problem is
with the combination of write and dread (O_DIRECT read).
You should be able to reproduce the bug with the following command
line.

$ while true; do ./fsstress -c -d /usr/src/test -z -f write=1 \
 -f dread=1 -f creat=1 -S -n 1000 -p 32; done

The test machine is a quad P3 machine with the following file systems.
/usr/src is an ext3 file system but mounted as an ext2 using mount -t ext2.
$ mount -v
/dev/rd/c0d0p2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/rd/c0d0p5 on /usr/src type ext2 (rw)


I didn't see memory leaks with the other three combinations of
read+write (dread+dwrite, read+dwrite, and read+write).

Any ideas?
I'll try to debug this next week, but rather like to see the fix
in the meanwhile. :)
--
IWAMOTO Toshihiro

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Andrew Morton]

IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
>
>  recently I noticed that direct IO causes memory leaks with
>  linux-2.6.0-test9.
>  The program that causes memory leaks is "fsstress", which is
>  testcases/kernel/fs/fsstress in ltp-full-20031106.tgz (ftp from
>  http://sourceforge.net/projects/ltp/).
> 
>  fsstress does various file operations, and I found that the problem is
>  with the combination of write and dread (O_DIRECT read).
>  You should be able to reproduce the bug with the following command
>  line.
> 
>  $ while true; do ./fsstress -c -d /usr/src/test -z -f write=1 \
>   -f dread=1 -f creat=1 -S -n 1000 -p 32; done

It seems OK here.   Please take a copy of /proc/meminfo and /proc/slabinfo.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[IWAMOTO Toshihiro]

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

At Thu, 20 Nov 2003 23:17:49 -0800,
Andrew Morton wrote:
> 
> IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
> >
> >  recently I noticed that direct IO causes memory leaks with
> >  linux-2.6.0-test9.
> >  The program that causes memory leaks is "fsstress", which is
> >  testcases/kernel/fs/fsstress in ltp-full-20031106.tgz (ftp from
> >  http://sourceforge.net/projects/ltp/).
> > 
> >  fsstress does various file operations, and I found that the problem is
> >  with the combination of write and dread (O_DIRECT read).
> >  You should be able to reproduce the bug with the following command
> >  line.
> > 
> >  $ while true; do ./fsstress -c -d /usr/src/test -z -f write=1 \
> >   -f dread=1 -f creat=1 -S -n 1000 -p 32; done
> 
> It seems OK here.   Please take a copy of /proc/meminfo and /proc/slabinfo.

It'll take a while to leak a noticable amount of memory. So I reduced
the amount of memory using a boot option.
I'll try the same test on another machine.

Here they are. slabinfo is in the attachment.

$ cat /proc/meminfo
MemTotal:       254592 kB
MemFree:          3952 kB
Buffers:           688 kB
Cached:           6184 kB
SwapCached:       2512 kB
Active:           8616 kB
Inactive:       212056 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       254592 kB
LowFree:          3952 kB
SwapTotal:     2097136 kB
SwapFree:      2090436 kB
Dirty:               0 kB
Writeback:           0 kB
Mapped:           4924 kB
Slab:            15200 kB
Committed_AS:    20580 kB
PageTables:        344 kB
VmallocTotal:   770040 kB
VmallocUsed:      9460 kB
VmallocChunk:   760580 kB


[-- Attachment #2: slabinfo.gz --]
[-- Type: application/octet-stream, Size: 2061 bytes --]

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Andrew Morton]

IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
>
> It'll take a while to leak a noticable amount of memory. So I reduced
>  the amount of memory using a boot option.

Well I'll be darned.  I took a new version of fsstress and it happens here
too.  We're leaking anonymous memory.  -mm doesn't do any better, either.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Gene Heskett]

On Friday 21 November 2003 02:55, Andrew Morton wrote:
>IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
>> It'll take a while to leak a noticable amount of memory. So I
>> reduced the amount of memory using a boot option.
>
>Well I'll be darned.  I took a new version of fsstress and it
> happens here too.  We're leaking anonymous memory.  -mm doesn't do
> any better, either.

Running 2.6.0-test9-mm4, default as scheduler

That triggerd me to go look at ksysguard, and I've got 70 megs out in 
swap in less than 24 hours uptime with my normal loading.  Usually it 
takes me a couple of weeks to get that much as I've half a gig of 
main memory.  Its also showing about 95 megs free.  Would this leak 
show up there (ksysguard), and if so, in what section?

T'would be nice if xosview were to be made operable, but this kernel 
breaks it.  I used to keep it running in the corner of one of my 
screens.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Andrew Morton]

Gene Heskett <gene.heskett@verizon.net> wrote:
>
> On Friday 21 November 2003 02:55, Andrew Morton wrote:
> >IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
> >> It'll take a while to leak a noticable amount of memory. So I
> >> reduced the amount of memory using a boot option.
> >
> >Well I'll be darned.  I took a new version of fsstress and it
> > happens here too.  We're leaking anonymous memory.  -mm doesn't do
> > any better, either.
> 
> Running 2.6.0-test9-mm4, default as scheduler
> 
> That triggerd me to go look at ksysguard, and I've got 70 megs out in 
> swap in less than 24 hours uptime with my normal loading.  Usually it 
> takes me a couple of weeks to get that much as I've half a gig of 
> main memory.

That's good.  The kernel has given you 70 megs more memory.

>  Its also showing about 95 megs free.

free memory isn't really relevant.  If there's plenty of `buffers' and
pagecache around then it's mostly reclaimable.

>  Would this leak 
> show up there (ksysguard), and if so, in what section?

I don't know.

> T'would be nice if xosview were to be made operable, but this kernel 
> breaks it.  I used to keep it running in the corner of one of my 
> screens.

I had a patch for that.  Maybe it got merged.  You should hunt down the
upstream source and try it out.

For diagnosing this sort of thing it is best to learn to read the /proc
files.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Gene Heskett]

On Friday 21 November 2003 03:40, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>> On Friday 21 November 2003 02:55, Andrew Morton wrote:
>> >IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
>> >> It'll take a while to leak a noticable amount of memory. So I
>> >> reduced the amount of memory using a boot option.
>> >
>> >Well I'll be darned.  I took a new version of fsstress and it
>> > happens here too.  We're leaking anonymous memory.  -mm doesn't
>> > do any better, either.
>>
>> Running 2.6.0-test9-mm4, default as scheduler
>>
>> That triggerd me to go look at ksysguard, and I've got 70 megs out
>> in swap in less than 24 hours uptime with my normal loading. 
>> Usually it takes me a couple of weeks to get that much as I've
>> half a gig of main memory.
>
>That's good.  The kernel has given you 70 megs more memory.
>
>>  Its also showing about 95 megs free.
>
Now its down to about 80, and the display for cache and buffers has 
shrunk considerably.  Normal after boot memory usage is in the 125 
meg area, and that portion of the display is now around 350 megs, 
having grown 100megs or so overnight.

>free memory isn't really relevant.  If there's plenty of `buffers'
> and pagecache around then it's mostly reclaimable.

Those two colors in the ksysguard report window are getting mighty 
thin.

>>  Would this leak
>> show up there (ksysguard), and if so, in what section?
>
>I don't know.
>
>> T'would be nice if xosview were to be made operable, but this
>> kernel breaks it.  I used to keep it running in the corner of one
>> of my screens.
>
>I had a patch for that.  Maybe it got merged.  You should hunt down
> the upstream source and try it out.

The srcs for xosview?  I did a freshmeat search, and what I found 
hadn't been touched in over a year.  I didn't bother grabbing it as 
it was the same version number as the copy I have.

>For diagnosing this sort of thing it is best to learn to read the
> /proc files.

cat /proc/meminfo:
MemTotal:       514964 kB
MemFree:        171100 kB
Buffers:         14256 kB
Cached:          80548 kB
SwapCached:      15912 kB
Active:         220456 kB
Inactive:         5124 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       514964 kB
LowFree:        171100 kB
SwapTotal:     3857104 kB
SwapFree:      3786316 kB
Dirty:              52 kB
Writeback:           0 kB
Mapped:         181676 kB
Slab:           111528 kB
Committed_AS:   540836 kB
PageTables:       2144 kB
VmallocTotal:   515896 kB
VmallocUsed:     51372 kB
VmallocChunk:   464524 kB

But in the various memory related things in /proc, I don't see a 
reference to anonymous?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Gene Heskett]

On Friday 21 November 2003 09:02, Gene Heskett wrote:
[...]
>>I had a patch for that.  Maybe it got merged.  You should hunt down
>> the upstream source and try it out.
>
>The srcs for xosview?  I did a freshmeat search, and what I found
>hadn't been touched in over a year.  I didn't bother grabbing it as
>it was the same version number as the copy I have.

I must have followed the wrong link, 1.8.1 is building now.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: O_DIRECT leaks memory on linux-2.6.0-test9

[Gene Heskett]

On Friday 21 November 2003 09:25, Gene Heskett wrote:
>On Friday 21 November 2003 09:02, Gene Heskett wrote:
>[...]
>
>>>I had a patch for that.  Maybe it got merged.  You should hunt
>>> down the upstream source and try it out.
>>
>>The srcs for xosview?  I did a freshmeat search, and what I found
>>hadn't been touched in over a year.  I didn't bother grabbing it as
>>it was the same version number as the copy I have.
>
>I must have followed the wrong link, 1.8.1 is building now.

But it won't build the memsat.o module when enabled.  Many pages of 
parse errors if I softlink the newest version number of it to 
memstat.c. Otherwise it cannot find it at all. Not much meat in the 
README's either.  That isn't the one with the newest date however, 
wth?

I'll try without it.

And that, when built, then './xosview' to run it insitu, never shows 
its window, and never shows up in the process table.  A ctrl-c 
returns the prompt instantly.  So I'm not going to install that 
one...

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Oops on module insertion of 3c509/3c95x

[Alexander Nyberg]

This is a problem in 2.6.0-test10 and now tested with 2.6-test11-bk8 
aswell which shows itself as I accidently
tried to modprobe the wrong module (3c509) for my NIC which is:
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
And after it modprobed 3c59x.
This does NOT seem to happen with other modules, nor any other module
in the 3cxxx series other than 3c509. This happens with pci=noacpi
aswell.

The impact of this is that the module's used counter "starts" at 1, 
which makes it impossible (ok, maybe with force) to unload it.
(I cut the oops out of dmesg if anyone wonders.)
---------------------------------------------------------------

storage:~#modprobe 3c509
FATAL: Error inserting 3c509
(/lib/modules/2.6.0-test10/kernel/drivers/net/3c509.ko): No such device

storage:~# modprobe 3c59x
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0d.0: 3Com PCI 3c905C Tornado at 0xdc00. Vers LK1.1.19
Unable to handle kernel paging request at virtual address e082cb58
 printing eip:
c0250b3f
*pde = 1ff6d067
*pte = 00000000
Oops: 0002 [#1]
CPU:    0
EIP:    0060:[<c0250b3f>]    Not tainted
EFLAGS: 00010296
EIP is at kobject_add+0x6f/0x110
eax: c039a200   ebx: e087ca5c   ecx: e082cb58   edx: e087ca78
esi: c039a208   edi: 00000000   ebp: e087ca44   esp: de5b9f04
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 347, threadinfo=de5b8000 task=defb3980)
Stack: c039a208 e087ca60 e087ca5c e087ca5c ffffffea 00000000 c0250c08
e087ca5c
       e087ca5c c039a1a0 e087ca5c c039a1a0 c0294b9a e087ca5c e0878928
00000000
       00000001 c0386bd8 c0386bd8 c029501f e087ca44 e087cb84 e0878928
c0386bf0
Call Trace:
 [<c0250c08>] kobject_register+0x28/0x60
 [<c0294b9a>] bus_add_driver+0x4a/0xa0
 [<c029501f>] driver_register+0x2f/0x40
 [<c02cf869>] eisa_driver_register+0x19/0x30
 [<e082a01f>] vortex_eisa_init+0x1f/0x80 [3c59x]
 [<e082af44>] vortex_init+0x24/0x7f [3c59x]
 [<c012f685>] sys_init_module+0x105/0x1d0
 [<c0108f1f>] syscall_call+0x7/0xb

Code: 89 11 89 4a 04 8b 43 28 8b 38 8d 4f 48 89 c8 ba ff ff 00 00
 Segmentation fault

storage:~#

---------------------------------------------------------------

storage:~# cat /proc/modules
3c59x 38472 1 - Loading 0xe0875000
rtc 11768 0 - Live 0xe0864000
ide_cd 40580 0 - Live 0xe0814000
cdrom 34656 1 ide_cd, Live 0xe0820000

---------------------------------------------------------------

storage:~# dmesg
Linux version 2.6.0-test10 (root@storage) (gcc version 3.3.2 (Debian))
#1 Mon Nov 24 18:45:56 CET 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
 BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
 BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131056
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 126960 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 VT8371                                    ) @
0x000f7890
ACPI: RSDT (v001 VT8371 AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x1fff3000
ACPI: FADT (v001 VT8371 AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x1fff3040
ACPI: DSDT (v001 VT8371 AWRDACPI 0x00001000 MSFT 0x0100000c) @
0x00000000
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=Linux-2.6-10 ro root=301
console=ttyS0,9600 console=tty0
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 1050.212 MHz processor.
Console: colour VGA+ 80x25
Memory: 514800k/524224k available (2265k kernel code, 8676k reserved,
615k data, 392k init, 0k highmem)
Calibrating delay loop... 2068.48 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0183fbff c1c7fbff 00000000
00000000
CPU:     After vendor identify, caps: 0183fbff c1c7fbff 00000000
00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After all inits, caps: 0183fbff c1c7fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) processor stepping 04
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1049.0942 MHz.
..... host bus clock speed is 199.0989 MHz.
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfb4e0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031002
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 03): [55] 89 & 1f ->
09
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even
'acpi=off'
Machine check exception polling timer started.
VFS: Disk quotas dquot_6.5.1
SGI XFS for Linux with ACLs, realtime, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
Applying VIA southbridge workaround.
PCI: Disabling Via external APIC routing
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 32M @ 0xe8000000
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller at PCI slot 0000: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 vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: SAMSUNG SV2001H, ATA DISK drive
hdb: CD-ROM 52X/AKH, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 39179952 sectors (20060 MB) w/2048KiB Cache, CHS=38869/16/63,
UDMA(100)
 hda: hda1 hda2
mice: PS/2 mouse device common for all mice
input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
device-mapper: 4.0.0-ioctl (2003-06-04) initialised: dm@uk.sistina.com
EISA: Probing bus 0 at eisa0
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 392k freed
EXT3 FS on hda1, internal journal
hdb: ATAPI 52X CD-ROM drive, 192kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 327672k swap on /dev/vg00/swap.  Priority:-1 extents:1
Real Time Clock Driver v1.12

---------------------------------------------------------------

storage:/usr/src# lspci -vvv
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
        Subsystem: ABIT Computer Corp. KT7/KT7-RAID/KT7A/KT7A-RAID
Mainboard
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
        Latency: 8
        Region 0: Memory at e8000000 (32-bit, prefetchable) [size=32M]
        Capabilities: [a0] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
(prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000f000-00000fff
        Memory behind bridge: ea000000-ebffffff
        Prefetchable memory behind bridge: e0000000-e7ffffff
        BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
        Subsystem: ABIT Computer Corp.: Unknown device 0000
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
        Subsystem: VIA Technologies, Inc.
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Region 4: I/O ports at d000 [size=16]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
40)
        Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin ? routed to IRQ 11
        Capabilities: [68] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 74)
        Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC
Management NIC
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32
bytes)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at dc00 [size=128]
        Region 1: Memory at ed000000 (32-bit, non-prefetchable)
[size=128]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-

00:11.0 SCSI storage controller: Adaptec AHA-2940UW Pro / AIC-788x (rev
01)
        Subsystem: Adaptec 2940UW Pro Ultra-Wide SCSI Controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 2000ns max), Cache Line Size: 0x08 (32
bytes)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at e000 [size=256]
        Region 1: Memory at ed001000 (32-bit, non-prefetchable)
[size=4K]
        Expansion ROM at <unassigned> [disabled] [size=64K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: nVidia Corporation NV15 [GeForce2
GTS/Pro] (rev a3) (prog-if 00 [VGA])
        Subsystem: LeadTek Research Inc. WinFast GeForce2 GTS with TV
output
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (1250ns min, 250ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ea000000 (32-bit, non-prefetchable)
[size=16M]
        Region 1: Memory at e0000000 (32-bit, prefetchable) [size=128M]
        Expansion ROM at <unassigned> [disabled] [size=64K]
        Capabilities: [60] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [44] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>

---------------------------------------------------------------

storage:/usr/src# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) processor
stepping        : 4
cpu MHz         : 1050.262
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips        : 2068.48

---------------------------------------------------------------

storage:/usr/src# cat /proc/ioports
0000-001f : dma1
0020-0021 : pic1
0040-005f : timer
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
02f8-02ff : serial
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
5000-500f : 0000:00:07.4
6000-607f : 0000:00:07.4
d000-d00f : 0000:00:07.1
  d000-d007 : ide0
  d008-d00f : ide1
dc00-dc7f : 0000:00:0d.0
  dc00-dc7f : 0000:00:0d.0
e000-e0ff : 0000:00:11.0

---------------------------------------------------------------

storage:/usr/src# cat /proc/iomem
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000cc000-000cc7ff : Extension ROM
000cd000-000cd7ff : Extension ROM
000f0000-000fffff : System ROM
00100000-1ffeffff : System RAM
  00100000-003377a1 : Kernel code
  003377a2-003d153f : Kernel data
1fff0000-1fff2fff : ACPI Non-volatile Storage
1fff3000-1fffffff : ACPI Tables
e0000000-e7ffffff : PCI Bus #01
  e0000000-e7ffffff : 0000:01:00.0
e8000000-e9ffffff : 0000:00:00.0
ea000000-ebffffff : PCI Bus #01
  ea000000-eaffffff : 0000:01:00.0
ed000000-ed00007f : 0000:00:0d.0
ed001000-ed001fff : 0000:00:11.0
ffff0000-ffffffff : reserved