harddisk or kernel problem?

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* harddisk or kernel problem?
@ 2004-02-13  7:54 Nico Schottelius
  2004-02-13  8:11 ` Nico Schottelius
  2004-02-13 16:56 ` Alex Goller
  0 siblings, 2 replies; 19+ messages in thread
From: Nico Schottelius @ 2004-02-13  7:54 UTC (permalink / raw)
  To: linux-kernel

Hello!

Since yesterday I have the problem that at bootup my cryptoloop (/home) does not
get mounted anymore. These messages are produced by the kernel:

---------------- snip ------------------

Freeing unused kernel memory: 140k freed
XFS mounting filesystem hda1
Ending clean XFS mount for filesystem: hda1
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
("xfs_trans_read_buf") error 5 buf count 8192
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 at 0xd8850e00, 00:0a:e6:ba:f6:c2, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
("xfs_trans_read_buf") error 5 buf count 8192

---------------- snap ------------------

if I log in as root and issue `mount /home`, it works:

---------------- snip ------------------

XFS mounting filesystem loop0
Ending clean XFS mount for filesystem: loop0

---------------- snap ------------------

Yesterday the errors
 `hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }`
repeated (don't have the dmesg, forgot to dump kernel messages).

Now I am trying the following:
enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O
scheduler) and disabling Vector-based interrupt indexing.

This is just a guess, can someone tell me if that is senseless or if my
harddisk is most likely broken?

Attached dmesg from 'running' system and the new .config (changes see
above) I made.

Help is very much appreciated,

Nico, who just had a hard disk crash some weeks ago

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-13  7:54 harddisk or kernel problem? Nico Schottelius
@ 2004-02-13  8:11 ` Nico Schottelius
  2004-02-13  9:52   ` Nico Schottelius
  2004-02-13 16:56 ` Alex Goller
  1 sibling, 1 reply; 19+ messages in thread
From: Nico Schottelius @ 2004-02-13  8:11 UTC (permalink / raw)
  Cc: linux-kernel

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

forgot the config and the dmesg..

Nico

Nico Schottelius [Fri, Feb 13, 2004 at 08:54:03AM +0100]:
> Hello!
> 
> Since yesterday I have the problem that at bootup my cryptoloop (/home) does not
> get mounted anymore. These messages are produced by the kernel:
> 
> ---------------- snip ------------------
> 
> Freeing unused kernel memory: 140k freed
> XFS mounting filesystem hda1
> Ending clean XFS mount for filesystem: hda1
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
> sector=8305454
> end_request: I/O error, dev hda, sector 8305454
> I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
> ("xfs_trans_read_buf") error 5 buf count 8192
> 8139too Fast Ethernet driver 0.9.26
> eth0: RealTek RTL8139 at 0xd8850e00, 00:0a:e6:ba:f6:c2, IRQ 5
> eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
> sector=8305454
> end_request: I/O error, dev hda, sector 8305454
> I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
> ("xfs_trans_read_buf") error 5 buf count 8192
> 
> 
> ---------------- snap ------------------
> 
> 
> if I log in as root and issue `mount /home`, it works:
> 
> ---------------- snip ------------------
> 
> XFS mounting filesystem loop0
> Ending clean XFS mount for filesystem: loop0
> 
> ---------------- snap ------------------
> 
> Yesterday the errors
>  `hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }`
> repeated (don't have the dmesg, forgot to dump kernel messages).
> 
> Now I am trying the following:
> enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O
> scheduler) and disabling Vector-based interrupt indexing.
> 
> This is just a guess, can someone tell me if that is senseless or if my
> harddisk is most likely broken?
> 
> Attached dmesg from 'running' system and the new .config (changes see
> above) I made.
> 
> Help is very much appreciated,
> 
> Nico, who just had a hard disk crash some weeks ago

[-- Attachment #2: dmesg-scice --]
[-- Type: text/plain, Size: 10304 bytes --]

Linux version 2.6.2 (root@scice) (gcc version 3.3.3 20040125 (prerelease) (Debian)) #2 Mon Feb 9 00:46:37 CET 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 0000000000095c00 (usable)
 BIOS-e820: 0000000000095c00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000016ff0000 (usable)
 BIOS-e820: 0000000016ff0000 - 0000000016ff8000 (ACPI data)
 BIOS-e820: 0000000016ff8000 - 0000000017000000 (ACPI NVS)
 BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
367MB LOWMEM available.
On node 0 totalpages: 94192
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 90096 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 AMI                                       ) @ 0x000fad50
ACPI: RSDT (v001 AMIINT AMIINT09 0x00000011 MSFT 0x00000097) @ 0x16ff0000
ACPI: FADT (v001 AMIINT AMIINT09 0x00000011 MSFT 0x00000097) @ 0x16ff0030
ACPI: DSDT (v001 TM5600    TMx86 0x00001000 MSFT 0x0100000d) @ 0x00000000
Building zonelist for node : 0
Kernel command line: video=sisfb:mode:1024x768x16,rate:60 init=/sbin/minit
sisfb: Options mode:1024x768x16,rate:60
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 599.211 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Memory: 369216k/376768k available (2042k kernel code, 6728k reserved, 595k data, 140k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1101.82 BogoMIPS
Security Scaffold v1.0.0 initialized
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: 0084893f 0081813f 00000000 00000000
CPU:     After vendor identify, caps: 0084893f 0081813f 0000000e 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 512K (128 bytes/line)
CPU: Processor revision 1.3.2.1, 600 MHz
CPU: Code Morphing Software revision 4.2.7-8-278
CPU: 20011004 02:04 official release 4.2.7#7
CPU serial number disabled.
CPU:     After all inits, caps: 0080893f 0081813f 0000000e 00000000
CPU: Transmeta(tm) Crusoe(tm) Processor TM5600 stepping 03
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfda61, last bus=0
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040116
ACPI: IRQ4 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 14 15)
ACPI: PCI Interrupt Link [LNKP] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: No IRQ known for interrupt pin A of device 0000:00:10.0
ACPI: PCI Interrupt Link [LNKP] enabled at IRQ 10
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
sisfb: Video ROM found and mapped to c00c0000
sisfb: Framebuffer at 0xd0000000, mapped to 0xd780a000, size 16384k
sisfb: MMIO at 0xeffc0000, mapped to 0xd880b000, size 256k
sisfb: Memory heap starting at 8192K
sisfb: Using MMIO queue mode
sisfb: SiS301LV bridge detected (revision 0xd1)
sisfb: Default mode is 1024x768x16 (60Hz)
sisfb: Added MTRRs
sisfb: Installed SISFB_GET_INFO ioctl (80046ef8)
sisfb: 2D acceleration is enabled, scrolling mode ypan
fb0: SIS 315PRO frame buffer device, Version 1.6.01
devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
SGI XFS with ACLs, no debug enabled
Initializing Cryptographic API
Activating ISA DMA hang workarounds.
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID0]
ACPI: Processor [CPU1] (supports C1, 8 throttling states)
sisfb: Change mode to 1024x768x16-60Hz
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
Linux agpgart interface v0.100 (c) Dave Jones
[drm] Initialized sis 1.1.0 20030826 on minor 0
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller at PCI slot 0000:00:10.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:10.0
ALI15X3: chipset revision 196
ALI15X3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:pio
hda: FUJITSU MHS2030AT, ATA DISK drive
Using deadline io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: QSI CD-RW/DVD-ROM SBW-242, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 58605120 sectors (30005 MB) w/2048KiB Cache, CHS=58140/16/63, UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Console: switching to colour frame buffer device 128x48
mice: PS/2 mouse device common for all mice
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
Synaptics Touchpad, model: 1
 Firmware: 5.8
 Sensor: 29
 new absolute packet format
 Touchpad has extended capability bits
 -> 4 multi-buttons, i.e. besides standard buttons
 -> multifinger detection
 -> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
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
NET: Registered protocol family 15
cpufreq: No CPUs supporting ACPI performance management found.
ACPI: (supports S0 S1 S3 S4 S5)
XFS mounting filesystem hda3
Ending clean XFS mount for filesystem: hda3
VFS: Mounted root (xfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 140k freed
XFS mounting filesystem hda1
Ending clean XFS mount for filesystem: hda1
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458, sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090       ("xfs_trans_read_buf") error 5 buf count 8192
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 at 0xd8850e00, 00:0a:e6:ba:f6:c2, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458, sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090       ("xfs_trans_read_buf") error 5 buf count 8192
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ehci_hcd 0000:00:0a.2: EHCI Host Controller
ehci_hcd 0000:00:0a.2: irq 9, pci mem d88b9f00
ehci_hcd 0000:00:0a.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0a.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:14.0: OHCI Host Controller
ohci_hcd 0000:00:14.0: irq 10, pci mem d88bb000
ohci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci_hcd 0000:00:0a.0: UHCI Host Controller
uhci_hcd 0000:00:0a.0: irq 11, io base 0000de80
uhci_hcd 0000:00:0a.0: new USB bus registered, assigned bus number 3
hub 2-0:1.0: new USB device on port 1, assigned address 2
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:0a.1: UHCI Host Controller
prism2_init: prism2_usb.o: 0.2.1-pre16 Loaded
prism2_init: dev_info is: prism2_usb
drivers/usb/core/usb.c: registered new driver prism2_usb
uhci_hcd 0000:00:0a.1: irq 5, io base 0000df00
uhci_hcd 0000:00:0a.1: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.5.6
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/10
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0381660(lo)
IPv6 over IPv4 tunneling driver
spurious 8259A interrupt: IRQ7.
XFS mounting filesystem loop0
Ending clean XFS mount for filesystem: loop0
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

[-- Attachment #3: kernel-dmesg-stripped --]
[-- Type: text/plain, Size: 311 bytes --]

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458, sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090       ("xfs_trans_read_buf") error 5 buf count 8192


[-- Attachment #4: kernel-dot-config --]
[-- Type: text/plain, Size: 28234 bytes --]

#
# 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_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
CONFIG_EMBEDDED=y
# CONFIG_KALLSYMS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_IOSCHED_NOOP is not set
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# 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_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN 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 is not set
# 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=7
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_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC 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 is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_EDD=y
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

#
# 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=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
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_ACPI_RELAXED_AML is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM 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=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
# CONFIG_CPU_FREQ_24_API is not set
# CONFIG_CPU_FREQ_TABLE is not set

#
# CPUFreq processor drivers
#
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_LONGRUN=y

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

#
# 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 is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# 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=y

#
# 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_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
# 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_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE 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 is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# 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=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX 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 is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

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

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

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

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID 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_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS 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_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX 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 is not set

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

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
CONFIG_I2O=m
CONFIG_I2O_PCI=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m

#
# Networking support
#
CONFIG_NET=y

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

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_TUNNEL=m
# CONFIG_DECNET is not set
CONFIG_BRIDGE=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

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

#
# IPv6: Netfilter Configuration
#
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_LIMIT=m
CONFIG_IP6_NF_MATCH_MAC=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_MULTIPORT=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_MARK=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AHESP=m
CONFIG_IP6_NF_MATCH_LENGTH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_MARK=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q 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=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
# CONFIG_NET_CLS_POLICE is not set

#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
CONFIG_BONDING=m
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m

#
# 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=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET 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 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_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB 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

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

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL 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 is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD 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_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_UINPUT 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=m
# 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=m
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=m
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# 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=y
# 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_NVIDIA is not set
CONFIG_AGP_SIS=y
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA 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=y
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI15X3=m
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELV 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_PHILIPSPAR 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_VELLEMAN is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# I2C Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

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

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
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 is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
CONFIG_FB_SIS=y
# CONFIG_FB_SIS_300 is not set
CONFIG_FB_SIS_315=y
# 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 is not set
# 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 is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI 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_ALI5451=m
# CONFIG_SND_AZT3328 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_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_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# 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=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m

#
# 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=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE 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_XPAD is not set

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

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# 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_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_XFS_FS=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
CONFIG_XFS_POSIX_ACL=y
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m

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

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# 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_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# 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=m
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
# CONFIG_EXPORTFS is not set
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_INTERMEZZO_FS=m
CONFIG_AFS_FS=m
CONFIG_RXRPC=m

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

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# 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 is not set
# 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_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 is not set
# 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 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER 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=m
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set

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

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-13  8:11 ` Nico Schottelius
@ 2004-02-13  9:52   ` Nico Schottelius
  2004-02-13 16:17     ` Bartlomiej Zolnierkiewicz
  0 siblings, 1 reply; 19+ messages in thread
From: Nico Schottelius @ 2004-02-13  9:52 UTC (permalink / raw)
  To: linux-kernel

Nico Schottelius [Fri, Feb 13, 2004 at 09:11:04AM +0100]:
> forgot the config and the dmesg..
> 

Now additionally I found a mistake in my thoughts:

hda/part3 makes the errors, hda/part4 is the cryptoloop partition.
So in fact the error occurs when mounting this particular partition, but
seems to be an error on partition3. Can someone give me a hint on what
todo?

Sincerly,

Nico

ps: if somebody answers/answers me, please cc-me. Thanks.

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-13  9:52   ` Nico Schottelius
@ 2004-02-13 16:17     ` Bartlomiej Zolnierkiewicz
  2004-02-15 23:34       ` Nico Schottelius
  0 siblings, 1 reply; 19+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-13 16:17 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: linux-kernel

On Friday 13 of February 2004 10:52, Nico Schottelius wrote:
> Nico Schottelius [Fri, Feb 13, 2004 at 09:11:04AM +0100]:
> > forgot the config and the dmesg..
>
> Now additionally I found a mistake in my thoughts:
>
> hda/part3 makes the errors, hda/part4 is the cryptoloop partition.
> So in fact the error occurs when mounting this particular partition, but
> seems to be an error on partition3. Can someone give me a hint on what
> todo?

Check your disk with SMART tools: http://smartmontools.sf.net.


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-13 16:17     ` Bartlomiej Zolnierkiewicz
@ 2004-02-15 23:34       ` Nico Schottelius
  2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
  2004-02-18 13:30         ` Steve Bromwich
  0 siblings, 2 replies; 19+ messages in thread
From: Nico Schottelius @ 2004-02-15 23:34 UTC (permalink / raw)
  To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel

Bartlomiej Zolnierkiewicz [Fri, Feb 13, 2004 at 05:17:34PM +0100]:
> [ ... ]
> Check your disk with SMART tools: http://smartmontools.sf.net.

Before I continue to report what I've found out:

Thank you all for your good help!

I'm really down as this is the second disk
dyeing within two month (and the second 2.5" hd even, I begin to think
notebooks don't like me :/).

I currently collect all data I get / find out to 

http://schotteli.us/~nico/hd-problem.02/
(renamed it, as this does not look like a kernel problem and I don't
want somebody believe this).

Currently I don't really understand the output of smartctl and cannot
say what causes the error. Perhaps someone can give me a hint on this?

Greetings,

Nico

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-15 23:34       ` Nico Schottelius
@ 2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
  2004-02-18 16:55           ` Bruce Allen
  2004-02-18 13:30         ` Steve Bromwich
  1 sibling, 1 reply; 19+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-16  0:09 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: linux-kernel

On Monday 16 of February 2004 00:34, Nico Schottelius wrote:
> Bartlomiej Zolnierkiewicz [Fri, Feb 13, 2004 at 05:17:34PM +0100]:
> > [ ... ]
> > Check your disk with SMART tools: http://smartmontools.sf.net.
>
> Before I continue to report what I've found out:
>
> Thank you all for your good help!
>
> I'm really down as this is the second disk
> dyeing within two month (and the second 2.5" hd even, I begin to think
> notebooks don't like me :/).

:-(  sh*t happens

> I currently collect all data I get / find out to
>
> http://schotteli.us/~nico/hd-problem.02/
> (renamed it, as this does not look like a kernel problem and I don't
> want somebody believe this).
>
> Currently I don't really understand the output of smartctl and cannot
> say what causes the error. Perhaps someone can give me a hint on this?

The most important things are: READ DMA errors were logged,
SMART self tests (short and extended) completed with read failure.

For me this is 100% disk problem (not cable etc.).


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
@ 2004-02-18 16:55           ` Bruce Allen
  2004-02-19  8:01             ` Nico Schottelius
  0 siblings, 1 reply; 19+ messages in thread
From: Bruce Allen @ 2004-02-18 16:55 UTC (permalink / raw)
  To: Bartlomiej Zolnierkiewicz; +Cc: Nico Schottelius, linux-kernel

> On Monday 16 of February 2004 00:34, Nico Schottelius wrote:
> > Bartlomiej Zolnierkiewicz [Fri, Feb 13, 2004 at 05:17:34PM +0100]:
> > > [ ... ]
> > > Check your disk with SMART tools: http://smartmontools.sf.net.
> >
> > Before I continue to report what I've found out:
> >
> > Thank you all for your good help!
> >
> > I'm really down as this is the second disk
> > dyeing within two month (and the second 2.5" hd even, I begin to think
> > notebooks don't like me :/).
> 
> :-(  sh*t happens
> 
> > I currently collect all data I get / find out to
> >
> > http://schotteli.us/~nico/hd-problem.02/
> > (renamed it, as this does not look like a kernel problem and I don't
> > want somebody believe this).
> >
> > Currently I don't really understand the output of smartctl and cannot
> > say what causes the error. Perhaps someone can give me a hint on this?
> 
> The most important things are: READ DMA errors were logged,
> SMART self tests (short and extended) completed with read failure.

FWIW, after reading this thread, I've slightly modified smartmontools so
that when smartctl prints the error log (-l error) it ALSO prints the LBA
at which a READ or WRITE command failed.

[Note that this is a 28-bit sector address.  If a disk is larger than 2^37
Bytes = 137 GB, then some LBAs can't be written in 28 bits, in which case
there won't be a summary error log entry.  If the disk is smaller than
2^37 Bytes then the failing LBA address should always be logged.]

This feature is in smartmontools releases AFTER 5.27, or from the
smartmontools CVS server.

In the case of Nico's disk the failed READ LBA address can be computed
from the error log registers at
http://schotteli.us/~nico/hd-problem.02/smartctl-a:

  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 32 bb 7e e0  Error: UNC

yielding:

  LBA = 0x007ebb32 (bits 0-3 of DH, CH, CL and SN)

which can be compared with the LBA of the first error in the self-test
log:

# 1  Extended offline    Completed: read failure       90%      1633
0x007ebb32

and with the LBA logged in SYSLOG:
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
sector=8305454

Since 8305458 = 0x7EBB32 it's a pretty open and shut case.

****************************************************************

Executive summary: smartmontools versions > 5.27 will print this:

  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 32 bb 7e e0  Error: UNC at LBA = 0x007ebb32 = 8305458

rather than this:

  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 32 bb 7e e0  Error: UNC

Cheers,
	Bruce





^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-18 16:55           ` Bruce Allen
@ 2004-02-19  8:01             ` Nico Schottelius
  2004-02-20 16:25               ` Bruce Allen
  2004-03-02 20:07               ` Bruce Allen
  0 siblings, 2 replies; 19+ messages in thread
From: Nico Schottelius @ 2004-02-19  8:01 UTC (permalink / raw)
  To: Bruce Allen; +Cc: Bartlomiej Zolnierkiewicz, linux-kernel

Bruce Allen [Wed, Feb 18, 2004 at 10:55:05AM -0600]:
> [...] 
> FWIW, after reading this thread, I've slightly modified smartmontools so
> that when smartctl prints the error log (-l error) it ALSO prints the LBA
> at which a READ or WRITE command failed.

Thank you very much for patching smartctl and explaining howto calulate
the LBA from those values.

So at least my hd crash had some sense.

> [Note that this is a 28-bit sector address.  If a disk is larger than 2^37
> Bytes = 137 GB, then some LBAs can't be written in 28 bits, in which case
> there won't be a summary error log entry.  If the disk is smaller than
> 2^37 Bytes then the failing LBA address should always be logged.]

Why are we bound to a 28 bit value?
As there are currently more and more disks out there with >=260GB, I
think this will be an issue very soon.

Have a nice day,

Nico, currenty working with knoppix, a wonderful live Linux
                           (www.knopper.net/knoppix)


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-19  8:01             ` Nico Schottelius
@ 2004-02-20 16:25               ` Bruce Allen
  2004-03-02 20:07               ` Bruce Allen
  1 sibling, 0 replies; 19+ messages in thread
From: Bruce Allen @ 2004-02-20 16:25 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: Bartlomiej Zolnierkiewicz, linux-kernel

> > [...] 
> > FWIW, after reading this thread, I've slightly modified smartmontools
so
> > that when smartctl prints the error log (-l error) it ALSO prints the
LBA
> > at which a READ or WRITE command failed.
> 
> Thank you very much for patching smartctl and explaining howto calulate
> the LBA from those values.

You're welcome!

> So at least my hd crash had some sense.

Yes.  One of the 512-byte sectors became unreadable, so when the OS
asked for the data from that sector, the disk generated a hard error.

> > [Note that this is a 28-bit sector address.  If a disk is larger than
2^37
> > Bytes = 137 GB, then some LBAs can't be written in 28 bits, in which
case
> > there won't be a summary error log entry.  If the disk is smaller than
> > 2^37 Bytes then the failing LBA address should always be logged.]
> 
> Why are we bound to a 28 bit value?
> As there are currently more and more disks out there with >=260GB, I
> think this will be an issue very soon.

To quote from the ATA specifications:

"The summary error log supports 28-bit addressing only".

This summary error log is the error log currently printed by
smartmontools. In principle, for ATA 6 and 7, there are two additional
logs: 'Comprehensive SMART error' log and 'Extended Comprehensive
SMART error log'.  The 'Comprehensive SMART error log' is also 28-bit
addresses only.  The 'Extended' log also supports 48-bit addresses.

The '-l directory' option to smartctl will show what logs your disk
supports.

When I actually get my hands on a disk that supports the 'Extended'
log, I'll add code to smartmontools to print it.  However, at least up
to this point I have not seen a disk that supports it.  To cite one
example, a recent Maxtor 250 GB disk (manufacture date Jan 28, 2004)
 Device Model:     Maxtor 6Y250P0
 Serial Number:    Y60PYXBE
 Firmware Version: YAR41BW0
does NOT support the Extended error logs.

Once I find a disk that actually supports the logs, I need to use the
ATA READ LOG EXT command to get the logs.  In order to issue this
command under Linux, I need to use the .  HDIO_DRIVE_TASKFILE ioctl().
In my experience many distribution kernels (eg, Redhat) don't support
this ioctl(), so users may need to rebuilt their kernels in order to
be able to read the Extended error logs.

Cheers,
	Bruce

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-19  8:01             ` Nico Schottelius
  2004-02-20 16:25               ` Bruce Allen
@ 2004-03-02 20:07               ` Bruce Allen
  2004-03-02 23:12                 ` Nico Schottelius
  1 sibling, 1 reply; 19+ messages in thread
From: Bruce Allen @ 2004-03-02 20:07 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: Bartlomiej Zolnierkiewicz, Bruce Allen, linux-kernel

Nico,

> > [...] 
> > FWIW, after reading this thread, I've slightly modified smartmontools so
> > that when smartctl prints the error log (-l error) it ALSO prints the LBA
> > at which a READ or WRITE command failed.
> 
> Thank you very much for patching smartctl and explaining howto calulate
> the LBA from those values.

FWIW, I've just posted a short howto explaining how to identify the file
stored at the bad sector, and how to force sector reallocation at the bad
LBA.  This will effectively 'repair' the disk though you will lose the
data in that disk block.  Please see:

http://smartmontools.sourceforge.net/BadBlockHowTo.txt

Comments gratefully incorporated.

Cheers,
	Bruce


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-03-02 20:07               ` Bruce Allen
@ 2004-03-02 23:12                 ` Nico Schottelius
  0 siblings, 0 replies; 19+ messages in thread
From: Nico Schottelius @ 2004-03-02 23:12 UTC (permalink / raw)
  To: Bruce Allen; +Cc: Bartlomiej Zolnierkiewicz, linux-kernel

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

Bruce, 

thank you for the nice explanation! It's very easy to understand and
perhaps you should include this document into the next release of
smartmontools.

I think there might even be a need for a "Hard-Disk-Failure-Howto".
Anyone here wants to write it, has data for something like that?

Nico

-- 
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A          | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-15 23:34       ` Nico Schottelius
  2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
@ 2004-02-18 13:30         ` Steve Bromwich
  2004-02-18 14:12           ` Nico Schottelius
  2004-02-18 16:41           ` Bruce Allen
  1 sibling, 2 replies; 19+ messages in thread
From: Steve Bromwich @ 2004-02-18 13:30 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: linux-kernel

On Mon, 16 Feb 2004, Nico Schottelius wrote:

> Bartlomiej Zolnierkiewicz [Fri, Feb 13, 2004 at 05:17:34PM +0100]:
> I'm really down as this is the second disk
> dyeing within two month (and the second 2.5" hd even, I begin to think
> notebooks don't like me :/).
>
> I currently collect all data I get / find out to
>
> http://schotteli.us/~nico/hd-problem.02/

194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
-       48 (Lifetime Min/Max 14/65)

If I'm reading this correctly, you've been running the drive when it's
extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
either Fahrenheit or a raw unconverted reading from the thermistor). I
managed to completely hork a notebook drive after leaving my laptop in the
boot of my car for several hours (~-25C), taking it into a warm apartment
(~19C), booting it up and lifting the notebook off my lap sideways whilst
I shifted to get comfortable and putting it back on my lap. The hard drive
had a head crash (I think) on the sectors it was reading while I moved and
the partition was effectively toast - this was my Debian partition, and
wouldn't boot any more, but I could boot off the RedHat partition and
/home was (thankfully) still readable. I pulled all the data off in
preparation for the drive failing before I could get a new one (I was down
in Boston at the time), but the bad sectors slowly spread through the
entire drive over the course of a couple of days and I couldn't read any
data at all.

Lessons learned:

* Let laptops settle to room temperature after being exposed to sub-zero
temperatures for a while (this is probably in the manual, but I don't have
one)

* Laptop notebooks may be somewhat ruggedised but they still don't like
being moved when they're reading off the drive.

Running drives really hot is also a good way to toast them, too!

Cheers, Steve

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-18 13:30         ` Steve Bromwich
@ 2004-02-18 14:12           ` Nico Schottelius
  2004-02-18 16:41           ` Bruce Allen
  1 sibling, 0 replies; 19+ messages in thread
From: Nico Schottelius @ 2004-02-18 14:12 UTC (permalink / raw)
  To: Steve Bromwich; +Cc: linux-kernel

I didn't really see situation when the drive went from very cold
to room temperature, although you are right, smart says so.

Thank you for the tips. I talked to my vendor I he'll replace the disc, 
as it is just some months old.

Nico

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-18 13:30         ` Steve Bromwich
  2004-02-18 14:12           ` Nico Schottelius
@ 2004-02-18 16:41           ` Bruce Allen
  2004-02-19  0:06             ` Steve Bromwich
  1 sibling, 1 reply; 19+ messages in thread
From: Bruce Allen @ 2004-02-18 16:41 UTC (permalink / raw)
  To: Steve Bromwich; +Cc: Nico Schottelius, linux-kernel

> > I currently collect all data I get / find out to
> >
> > http://schotteli.us/~nico/hd-problem.02/
> 
> 194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
> -       48 (Lifetime Min/Max 14/65)
> 
> If I'm reading this correctly, you've been running the drive when it's
> extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
> either Fahrenheit or a raw unconverted reading from the thermistor).

Neither.  Fujitsu uses Celsuis: 14, 48, and 65 are all in Celsuis.



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-18 16:41           ` Bruce Allen
@ 2004-02-19  0:06             ` Steve Bromwich
  2004-02-19  8:16               ` Nico Schottelius
  0 siblings, 1 reply; 19+ messages in thread
From: Steve Bromwich @ 2004-02-19  0:06 UTC (permalink / raw)
  To: Bruce Allen; +Cc: Nico Schottelius, linux-kernel

On Wed, 18 Feb 2004, Bruce Allen wrote:

> > 194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
> > -       48 (Lifetime Min/Max 14/65)
> >
> > If I'm reading this correctly, you've been running the drive when it's
> > extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
> > either Fahrenheit or a raw unconverted reading from the thermistor).
>
> Neither.  Fujitsu uses Celsuis: 14, 48, and 65 are all in Celsuis.

Good grief... I'm not surprised the drive's dying, then! I've seen drives
lock up around 35C, I'm quite impressed the drive is still chugging along
(to some extent, at least) at 48C - and a max of 65C? Looking at a few of
Fujitsu's pages (eg,
http://www.fujitsu.ca/products/mobile_hdd/mht_ah/physical_specs.html),
ambient operating temperature is 5C to 55C - perhaps that's the cause of
the drive dying?

Just out of curiosity, Nico, what're you doing with these drives that
they're running so hot?

Cheers, Steve

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-19  0:06             ` Steve Bromwich
@ 2004-02-19  8:16               ` Nico Schottelius
  2004-02-20 17:10                 ` Frédéric L. W. Meunier
  0 siblings, 1 reply; 19+ messages in thread
From: Nico Schottelius @ 2004-02-19  8:16 UTC (permalink / raw)
  To: Steve Bromwich; +Cc: Bruce Allen, linux-kernel

Steve Bromwich [Wed, Feb 18, 2004 at 08:06:47PM -0400]:
> On Wed, 18 Feb 2004, Bruce Allen wrote:
> 
> > > 194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
> > > -       48 (Lifetime Min/Max 14/65)
> > >
> > > If I'm reading this correctly, you've been running the drive when it's
> > > extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
> > > either Fahrenheit or a raw unconverted reading from the thermistor).
> >
> > Neither.  Fujitsu uses Celsuis: 14, 48, and 65 are all in Celsuis.
> 
> Good grief... I'm not surprised the drive's dying, then! I've seen drives
> lock up around 35C, I'm quite impressed the drive is still chugging along
> (to some extent, at least) at 48C - and a max of 65C? Looking at a few of
> Fujitsu's pages (eg,
> http://www.fujitsu.ca/products/mobile_hdd/mht_ah/physical_specs.html),
> ambient operating temperature is 5C to 55C - perhaps that's the cause of
> the drive dying?
> 
> Just out of curiosity, Nico, what're you doing with these drives that
> they're running so hot?

You won't believe it.
It ran in a standard ECS Elitebook A530 Notebook. 
I always waited some time (30 Minutes up to some hours), when it was
cold outside.
I am working with this laptop about 10-20 hours a day, it runs several
compile runs, etc.

Mostly the same things I did on my Acer Travelmate..well this hard disk
died, too..

Well, currently I am wondering why two disks died, too.

Sincerly,

Nico

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-19  8:16               ` Nico Schottelius
@ 2004-02-20 17:10                 ` Frédéric L. W. Meunier
  2004-02-20 22:37                   ` Eric D. Mudama
  0 siblings, 1 reply; 19+ messages in thread
From: Frédéric L. W. Meunier @ 2004-02-20 17:10 UTC (permalink / raw)
  To: Nico Schottelius; +Cc: Bruce Allen, linux-kernel

On Thu, 19 Feb 2004, Nico Schottelius wrote:

> Steve Bromwich [Wed, Feb 18, 2004 at 08:06:47PM -0400]:
> > On Wed, 18 Feb 2004, Bruce Allen wrote:
> >
> > > > 194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
> > > > -       48 (Lifetime Min/Max 14/65)
> > > >
> > > > If I'm reading this correctly, you've been running the drive when it's
> > > > extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
> > > > either Fahrenheit or a raw unconverted reading from the thermistor).
> > >
> > > Neither.  Fujitsu uses Celsuis: 14, 48, and 65 are all in Celsuis.
> >
> > Good grief... I'm not surprised the drive's dying, then! I've seen drives
> > lock up around 35C, I'm quite impressed the drive is still chugging along
> > (to some extent, at least) at 48C - and a max of 65C? Looking at a few of
> > Fujitsu's pages (eg,
> > http://www.fujitsu.ca/products/mobile_hdd/mht_ah/physical_specs.html),
> > ambient operating temperature is 5C to 55C - perhaps that's the cause of
> > the drive dying?
> >
> > Just out of curiosity, Nico, what're you doing with these drives that
> > they're running so hot?
>
> You won't believe it.
> It ran in a standard ECS Elitebook A530 Notebook.
> I always waited some time (30 Minutes up to some hours), when it was
> cold outside.
> I am working with this laptop about 10-20 hours a day, it runs several
> compile runs, etc.

It isn't that hot, and by ambient temperature I assume it's the
local temperature, not of the hard drive.

194 Temperature_Celsius     0x0022   079   074   042    Old_age   Always       -       54

and has been running almost fine for over 2 years.

-- 
http://www.pervalidus.net/contact.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-20 17:10                 ` Frédéric L. W. Meunier
@ 2004-02-20 22:37                   ` Eric D. Mudama
  0 siblings, 0 replies; 19+ messages in thread
From: Eric D. Mudama @ 2004-02-20 22:37 UTC (permalink / raw)
  To: Frédéric L. W. Meunier
  Cc: Nico Schottelius, Bruce Allen, linux-kernel

On Fri, Feb 20 at 14:10, Frédéric L. W. Meunier wrote:
>It isn't that hot, and by ambient temperature I assume it's the
>local temperature, not of the hard drive.
>
>194 Temperature_Celsius     0x0022   079   074   042    Old_age   Always       -       54
>
>and has been running almost fine for over 2 years.

The SMART data is the temperature recorded by the drive itself.  There
are various places where these measurements may be made, the actual
implementation is vendor specific.

An ambient temperature exceeding 55C would void most drive warranties,
it isn't a good idea.  Sure, your drive may survive at higher temps,
but it really is a bad idea.

-- 
Eric D. Mudama
edmudama@mail.bounceswoosh.org

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: harddisk or kernel problem?
  2004-02-13  7:54 harddisk or kernel problem? Nico Schottelius
  2004-02-13  8:11 ` Nico Schottelius
@ 2004-02-13 16:56 ` Alex Goller
  1 sibling, 0 replies; 19+ messages in thread
From: Alex Goller @ 2004-02-13 16:56 UTC (permalink / raw)
  To: Nico Schottelius

On Fri, Feb 13, 2004 at 08:54:03AM +0100, Nico Schottelius wrote:
> Freeing unused kernel memory: 140k freed
> XFS mounting filesystem hda1
> Ending clean XFS mount for filesystem: hda1
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
> sector=8305454

These result from the ide/dma code. Those errors are normally thrown
(someone correct me if i'm wrong) if ecc on that particular sector
fails. A EIO error is thrown, and is handed over to the layer above
(xfs in your case). These errors happen as well if you do raw reads
on those sectors.

> end_request: I/O error, dev hda, sector 8305454
> I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090

This is EIO handed over to xfs.

> Now I am trying the following:
> enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O
> scheduler) and disabling Vector-based interrupt indexing.

I don't think this will help. The proplem is probably all about a
broken sector on your disk. And if i understand the ide code correctly
you can't do anything about that.

> This is just a guess, can someone tell me if that is senseless or if my
> harddisk is most likely broken?

Yes, that's the most likely case. Smartmontools (smartctl) should show
errors on the sectors mentioned in your dumps as well (they do here).

Error 1689 occurred at disk power-on lifetime: 703 hours
  When the command that caused the error occurred, the device was active or idle

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 2c 46 58 e0  Error: UNC

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  25 00 30 23 46 58 e0 00    3864.401  READ DMA EXT
  25 00 32 21 46 58 e0 00    3860.425  READ DMA EXT
  25 00 34 1f 46 58 e0 00    3843.845  READ DMA EXT
  25 00 36 1d 46 58 e0 00    3839.939  READ DMA EXT
  25 00 38 1b 46 58 e0 00    3839.914  READ DMA EXT

And so on.

bye, alex
-- 
alexander goller		alex@vivien.franken.de

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2004-03-02 23:11 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-13  7:54 harddisk or kernel problem? Nico Schottelius
2004-02-13  8:11 ` Nico Schottelius
2004-02-13  9:52   ` Nico Schottelius
2004-02-13 16:17     ` Bartlomiej Zolnierkiewicz
2004-02-15 23:34       ` Nico Schottelius
2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
2004-02-18 16:55           ` Bruce Allen
2004-02-19  8:01             ` Nico Schottelius
2004-02-20 16:25               ` Bruce Allen
2004-03-02 20:07               ` Bruce Allen
2004-03-02 23:12                 ` Nico Schottelius
2004-02-18 13:30         ` Steve Bromwich
2004-02-18 14:12           ` Nico Schottelius
2004-02-18 16:41           ` Bruce Allen
2004-02-19  0:06             ` Steve Bromwich
2004-02-19  8:16               ` Nico Schottelius
2004-02-20 17:10                 ` Frédéric L. W. Meunier
2004-02-20 22:37                   ` Eric D. Mudama
2004-02-13 16:56 ` Alex Goller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox