2004-06-22 17:47:28

by George Georgalis

[permalink] [raw]
Subject: SIIMAGE sata fails with 2.6.7

My via C3 Ezra is out to lunch after big SiI3112 sata writes.

dd if=/dev/zero of=/usr/zero2 bs=1024 count=100000

causes no apparent problems...

dd if=/dev/zero of=/usr/zero2 bs=1024 count=500000
500000+0 records in
500000+0 records out

seems to complete, but 4/5 times a process, pdflush, continues at 98%
cpu. I'm using reiserfs.

shells open continue to work (and I can run the command again without
error), but anything that requires access to the /usr partition does not
return. ...Another attempt to run the command is not returning, now dd
is at 96% cpu, pdflush is at 0% cpu and top (still interactive) is the
only other non-idle process.

There is a problem booting too. The sata drive is seen as /dev/hdc
(primary sata channel, only one on board ata channel) but linux seems to
think there is a drive on the second sata channel /dev/hde, which takes
30 seconds to timeout.

hde: no response (status = 0xfe)
hde: no response (status = 0xfe), resetting drive
hde: no response (status = 0xfe)

I suspect there is a configuration to not do that, but I don't know what
it is. Presently, nothing is connected to the single on board ide channel
(hda, hdb), but no apparent difference when a cdrom is on hda with the
hdc sata drive.

VIA EPIA-V 10000A (1x UltraDMA 100/66 Connector)
Addonics ADSA2 Serial ATA PCI host controller
Seagate Barracuda 7200.7 160GB 7200rpm 8MB Buffer Serial ATA Hard Drive - ST3160023AS

http://www.viavpsd.com/product/epia_v_spec.jsp
http://www.addonics.com/products/host_controller/sata_controller.asp

I'm using a the SIIMAGE (Silicon Image chipset support) in a monolithic
2.6.7 kernel with the SiI3112 chipset, per bootup message.


00:14.0 RAID bus controller: CMD Technology Inc: Unknown device 3112 (rev 02)
Subsystem: CMD Technology Inc: Unknown device 6112
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 15
I/O ports at dc00 [size=8]
I/O ports at e000 [size=4]
I/O ports at e400 [size=8]
I/O ports at e800 [size=4]
I/O ports at ec00 [size=16]
Memory at e4400000 (32-bit, non-prefetchable) [size=512]
Expansion ROM at <unassigned> [disabled] [size=512K]
Capabilities: [60] Power Management version 2


My config is attached and I'm happy to try with other kernels or run
specific debugging.

// George



--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631


Attachments:
(No filename) (2.49 kB)
linux-2.6.7-sta.config (27.57 kB)
Download all attachments

2004-06-22 20:32:36

by Jeff Garzik

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

does sata_sil driver work for you?

2004-06-23 14:17:09

by George Georgalis

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Tue, Jun 22, 2004 at 04:25:42PM -0400, Jeff Garzik wrote:
>does sata_sil driver work for you?

I have this file,

-rw-r--r-- 1 500 500 12779 Jun 16 01:18 ./drivers/scsi/sata_sil.c

but I don't see a switch for it in the config, also I'm not sure where
the most recent patch for it is.

// George


--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-23 15:33:01

by Hugo Mills

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Wed, Jun 23, 2004 at 10:16:59AM -0400, George Georgalis wrote:
> On Tue, Jun 22, 2004 at 04:25:42PM -0400, Jeff Garzik wrote:
> >does sata_sil driver work for you?
>
> I have this file,
>
> -rw-r--r-- 1 500 500 12779 Jun 16 01:18 ./drivers/scsi/sata_sil.c
>
> but I don't see a switch for it in the config, also I'm not sure where
> the most recent patch for it is.

The option is under

Device Drivers --->
SCSI device support --->
SCSI low-level drivers --->
[*] Serial ATA (SATA)
< > ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL) (NEW)
< > Intel PIIX/ICH SATA support (NEW)
< > Promise SATA support (NEW)
<*> Silicon Image SATA support (NEW)
< > VIA SATA support (NEW)
< > VITESSE VSC-7174 SATA support (NEW)

Hugo.

--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- "Your problem is that you have a negative personality." ---
"No, I don't!"


Attachments:
(No filename) (1.10 kB)
signature.asc (189.00 B)
Digital signature
Download all attachments

2004-06-23 16:35:21

by George Georgalis

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Wed, Jun 23, 2004 at 04:32:35PM +0100, Hugo Mills wrote:
>On Wed, Jun 23, 2004 at 10:16:59AM -0400, George Georgalis wrote:
>> On Tue, Jun 22, 2004 at 04:25:42PM -0400, Jeff Garzik wrote:
>> >does sata_sil driver work for you?
>>
>> I have this file,
>>
>> -rw-r--r-- 1 500 500 12779 Jun 16 01:18 ./drivers/scsi/sata_sil.c
>>
>> but I don't see a switch for it in the config, also I'm not sure where
>> the most recent patch for it is.
>
> The option is under
>
>Device Drivers --->
> SCSI device support --->
> SCSI low-level drivers --->
> [*] Serial ATA (SATA)
> < > ServerWorks Frodo / Apple K2 SATA support (EXPERIMENTAL) (NEW)
> < > Intel PIIX/ICH SATA support (NEW)
> < > Promise SATA support (NEW)
> <*> Silicon Image SATA support (NEW)
> < > VIA SATA support (NEW)
> < > VITESSE VSC-7174 SATA support (NEW)
>

Thanks, I discovered and was building that after I discovered the
"development and/or incomplete code/drivers" option is also required.

My system would not boot without SIIMAGE too, is that expected?
Should there be a dependency in menuconfig?

Sad news, at about 800 Mb, pdflush stopped completing and the device
was blocked.

Oooh, guess I needed to mount as a scsi dev now? but I don't see any
scsi devices available... must I first not mount the hdc partitions?

// George



--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-23 17:36:18

by Ricky Beam

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Wed, 23 Jun 2004, George Georgalis wrote:
>Oooh, guess I needed to mount as a scsi dev now? but I don't see any
>scsi devices available... must I first not mount the hdc partitions?

Don't compile in the SIIMAGE driver. The IDE drivers are probed before
SCSI, so it'll assume control of the chip and sata_sil will never get
a chance.

And you'll need a current bitkeeper snapshot (or -bk# tarball made after
6/22) to have the sata_sil Seagate drive fix.

--Ricky


2004-06-23 20:26:54

by George Georgalis

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Wed, Jun 23, 2004 at 01:30:12PM -0400, Ricky Beam wrote:
>On Wed, 23 Jun 2004, George Georgalis wrote:
>>Oooh, guess I needed to mount as a scsi dev now? but I don't see any
>>scsi devices available... must I first not mount the hdc partitions?
>
>Don't compile in the SIIMAGE driver. The IDE drivers are probed before
>SCSI, so it'll assume control of the chip and sata_sil will never get
>a chance.
>
>And you'll need a current bitkeeper snapshot (or -bk# tarball made after
>6/22) to have the sata_sil Seagate drive fix.

I patched 2.6.7 with bk6, configured no SIIMAGE and with SCSI_SATA_SIL.
(I got errors with security/selinux/hooks.c so I disabled SELinux)

I changed "hdc" entries to "sda" in fstab and grub, but on reboot
my root, sda1, could not be found. Might it be another device?
Or something else? config attached.

Next attempt will put root on an ata device, but I'm looking to boot
from sata.

// George

--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631


Attachments:
(No filename) (1.11 kB)
linux-2.6.7-bk6-ezra-sata.config (32.00 kB)
Download all attachments

2004-06-23 21:29:22

by Fabian Fenaut

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

I think you need CONFIG_BLK_DEV_INITRD, otherwise libata and sata_sil
won't be loaded at boot.

George Georgalis wrote:
> I patched 2.6.7 with bk6, configured no SIIMAGE and with
> SCSI_SATA_SIL. (I got errors with security/selinux/hooks.c so I
> disabled SELinux)
>
> I changed "hdc" entries to "sda" in fstab and grub, but on reboot my
> root, sda1, could not be found. Might it be another device? Or
> something else? config attached.
>
> Next attempt will put root on an ata device, but I'm looking to boot
> from sata.
>
> ------------------------------------------------------------------------
> #
> # Automatically generated make config: don't edit
> #
> [...]
> # CONFIG_BLK_DEV_INITRD is not set
> [...]

2004-06-23 22:00:42

by George Georgalis

[permalink] [raw]
Subject: Re: SIIMAGE and sata_sil with 2.6.7-bk

On Wed, Jun 23, 2004 at 11:23:37PM +0200, Fabian Fenaut wrote:
>I think you need CONFIG_BLK_DEV_INITRD, otherwise libata and sata_sil
>won't be loaded at boot.

Since this is a monolithic kernel, that shouldn't be required.

I now have the box up on an ATA disk, root=/dev/hda1
but I don't see the sata drive or any scsi devices in
/proc/sys/dev/scsi/

This seems to indicate "sata_sil" which is more than lspci

# cat /proc/bus/pci/devices | grep sata
00a0 10953112 f 0000dc01 0000e001 0000e401 0000e801 0000ec01 e4400000 00000000 00000008 00000004 00000008 00000004 00000010 00000200 00080000 sata_sil


do I need to change my partition types to md or something? (...oh, atm I
can't.) Why isn't the controler in /proc/sys/dev/scsi/?

// George

--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-24 01:05:13

by Ricky Beam

[permalink] [raw]
Subject: Re: SIIMAGE sata fails with 2.6.7

On Wed, 23 Jun 2004, George Georgalis wrote:
>I changed "hdc" entries to "sda" in fstab and grub, but on reboot
>my root, sda1, could not be found. Might it be another device?
>Or something else? config attached.

# CONFIG_BLK_DEV_SD is not set

I'm gonna go ahead and say what I'm thinking *grin*... well, duh. There's
no support for any SCSI DISKS. libata is a scsi driver which makes your
sata drives appear as scsi drives.

Turn that on, recompile, and reboot.

--Ricky


2004-06-24 15:59:24

by George Georgalis

[permalink] [raw]
Subject: SATA_SIL fails with 2.6.7-bk6 seagate drive

On Wed, Jun 23, 2004 at 08:59:06PM -0400, Ricky Beam wrote:
>On Wed, 23 Jun 2004, George Georgalis wrote:
>>I changed "hdc" entries to "sda" in fstab and grub, but on reboot
>>my root, sda1, could not be found. Might it be another device?
>>Or something else? config attached.
>
># CONFIG_BLK_DEV_SD is not set
>
>I'm gonna go ahead and say what I'm thinking *grin*... well, duh. There's
>no support for any SCSI DISKS. libata is a scsi driver which makes your
>sata drives appear as scsi drives.
>
>Turn that on, recompile, and reboot.

Whoops! Well that got me able to mount it. Thanks!

dd if=/dev/zero of=/mnt/zero-`date +%s`

has caused pdflush to block IO, any access to /mnt and the process
does not return. other than the pdflush load of ~99% the box seems to
function normally. 2.6.7-bk6, seagate drive

I enabled some video options which seem to have blanked my display,
wrong driver, bug or overscanning text console (?), not sure; but I'll
follow up with more detailed sata report when I get video okay (at least
24 hrs).

// George

--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-24 18:53:39

by Ricky Beam

[permalink] [raw]
Subject: Re: SATA_SIL fails with 2.6.7-bk6 seagate drive

On Thu, 24 Jun 2004, George Georgalis wrote:
...
>has caused pdflush to block IO, any access to /mnt and the process
>does not return. other than the pdflush load of ~99% the box seems to
>function normally. 2.6.7-bk6, seagate drive

-bk6 is not new enough. bk7 has the necessary max_sectors fix. You
may need to add your drive model to the sil_blacklist in
drivers/scsi/sata_sil.c.

--Ricky


2004-06-25 21:34:45

by George Georgalis

[permalink] [raw]
Subject: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Thu, Jun 24, 2004 at 02:46:39PM -0400, Ricky Beam wrote:
>On Thu, 24 Jun 2004, George Georgalis wrote:
>...
>>has caused pdflush to block IO, any access to /mnt and the process
>>does not return. other than the pdflush load of ~99% the box seems to
>>function normally. 2.6.7-bk6, seagate drive
>
>-bk6 is not new enough. bk7 has the necessary max_sectors fix. You
>may need to add your drive model to the sil_blacklist in
>drivers/scsi/sata_sil.c.

Okay, 2.6.7-bk8 has written 8Gb to the sda4 with SATA_SIL and still
going strong! "dd if=/dev/zero of=/mnt/zero-`date +%s`"

However at about 3Gb (if that is relevant) top segfaulted with a
non critical oops. top will not restart, but the box is otherwise
functioning well considering the write load.

Is there any way to determine the drive model without first connecting
with the other sata driver (as hdc) and using hdparm?


Unable to handle kernel NULL pointer dereference at virtual address 000000b4
printing eip:
c017c78a
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c017c78a>] Not tainted
EFLAGS: 00010286 (2.6.7-sta-bk8)
EIP is at pid_alive+0xa/0x30
eax: 000000b8 ebx: d32b0310 ecx: 00000000 edx: 00000000
esi: 00000000 edi: ef7bb7a0 ebp: d22b1b40 esp: db473e4c
ds: 007b es: 007b ss: 0068
Process top (pid: 489, threadinfo=db472000 task=e60ac7c0)
Stack: c017cca4 00000000 d22b1b40 db473f18 ef7bb7a0 db473ec4 c0159754 d22b1b40
db473f18 eaa1f006 eaa1f009 db473ec4 db473f18 c0159cc5 db473f18 db473ecc
db473ec4 ef7b86e0 d22b1dfc ee655240 bffff000 c0141ec8 c15cd660 c013e95c
Call Trace:
[<c017cca4>] pid_revalidate+0x14/0xc0
[<c0159754>] do_lookup+0x44/0x80
[<c0159cc5>] link_path_walk+0x535/0xa20
[<c0141ec8>] find_extend_vma+0x18/0x70
[<c013e95c>] follow_page+0x8c/0xb0
[<c013ea3c>] get_user_pages+0xbc/0x3d0
[<c015a406>] path_lookup+0x86/0x1a0
[<c015a6a9>] __user_walk+0x39/0x70
[<c0155a95>] vfs_stat+0x15/0x60
[<c02445dd>] copy_to_user+0x2d/0x40
[<c0156151>] sys_stat64+0x11/0x30
[<c014dcbd>] __fput+0x8d/0xf0
[<c014c6c3>] filp_close+0x43/0x70
[<c014c744>] sys_close+0x54/0x80
[<c0105dc7>] syscall_call+0x7/0xb




Could this be related to "Unknown HZ value! (91) Assume 100." which
started showing up with VIA motherboards on 2.5.x (I think) on top or ps
commands. When I researched it before, It never caused ill, had been
identified as a "kernel bug" but benign. I know nothing more.

ATM, ps also seg faults, here is a corresponding oops,

<1>Unable to handle kernel NULL pointer dereference at virtual address 000000b4
printing eip:
c017c78a
*pde = 00000000
Oops: 0000 [#5]
PREEMPT
CPU: 0
EIP: 0060:[<c017c78a>] Not tainted
EFLAGS: 00010286 (2.6.7-sta-bk8)
EIP is at pid_alive+0xa/0x30
eax: 000000b8 ebx: d32b0310 ecx: 00000000 edx: 00000000
esi: 00000000 edi: ef7bb7a0 ebp: d22b1b40 esp: ecc59e4c
ds: 007b es: 007b ss: 0068
Process ps (pid: 3456, threadinfo=ecc58000 task=e60ac7c0)
Stack: c017cca4 00000000 d22b1b40 ecc59f18 ef7bb7a0 ecc59ec4 c0159754 d22b1b40
ecc59f18 cf499006 cf499009 ecc59ec4 ecc59f18 c0159cc5 ecc59f18 ecc59ecc
ecc59ec4 ef7b86e0 d22b1dfc ee655240 bffff000 c0141ec8 c15cd660 c013e95c
Call Trace:
[<c017cca4>] pid_revalidate+0x14/0xc0
[<c0159754>] do_lookup+0x44/0x80
[<c0159cc5>] link_path_walk+0x535/0xa20
[<c0141ec8>] find_extend_vma+0x18/0x70
[<c013e95c>] follow_page+0x8c/0xb0
[<c013ea3c>] get_user_pages+0xbc/0x3d0
[<c015a406>] path_lookup+0x86/0x1a0
[<c015a6a9>] __user_walk+0x39/0x70
[<c0155a95>] vfs_stat+0x15/0x60
[<c02445dd>] copy_to_user+0x2d/0x40
[<c0156151>] sys_stat64+0x11/0x30
[<c014dcbd>] __fput+0x8d/0xf0
[<c014c6c3>] filp_close+0x43/0x70
[<c014c744>] sys_close+0x54/0x80
[<c0105dc7>] syscall_call+0x7/0xb
Code: 39 82 b4 00 00 00 75 07 8b 82 bc 00 00 00 c3 0f 0b 04 03 72


config attached. I wrote 25G of zero and killed the dd process, top and
ps still segfault. Thanks all for your help!

// George



--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631


Attachments:
(No filename) (4.07 kB)
2.6.7-sta-bk8.config.gz (7.87 kB)
Download all attachments

2004-06-25 23:16:25

by Linus Torvalds

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops



On Fri, 25 Jun 2004, George Georgalis wrote:
>
> However at about 3Gb (if that is relevant) top segfaulted with a
> non critical oops. top will not restart, but the box is otherwise
> functioning well considering the write load.

Ok, this is unlikely to be SATA-related, unless SATA just happened to
corrupt something really strange.

> Unable to handle kernel NULL pointer dereference at virtual address 000000b4
> printing eip:
> c017c78a
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[<c017c78a>] Not tainted
> EFLAGS: 00010286 (2.6.7-sta-bk8)
> EIP is at pid_alive+0xa/0x30

That's "p->pids[PIDTYPE_PID].pidptr", and it looks like "p" is NULL.

That in turn _shouldn't_ happen, since that comes from

struct task_struct *task = proc_task(inode);

and proc_task() should always be non-NULL for any /proc file that has one
of the pid-based dentry ops.

> Could this be related to "Unknown HZ value! (91) Assume 100." which
> started showing up with VIA motherboards on 2.5.x (I think) on top or ps
> commands. When I researched it before, It never caused ill, had been
> identified as a "kernel bug" but benign. I know nothing more.

No, that's just a pstools bug. It shouldn't try to guess HZ at all.

> ATM, ps also seg faults, here is a corresponding oops,

Same problem. One of your existing /proc/<xxx>/ directories has a NULL
"task" pointer, and that really shouldn't happen.

Hmm. I do worry that maybe it's the SATA thing that has written NULL
somewhere, since the /proc code never clears that field once it is set
(and it would always be set by the code that creates the inode in the
first place).

Linus

2004-06-26 14:59:24

by Albert Cahalan

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

Linus Torvalds writes:
> On Fri, 25 Jun 2004, George Georgalis wrote:

>> Could this be related to "Unknown HZ value! (91) Assume 100." which
>> started showing up with VIA motherboards on 2.5.x (I think) on top or ps
>> commands. When I researched it before, It never caused ill, had been
>> identified as a "kernel bug" but benign. I know nothing more.
>
> No, that's just a pstools bug. It shouldn't try to guess HZ at all.

With an older kernel I'd say he's losing 9% of his clock ticks.
In this case though, incompatible /proc/stat changes are
at fault. No longer does idle CPU time include IO-wait CPU time.
This shouldn't have changed; user tools can subtract as needed.

I'm sorry to say that the HZ-guessing code is now only
used for the 2.2.xx kernels. Over the years it has found
many clock problems. Had the 2.4.xx kernels used a 64-bit
jiffies counter, the HZ-guessing code would still be used.

You never did come up with an alternative to HZ-guessing
that would work on those old 1200-HZ Alpha boxes, the ARM
boxes that ran at 64 HZ and so on. I suppose you can blame
the arch maintainers, but user-space has to deal with it.
So HZ-guessing is a workaround for a kernel bug, especially
because you claim that HZ (USER_HZ now) is part of the ABI.


2004-06-26 15:12:38

by Arjan van de Ven

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops


> You never did come up with an alternative to HZ-guessing
> that would work on those old 1200-HZ Alpha boxes, the ARM
> boxes that ran at 64 HZ and so on. I suppose you can blame
> the arch maintainers, but user-space has to deal with it.
> So HZ-guessing is a workaround for a kernel bug, especially
> because you claim that HZ (USER_HZ now) is part of the ABI.

well.... this value is *passed to userspace* via the AT_ attributes ....
glibc probably nicely exports this info via sysconf(). I guess/hope your
tools are now using that ?


Attachments:
signature.asc (189.00 B)
This is a digitally signed message part

2004-06-26 15:54:58

by Linus Torvalds

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops



On Sat, 26 Jun 2004, Albert Cahalan wrote:
>
> You never did come up with an alternative to HZ-guessing
> that would work on those old 1200-HZ Alpha boxes, the ARM
> boxes that ran at 64 HZ and so on.

The fix for those should be that they should all export the same HZ to
user space, regardless of any internal tick. So that's a kernel bug, in
that those architectures expose the _internal_ HZ rather than some
user-visible well-defined one.

> I suppose you can blame the arch maintainers, but user-space has to deal
> with it.

If the user space tools didn't try to deal with it, the architectures
would probably get fixed in a jiffy. All the support for kernel-to-user HZ
conversion is there.

So I still maintain that procps should _not_ try to guess HZ. As it is,
it's a bug, and it helps make excuses for _other_ bugs.

Linus

2004-06-26 16:01:02

by Linus Torvalds

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops



On Sat, 26 Jun 2004, Arjan van de Ven wrote:
>
> well.... this value is *passed to userspace* via the AT_ attributes ....
> glibc probably nicely exports this info via sysconf(). I guess/hope your
> tools are now using that ?

Even then, it's a bug in my opinion. Yes, procps should be able to just
use sysconf(_SC_CLK_TCK), but the fact is, using CLK_TCK and HZ is
traditional unix behaviour, and we should just support it.

Linus

2004-06-26 16:15:08

by Arjan van de Ven

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Sat, 2004-06-26 at 18:00, Linus Torvalds wrote:
> On Sat, 26 Jun 2004, Arjan van de Ven wrote:
> >
> > well.... this value is *passed to userspace* via the AT_ attributes ....
> > glibc probably nicely exports this info via sysconf(). I guess/hope your
> > tools are now using that ?
>
> Even then, it's a bug in my opinion.

Agreed 100%. It gets kind of fun though if you have say 32 bit emulation
in a 64 bit kernel and the 64 bit environment has a different user HZ
than the 32 bit env....



Attachments:
signature.asc (189.00 B)
This is a digitally signed message part

2004-06-26 19:36:04

by Albert Cahalan

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Sat, 2004-06-26 at 11:12, Arjan van de Ven wrote:
> > You never did come up with an alternative to HZ-guessing
> > that would work on those old 1200-HZ Alpha boxes, the ARM
> > boxes that ran at 64 HZ and so on. I suppose you can blame
> > the arch maintainers, but user-space has to deal with it.
> > So HZ-guessing is a workaround for a kernel bug, especially
> > because you claim that HZ (USER_HZ now) is part of the ABI.
>
> well.... this value is *passed to userspace* via the AT_ attributes ....
> glibc probably nicely exports this info via sysconf(). I guess/hope your
> tools are now using that ?

They use the AT_ attribute when it is provided.
(Linux 2.4 and above only)

The glibc wrapper is defective; it takes a bad
guess at HZ when the AT_ attribute is missing.
Had sysconf() worked as documented, returning an
error code on failure, it would have been used.

The sysconf() call for getting the number of CPUs
is also broken, at least on SPARC. It would return
a 0 instead of the proper -1 error code. I think
it tried to scan /proc/cpuinfo for CPUs.



2004-06-26 19:39:23

by Albert Cahalan

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Sat, 2004-06-26 at 12:00, Linus Torvalds wrote:
> On Sat, 26 Jun 2004, Arjan van de Ven wrote:
> >
> > well.... this value is *passed to userspace* via the AT_ attributes ....
> > glibc probably nicely exports this info via sysconf(). I guess/hope your
> > tools are now using that ?
>
> Even then, it's a bug in my opinion. Yes, procps should be able to just
> use sysconf(_SC_CLK_TCK), but the fact is, using CLK_TCK and HZ is
> traditional unix behaviour, and we should just support it.

It's not working right now, likely due to non-integer HZ.
Here's a bug report.......


Even with the 2.6.7 kernel, I'm still getting reports of process
start times wandering. Here is an example:

"About 12 hours since reboot to 2.6.7 there was already a
difference of about 7 seconds between the real start time
and the start time reported by ps. Now, 24 hours since reboot
the difference is 10 seconds."

The calculation used is:

now - uptime + process_run_time

The code shown below works great on a 2.4.xx or earlier kernel.
It generally relys on USER_HZ, which is supposedly in our ABI.

I have a feeling we'll forever be chasing bugs related to not
using a PLL to drive the clock tick at exactly HZ ticks per second.
Perhaps the DragonflyBSD code could be stolen. Anyway, the code:

///////////////////////////////////////////////////////////////////////////
unsigned long seconds_since_1970 = time(NULL);
unsigned long seconds_since_boot = uptime(0,0);
unsigned long time_of_boot = seconds_since_1970 - seconds_since_boot;
int pr_stime(char *restrict const outbuf, const proc_t *restrict const pp){
struct tm *proc_time;
struct tm *our_time;
time_t t;
const char *fmt;
int tm_year;
int tm_yday;
our_time = localtime(&seconds_since_1970); /* not reentrant */
tm_year = our_time->tm_year;
tm_yday = our_time->tm_yday;
t = time_of_boot + pp->start_time / Hertz;
proc_time = localtime(&t); /* not reentrant, this corrupts our_time */
fmt = "%H:%M"; /* 03:02 23:59 */
if(tm_yday != proc_time->tm_yday) fmt = "%b%d"; /* Jun06 Aug27 */
if(tm_year != proc_time->tm_year) fmt = "%Y"; /* 1991 2001 */
return strftime(outbuf, 42, fmt, proc_time);
}
///////////////////////////////////////////////////////////////////////////


2004-06-28 02:13:26

by George Georgalis

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Fri, Jun 25, 2004 at 04:16:03PM -0700, Linus Torvalds wrote:
>That's "p->pids[PIDTYPE_PID].pidptr", and it looks like "p" is NULL.
>
>That in turn _shouldn't_ happen, since that comes from
>
> struct task_struct *task = proc_task(inode);
>
>and proc_task() should always be non-NULL for any /proc file that has one
>of the pid-based dentry ops.

>On Fri, 25 Jun 2004, George Georgalis wrote:
>> ATM, ps also seg faults, here is a corresponding oops,
>
>Same problem. One of your existing /proc/<xxx>/ directories has a NULL
>"task" pointer, and that really shouldn't happen.

The first thing I noticed when reading sata_sil.c was readl() and
writel() calls. Thinking that meant "read/write line" I guessed it
could invoke a sectors = 15 hardware issue with some data, and went to
see exactly what it means.

I haven't determined which include/asm-*/io.h is used for
MCYRIXIII/MVIAC3, but my best guess is include/asm-i386/io.h

#define readl(addr) (*(volatile unsigned int *) (addr))
#define writel(b,addr) (*(volatile unsigned int *) (addr) = (b))

then I find volatile in a driver example from
http://publications.gbdirect.co.uk/c_book/chapter8/const_and_volatile.html
Which describes how volatile is used to peek hardware status.

but, in sata_sil.c, sil_scr_write does

writel(val, mmio);

volatile is used for data, not status! I can't glean this construct
(when the data runs out it's null and the loop ends?). Was going to say
if hardware caused status to turn up null that could be checked and
assigned before being used...

On Sun, Jun 27, 2004 at 10:39:08AM -0700, Linus Torvalds wrote:
>So I stand by the rule: we should make _code_ have the access rules, and
>the data itself should never be volatile. And yes, jiffies breaks that
>rule, but hey, that's not something I'm proud of.

So sata_sil.c is using the wrong construct or am I not reading it right?

>Hmm. I do worry that maybe it's the SATA thing that has written NULL
>somewhere, since the /proc code never clears that field once it is set
>(and it would always be set by the code that creates the inode in the
>first place).

Might it come from reiserfs? I didn't mkfs again after the last sata
device block(s). I'll be doing some more experimentation, how would I
'find' the null in proc? can I detect that in user space?

// George


--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-29 08:30:34

by George Georgalis

[permalink] [raw]
Subject: radix-tree.c or sata_sil.c 2.6.7-bk oops



sata_sil version 0.54
kernel BUG at lib/radix-tree.c:271!
0000:00:14.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) Silicon Image Serial ATARaid Controller [ CMD/Sil 3112/3112A ] (rev 02)


on 2.6.7 from a bk checkout, yesterday, fresh reiserfs, at 4.2G of write
to sata sda1, dd segfaulted and the (soft) oops indicated radix-tree.c,
I don't know what that is. below is some info from bootup, the tail of
dmesg and .config

// George



sata_sil version 0.54
ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 15 (level, low) -> IRQ 15
ata1: SATA max UDMA/100 cmd 0xF0079080 ctl 0xF007908A bmdma 0xF0079000 irq 15
ata2: SATA max UDMA/100 cmd 0xF00790C0 ctl 0xF00790CA bmdma 0xF0079008 irq 15
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
Vendor: ATA Model: ST3160023AS Rev: 3.18
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0


ReiserFS: sda1: found reiserfs format "3.6" with standard journal
ReiserFS: sda1: using ordered data mode
ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda1: checking transaction log (sda1)
ReiserFS: sda1: Using r5 hash to sort names
ReiserFS: sda1: warning: Created .reiserfs_priv on sda1 - reserved for xattr storage.
------------[ cut here ]------------
kernel BUG at lib/radix-tree.c:271!
invalid operand: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c023de83>] Not tainted
EFLAGS: 00010086 (2.6.7)
EIP is at radix_tree_insert+0xb3/0x100
eax: ffffffff ebx: 00000000 ecx: 00000000 edx: 00000035
esi: fffffffa edi: db394e5c ebp: db394d84 esp: eb6f9d28
ds: 007b es: 007b ss: 0068
Process dd (pid: 479, threadinfo=eb6f8000 task=ef50c0b0)
Stack: 00000000 eb6f8000 c1222920 eee52ac4 c013046a eee52ac8 00109d75 c1222920
c1222920 c1222920 000000d2 00109d75 c01304cb c1222920 eee52ac4 00109d75
000000d2 c1222920 00000000 c01309a4 c1222920 eee52ac4 00109d75 000000d2
Call Trace:
[<c013046a>] add_to_page_cache+0x4a/0x90
[<c01304cb>] add_to_page_cache_lru+0x1b/0x40
[<c01309a4>] find_or_create_page+0x34/0xb0
[<c0192eb8>] reiserfs_prepare_file_region_for_write+0x8d8/0x970
[<c01933cf>] reiserfs_file_write+0x47f/0x700
[<c0295f21>] blk_run_queue+0x21/0x40
[<c02c06a3>] scsi_io_completion+0x1b3/0x450
[<c02cad4b>] sd_rw_intr+0x4b/0x1e0
[<c026c79f>] read_zero+0x1af/0x200
[<c0121139>] run_timer_softirq+0x109/0x1a0
[<c014c40a>] vfs_write+0xba/0x100
[<c014c4cd>] sys_write+0x2d/0x50
[<c0105c57>] syscall_call+0x7/0xb
Code: 0f 0b 0f 01 85 4d 45 c0 eb e7 0f 0b 0e 01 85 4d 45 c0 eb d0
<6>note: dd[479] exited with preempt_count 2
bad: scheduling while atomic!
[<c04196a3>] schedule+0x4b3/0x4c0
[<c013dbe7>] unmap_vmas+0x117/0x1f0
[<c013dcb2>] unmap_vmas+0x1e2/0x1f0
[<c0141a85>] exit_mmap+0x65/0x150
[<c01180c9>] mmput+0x59/0x80
[<c011bcf9>] do_exit+0x149/0x350
[<c0107560>] do_invalid_op+0x0/0xa0
[<c01072e3>] die+0xd3/0xe0
[<c01075f3>] do_invalid_op+0x93/0xa0
[<c023de83>] radix_tree_insert+0xb3/0x100
[<c0106c1d>] error_code+0x2d/0x40
[<c023de83>] radix_tree_insert+0xb3/0x100
[<c013046a>] add_to_page_cache+0x4a/0x90
[<c01304cb>] add_to_page_cache_lru+0x1b/0x40
[<c01309a4>] find_or_create_page+0x34/0xb0
[<c0192eb8>] reiserfs_prepare_file_region_for_write+0x8d8/0x970
[<c01933cf>] reiserfs_file_write+0x47f/0x700
[<c0295f21>] blk_run_queue+0x21/0x40
[<c02c06a3>] scsi_io_completion+0x1b3/0x450
[<c02cad4b>] sd_rw_intr+0x4b/0x1e0
[<c026c79f>] read_zero+0x1af/0x200
[<c0121139>] run_timer_softirq+0x109/0x1a0
[<c014c40a>] vfs_write+0xba/0x100
[<c014c4cd>] sys_write+0x2d/0x50
[<c0105c57>] syscall_call+0x7/0xb


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_MCYRIXIII=y
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_PROC_INTF is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_24_API=y
CONFIG_CPU_FREQ_TABLE=y

#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_LONGRUN is not set
CONFIG_X86_LONGHAUL=y

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCI_USE_VECTOR is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set
CONFIG_MTD_CONCAT=y

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
# CONFIG_MTD_BLOCK is not set
CONFIG_MTD_BLOCK_RO=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
CONFIG_MTD_ABSENT=y
# CONFIG_MTD_OBSOLETE_CHIPS is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_SC520CDP is not set
# CONFIG_MTD_SCx200_DOCFLASH is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_MEGARAID is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_ATA_PIIX is not set
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
CONFIG_SCSI_SATA_SIL=y
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
# CONFIG_DM_ZERO is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=y

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set

#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=y

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=y
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=y
# CONFIG_IEEE1394_RAWIO is not set
# CONFIG_IEEE1394_CMP is not set

#
# I2O device support
#
CONFIG_I2O=y
CONFIG_I2O_CONFIG=y
CONFIG_I2O_BLOCK=y
CONFIG_I2O_SCSI=y
CONFIG_I2O_PROC=y

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y

#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=y
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=y
# CONFIG_IP_VS_WRR is not set
# CONFIG_IP_VS_LC is not set
# CONFIG_IP_VS_WLC is not set
# CONFIG_IP_VS_LBLC is not set
# CONFIG_IP_VS_LBLCR is not set
# CONFIG_IP_VS_DH is not set
# CONFIG_IP_VS_SH is not set
CONFIG_IP_VS_SED=y
# CONFIG_IP_VS_NQ is not set

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=y
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_FTP=y
CONFIG_IP_NF_IRC=y
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_IPRANGE=y
# CONFIG_IP_NF_MATCH_MAC is not set
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
# CONFIG_IP_NF_MATCH_DSCP is not set
CONFIG_IP_NF_MATCH_AH_ESP=y
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_HELPER=y
CONFIG_IP_NF_MATCH_STATE=y
CONFIG_IP_NF_MATCH_CONNTRACK=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
# CONFIG_IP_NF_TARGET_NETMAP is not set
CONFIG_IP_NF_TARGET_SAME=y
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_DSCP=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_CLASSIFY=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_NF_TARGET_NOTRACK is not set
CONFIG_IP_NF_RAW=y
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
CONFIG_XFRM=y
CONFIG_XFRM_USER=y

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_CSZ is not set
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_DELAY is not set
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_CLS_RSVP=y
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y
# CONFIG_VIA_VELOCITY is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_PCIPS2=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I8XX_TCO is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_MACHZ_WDT is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_HW_RANDOM=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_INTEL_MCH is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=y
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
CONFIG_HANGCHECK_TIMER=y

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set

#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=y

#
# Video For Linux
#

#
# Video Adapters
#
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set

#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_RTCTIMER=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
CONFIG_SND_VIA82XX=y
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
CONFIG_SND_USB_AUDIO=y

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_W9968CF is not set

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
# CONFIG_REISERFS_FS_POSIX_ACL is not set
CONFIG_REISERFS_FS_SECURITY=y
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=y
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
# CONFIG_FAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
# CONFIG_JFFS2_FS_NAND is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=y
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
CONFIG_NLS_CODEPAGE_869=y
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
CONFIG_NLS_ISO8859_7=y
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=y
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_ARC4 is not set
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_TEST=y

#
# Library routines
#
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-29 08:47:47

by Sebastian Slota

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

Hi,

I'm breaking the testing for some 3 months, I'm writing a work and I'm short
of time...

so far:
Tried Kernel with bk8:

root@t-rex root # cat /proc/mdstat
Personalities : [raid0] [raid5] [multipath]
md1 : active raid5 sdc3[2] sdb3[1] sda3[0]
261730816 blocks level 5, 128k chunk, algorithm 2 [3/3] [UUU]

md0 : active raid0 sdc2[2] sdb2[1] sda2[0]
73256064 blocks 128k chunks

unused devices: <none>

root@t-rex root # hdparm -tT /dev/md0

/dev/md0:
Timing buffer-cache reads: 3896 MB in 2.01 seconds = 1935.71 MB/sec
Timing buffered disk reads: 274 MB in 3.02 seconds = 90.68 MB/sec
root@t-rex root # hdparm -tT /dev/md1

/dev/md1:
Timing buffer-cache reads: 3760 MB in 2.00 seconds = 1879.35 MB/sec
Timing buffered disk reads: 206 MB in 3.01 seconds = 68.49 MB/secc

Copy a DVD to HD, both went OK!
copy data from an ATA HD ( hda ) broke.

I read from ppl they're running linux on some older hardware, maybe thats
why it doesnt work... but ~25mb/s is nothing for me...
Also I hear about some patches to limit the speed to ~30MB/s.

I hope its kidding!

Back to M$. there it works.

S.


> On Thu, Jun 24, 2004 at 02:46:39PM -0400, Ricky Beam wrote:
> >On Thu, 24 Jun 2004, George Georgalis wrote:
> >...
> >>has caused pdflush to block IO, any access to /mnt and the process
> >>does not return. other than the pdflush load of ~99% the box seems to
> >>function normally. 2.6.7-bk6, seagate drive
> >
> >-bk6 is not new enough. bk7 has the necessary max_sectors fix. You
> >may need to add your drive model to the sil_blacklist in
> >drivers/scsi/sata_sil.c.
>
> Okay, 2.6.7-bk8 has written 8Gb to the sda4 with SATA_SIL and still
> going strong! "dd if=/dev/zero of=/mnt/zero-`date +%s`"
>
> However at about 3Gb (if that is relevant) top segfaulted with a
> non critical oops. top will not restart, but the box is otherwise
> functioning well considering the write load.
>
> Is there any way to determine the drive model without first connecting
> with the other sata driver (as hdc) and using hdparm?
>
>
> Unable to handle kernel NULL pointer dereference at virtual address
> 000000b4
> printing eip:
> c017c78a
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[<c017c78a>] Not tainted
> EFLAGS: 00010286 (2.6.7-sta-bk8)
> EIP is at pid_alive+0xa/0x30
> eax: 000000b8 ebx: d32b0310 ecx: 00000000 edx: 00000000
> esi: 00000000 edi: ef7bb7a0 ebp: d22b1b40 esp: db473e4c
> ds: 007b es: 007b ss: 0068
> Process top (pid: 489, threadinfo=db472000 task=e60ac7c0)
> Stack: c017cca4 00000000 d22b1b40 db473f18 ef7bb7a0 db473ec4 c0159754
> d22b1b40
> db473f18 eaa1f006 eaa1f009 db473ec4 db473f18 c0159cc5 db473f18
> db473ecc
> db473ec4 ef7b86e0 d22b1dfc ee655240 bffff000 c0141ec8 c15cd660
> c013e95c
> Call Trace:
> [<c017cca4>] pid_revalidate+0x14/0xc0
> [<c0159754>] do_lookup+0x44/0x80
> [<c0159cc5>] link_path_walk+0x535/0xa20
> [<c0141ec8>] find_extend_vma+0x18/0x70
> [<c013e95c>] follow_page+0x8c/0xb0
> [<c013ea3c>] get_user_pages+0xbc/0x3d0
> [<c015a406>] path_lookup+0x86/0x1a0
> [<c015a6a9>] __user_walk+0x39/0x70
> [<c0155a95>] vfs_stat+0x15/0x60
> [<c02445dd>] copy_to_user+0x2d/0x40
> [<c0156151>] sys_stat64+0x11/0x30
> [<c014dcbd>] __fput+0x8d/0xf0
> [<c014c6c3>] filp_close+0x43/0x70
> [<c014c744>] sys_close+0x54/0x80
> [<c0105dc7>] syscall_call+0x7/0xb
>
>
>
>
> Could this be related to "Unknown HZ value! (91) Assume 100." which
> started showing up with VIA motherboards on 2.5.x (I think) on top or ps
> commands. When I researched it before, It never caused ill, had been
> identified as a "kernel bug" but benign. I know nothing more.
>
> ATM, ps also seg faults, here is a corresponding oops,
>
> <1>Unable to handle kernel NULL pointer dereference at virtual address
> 000000b4
> printing eip:
> c017c78a
> *pde = 00000000
> Oops: 0000 [#5]
> PREEMPT
> CPU: 0
> EIP: 0060:[<c017c78a>] Not tainted
> EFLAGS: 00010286 (2.6.7-sta-bk8)
> EIP is at pid_alive+0xa/0x30
> eax: 000000b8 ebx: d32b0310 ecx: 00000000 edx: 00000000
> esi: 00000000 edi: ef7bb7a0 ebp: d22b1b40 esp: ecc59e4c
> ds: 007b es: 007b ss: 0068
> Process ps (pid: 3456, threadinfo=ecc58000 task=e60ac7c0)
> Stack: c017cca4 00000000 d22b1b40 ecc59f18 ef7bb7a0 ecc59ec4 c0159754
> d22b1b40
> ecc59f18 cf499006 cf499009 ecc59ec4 ecc59f18 c0159cc5 ecc59f18
> ecc59ecc
> ecc59ec4 ef7b86e0 d22b1dfc ee655240 bffff000 c0141ec8 c15cd660
> c013e95c
> Call Trace:
> [<c017cca4>] pid_revalidate+0x14/0xc0
> [<c0159754>] do_lookup+0x44/0x80
> [<c0159cc5>] link_path_walk+0x535/0xa20
> [<c0141ec8>] find_extend_vma+0x18/0x70
> [<c013e95c>] follow_page+0x8c/0xb0
> [<c013ea3c>] get_user_pages+0xbc/0x3d0
> [<c015a406>] path_lookup+0x86/0x1a0
> [<c015a6a9>] __user_walk+0x39/0x70
> [<c0155a95>] vfs_stat+0x15/0x60
> [<c02445dd>] copy_to_user+0x2d/0x40
> [<c0156151>] sys_stat64+0x11/0x30
> [<c014dcbd>] __fput+0x8d/0xf0
> [<c014c6c3>] filp_close+0x43/0x70
> [<c014c744>] sys_close+0x54/0x80
> [<c0105dc7>] syscall_call+0x7/0xb
> Code: 39 82 b4 00 00 00 75 07 8b 82 bc 00 00 00 c3 0f 0b 04 03 72
>
>
> config attached. I wrote 25G of zero and killed the dd process, top and
> ps still segfault. Thanks all for your help!
>
> // George
>
>
>
> --
> George Georgalis, Architect and administrator, Linux services. IXOYE
> http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
> Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631
>

--
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info

2004-06-30 04:44:26

by George Georgalis

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

On Tue, Jun 29, 2004 at 10:46:45AM +0200, Sebastian Slota wrote:
>Tried Kernel with bk8:
>
>root@t-rex root # cat /proc/mdstat
>Personalities : [raid0] [raid5] [multipath]
>md1 : active raid5 sdc3[2] sdb3[1] sda3[0]
>261730816 blocks level 5, 128k chunk, algorithm 2 [3/3] [UUU]
>
>md0 : active raid0 sdc2[2] sdb2[1] sda2[0]
>73256064 blocks 128k chunks
>
>unused devices: <none>
>
>root@t-rex root # hdparm -tT /dev/md0
>
>/dev/md0:
>Timing buffer-cache reads: 3896 MB in 2.01 seconds = 1935.71 MB/sec
>Timing buffered disk reads: 274 MB in 3.02 seconds = 90.68 MB/sec
>root@t-rex root # hdparm -tT /dev/md1
>
>/dev/md1:
>Timing buffer-cache reads: 3760 MB in 2.00 seconds = 1879.35 MB/sec
>Timing buffered disk reads: 206 MB in 3.01 seconds = 68.49 MB/secc
>
>Copy a DVD to HD, both went OK!
>copy data from an ATA HD ( hda ) broke.
>
>I read from ppl they're running linux on some older hardware, maybe thats
>why it doesnt work... but ~25mb/s is nothing for me...
>Also I hear about some patches to limit the speed to ~30MB/s.


I was able to dd ~140 GB with SATA_SIL today, on a stock bk kernel, till
I ran out of disk, no errors. which was a pleasant unexpected surprise.

but when I checked "Timing buffered disk reads" it was around 25 MB/sec
not the ~52 MB/sec I saw before with the oops. The odd thing was this
disk was not in the blacklist so I don't know why it was running slower.

// George


--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:[email protected]
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631

2004-06-30 06:16:48

by Jeff Garzik

[permalink] [raw]
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops

George Georgalis wrote:
> I was able to dd ~140 GB with SATA_SIL today, on a stock bk kernel, till
> I ran out of disk, no errors. which was a pleasant unexpected surprise.
>
> but when I checked "Timing buffered disk reads" it was around 25 MB/sec
> not the ~52 MB/sec I saw before with the oops. The odd thing was this
> disk was not in the blacklist so I don't know why it was running slower.


Try mounting a filesystem, unmounting it, and then doing the timing.

Jeff