* Ibm Serveraid Problem with 2.4.25
@ 2004-02-26 9:12 Jo Christian Buvarp
2004-02-26 23:48 ` Enrico Demarin
0 siblings, 1 reply; 19+ messages in thread
From: Jo Christian Buvarp @ 2004-02-26 9:12 UTC (permalink / raw)
To: linux-kernel
Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
The server is an IBM 345 with a Serveraid 5I controller, when doing an
dmesg i get this error:
attempt to access beyond end of device
08:05: rw=0, want=528036, limit=528034
attempt to access beyond end of device
08:09: rw=0, want=65208120, limit=65208118
This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
looks fine :)
I tried upgrading the serveraid bios to the newest version (6.11.07),
but i still got the error.
So is this an bug in the kernel? Or do I have a problem on my server ?
Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
--
--------------------------------------------------------------
Med vennlig hilsen/Yours sincerely
Jo Christian Buvarp
Teknisk Leder
Svorka Aksess AS
Notice:
This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review or distribution by others
is strictly prohibited. If this e-mail is received by others than the
intended recipient, please contact the sender and delete all copies.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-26 9:12 Ibm Serveraid Problem with 2.4.25 Jo Christian Buvarp
@ 2004-02-26 23:48 ` Enrico Demarin
2004-02-27 1:48 ` Enrico Demarin
0 siblings, 1 reply; 19+ messages in thread
From: Enrico Demarin @ 2004-02-26 23:48 UTC (permalink / raw)
To: Jo Christian Buvarp; +Cc: linux-kernel
I have the same here using the "partially opensource" drivers for a
Promise TX2... no message on 2.4.24.I wonder if it also means it's
corrupting the FS ? :(
- Enrico
On Thu, 2004-02-26 at 04:12, Jo Christian Buvarp wrote:
> Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
> The server is an IBM 345 with a Serveraid 5I controller, when doing an
> dmesg i get this error:
>
> attempt to access beyond end of device
> 08:05: rw=0, want=528036, limit=528034
> attempt to access beyond end of device
> 08:09: rw=0, want=65208120, limit=65208118
>
> This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
> looks fine :)
> I tried upgrading the serveraid bios to the newest version (6.11.07),
> but i still got the error.
>
> So is this an bug in the kernel? Or do I have a problem on my server ?
> Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-26 23:48 ` Enrico Demarin
@ 2004-02-27 1:48 ` Enrico Demarin
2004-02-27 3:14 ` Marcelo Tosatti
0 siblings, 1 reply; 19+ messages in thread
From: Enrico Demarin @ 2004-02-27 1:48 UTC (permalink / raw)
To: Jo Christian Buvarp; +Cc: linux-kernel
Hi everyone,
I just checked, same message on a IBM x235 , it uses the
Fusion MPT SCSI Host driver 2.05.11.03
driver.
Same message as you ( except the offsets vary ) when I reboot.
- Enrico
On Thu, 2004-02-26 at 18:48, Enrico Demarin wrote:
> I have the same here using the "partially opensource" drivers for a
> Promise TX2... no message on 2.4.24.I wonder if it also means it's
> corrupting the FS ? :(
>
>
> - Enrico
>
> On Thu, 2004-02-26 at 04:12, Jo Christian Buvarp wrote:
> > Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
> > The server is an IBM 345 with a Serveraid 5I controller, when doing an
> > dmesg i get this error:
> >
> > attempt to access beyond end of device
> > 08:05: rw=0, want=528036, limit=528034
> > attempt to access beyond end of device
> > 08:09: rw=0, want=65208120, limit=65208118
> >
> > This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
> > looks fine :)
> > I tried upgrading the serveraid bios to the newest version (6.11.07),
> > but i still got the error.
> >
> > So is this an bug in the kernel? Or do I have a problem on my server ?
> > Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-27 1:48 ` Enrico Demarin
@ 2004-02-27 3:14 ` Marcelo Tosatti
2004-02-27 2:37 ` Enrico Demarin
2004-02-27 7:16 ` Jo Christian Buvarp
0 siblings, 2 replies; 19+ messages in thread
From: Marcelo Tosatti @ 2004-02-27 3:14 UTC (permalink / raw)
To: Enrico Demarin
Cc: Jo Christian Buvarp, linux-kernel, Moore, Eric Dean,
Andrew Morton
Jo,
You're also using the MPT Fusion driver?
It has been updated in 2.4.25, and probably something broke. DAMN.
Eric, please look into this for us ?
On Thu, 26 Feb 2004, Enrico Demarin wrote:
> Hi everyone,
>
> I just checked, same message on a IBM x235 , it uses the
>
> Fusion MPT SCSI Host driver 2.05.11.03
>
> driver.
>
> Same message as you ( except the offsets vary ) when I reboot.
>
> - Enrico
>
> On Thu, 2004-02-26 at 18:48, Enrico Demarin wrote:
> > I have the same here using the "partially opensource" drivers for a
> > Promise TX2... no message on 2.4.24.I wonder if it also means it's
> > corrupting the FS ? :(
> >
> >
> > - Enrico
> >
> > On Thu, 2004-02-26 at 04:12, Jo Christian Buvarp wrote:
> > > Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
> > > The server is an IBM 345 with a Serveraid 5I controller, when doing an
> > > dmesg i get this error:
> > >
> > > attempt to access beyond end of device
> > > 08:05: rw=0, want=528036, limit=528034
> > > attempt to access beyond end of device
> > > 08:09: rw=0, want=65208120, limit=65208118
> > >
> > > This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
> > > looks fine :)
> > > I tried upgrading the serveraid bios to the newest version (6.11.07),
> > > but i still got the error.
> > >
> > > So is this an bug in the kernel? Or do I have a problem on my server ?
> > > Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-27 3:14 ` Marcelo Tosatti
@ 2004-02-27 2:37 ` Enrico Demarin
2004-02-27 7:16 ` Jo Christian Buvarp
1 sibling, 0 replies; 19+ messages in thread
From: Enrico Demarin @ 2004-02-27 2:37 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: linux-kernel
Hi Marcelo,
I suspect it's not the MPT fusion driver itself, because I get
the same message on another IBM ( x205 ) which has a Promise TX2
controller ( ATA raid ) .
I am using the Promise driver in that case, and I get the same error on
reboot ( although the MPT driver is compiled in, this machine doesn't
have an MPT controller )
Right now i only have remote access to that machine but I can try
tomorrow morning to compile without MPT and see if it makes a
difference.
- Enrico
Here is the configuration file for the x205 in question :
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_LOLAT is not set
# CONFIG_LOLAT_SYSCTL 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_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# 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_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_HAS_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_F00F_WORKS_OK=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_TSC_DISABLE is not set
CONFIG_X86_TSC=y
#
# General setup
#
CONFIG_NET=y
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_ISA=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_OOM_KILLER is not set
# CONFIG_PM is not set
# CONFIG_APM is not set
#
# ACPI Support
#
# CONFIG_ACPI 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_PC_PCMCIA is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_IP22 is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set
#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_CISS_MONITOR_THREAD 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_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_STATS is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
# CONFIG_IP_ROUTE_FWMARK is not set
# CONFIG_IP_ROUTE_NAT is not set
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# 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=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_H323=m
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_TFTP is not set
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_CT_PROTO_GRE=m
CONFIG_IP_NF_PPTP=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=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_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=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_NAT_H323=m
CONFIG_IP_NF_NAT_PPTP=m
CONFIG_IP_NF_NAT_PROTO_GRE=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=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_LOG=m
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
#
#
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC 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_CSZ=y
# CONFIG_NET_SCH_HFSC 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=y
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=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set
#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
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_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS 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
#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_GENERIC is not set
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_ADMA100 is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE 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_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
CONFIG_BLK_DEV_RZ1000=y
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_SVWKS=y
# 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_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set
#
# SCSI support
#
CONFIG_SCSI=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
# 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 is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_MEGARAID2 is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA 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_GENERIC_NCR5380 is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS 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_SEAGATE is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_BOOT=y
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_ISENSE=m
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_NET_FC=y
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
CONFIG_EL3=m
# CONFIG_3C515 is not set
# CONFIG_ELMC is not set
# CONFIG_ELMC_II is not set
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=m
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_CS89x0 is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
CONFIG_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# 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_SUNDANCE_MMIO is not set
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
# CONFIG_MYRI_SBUS 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=m
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE 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=y
# CONFIG_IPHASE5526 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
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_UINPUT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_EXTENDED=y
CONFIG_SERIAL_MANY_PORTS=y
CONFIG_SERIAL_SHARE_IRQ=y
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_PROC=m
#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
# CONFIG_MK712_MOUSE is not set
#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
#
# Input core support is needed for gameports
#
#
# Input core support is needed for joysticks
#
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_SCx200 is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_RNG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_AMD_PM768 is not set
# 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 is not set
#
# Direct Rendering Manager (XFree86 DRI support)
#
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_OBMOUSE is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW 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_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
CONFIG_CRAMFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_XFS_FS is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_TRACE is not set
# CONFIG_XFS_DEBUG is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_NFS_FS is not set
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
# CONFIG_SUNRPC is not set
# CONFIG_LOCKD is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y
#
# Native Language Support
#
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=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 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
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set
#
# Frame-buffer support
#
# CONFIG_FB is not set
#
# Sound
#
# CONFIG_SOUND 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
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_UHCI=m
CONFIG_USB_UHCI_ALT=m
CONFIG_USB_OHCI=m
# CONFIG_USB_SL811HS_ALT is not set
# CONFIG_USB_SL811HS is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_EMI26 is not set
CONFIG_USB_BLUETOOTH=m
# CONFIG_USB_MIDI is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG 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
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
#
# Input core support is needed for USB HID input layer or HIDBP
support
#
# CONFIG_USB_HIDINPUT is not set
CONFIG_USB_HIDDEV=y
# 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
#
# USB Imaging devices
#
# CONFIG_USB_DC2XX is not set
# 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
#
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER 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_RIO500 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
#
# Support for USB gadgets
#
# CONFIG_USB_GADGET is not set
#
# Bluetooth support
#
# CONFIG_BLUEZ is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_HIGHMEM 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_FRAME_POINTER is not set
CONFIG_LOG_BUF_SHIFT=0
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
On Thu, 2004-02-26 at 22:14, Marcelo Tosatti wrote:
> Jo,
>
> You're also using the MPT Fusion driver?
>
> It has been updated in 2.4.25, and probably something broke. DAMN.
>
> Eric, please look into this for us ?
>
> On Thu, 26 Feb 2004, Enrico Demarin wrote:
>
> > Hi everyone,
> >
> > I just checked, same message on a IBM x235 , it uses the
> >
> > Fusion MPT SCSI Host driver 2.05.11.03
> >
> > driver.
> >
> > Same message as you ( except the offsets vary ) when I reboot.
> >
> > - Enrico
> >
> > On Thu, 2004-02-26 at 18:48, Enrico Demarin wrote:
> > > I have the same here using the "partially opensource" drivers for a
> > > Promise TX2... no message on 2.4.24.I wonder if it also means it's
> > > corrupting the FS ? :(
> > >
> > >
> > > - Enrico
> > >
> > > On Thu, 2004-02-26 at 04:12, Jo Christian Buvarp wrote:
> > > > Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
> > > > The server is an IBM 345 with a Serveraid 5I controller, when doing an
> > > > dmesg i get this error:
> > > >
> > > > attempt to access beyond end of device
> > > > 08:05: rw=0, want=528036, limit=528034
> > > > attempt to access beyond end of device
> > > > 08:09: rw=0, want=65208120, limit=65208118
> > > >
> > > > This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
> > > > looks fine :)
> > > > I tried upgrading the serveraid bios to the newest version (6.11.07),
> > > > but i still got the error.
> > > >
> > > > So is this an bug in the kernel? Or do I have a problem on my server ?
> > > > Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-27 3:14 ` Marcelo Tosatti
2004-02-27 2:37 ` Enrico Demarin
@ 2004-02-27 7:16 ` Jo Christian Buvarp
2004-02-27 14:36 ` Marcelo Tosatti
1 sibling, 1 reply; 19+ messages in thread
From: Jo Christian Buvarp @ 2004-02-27 7:16 UTC (permalink / raw)
To: Marcelo Tosatti
Cc: Enrico Demarin, linux-kernel, Moore, Eric Dean, Andrew Morton
No, I only got IBM ServeRAID support
--------------------------------------------------------------
Med vennlig hilsen/Yours sincerely
Jo Christian Buvarp
Teknisk Leder
Svorka Aksess AS
Notice:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If this e-mail is received by others than the intended recipient, please contact the sender and delete all copies.
Marcelo Tosatti wrote:
>Jo,
>
>You're also using the MPT Fusion driver?
>
>It has been updated in 2.4.25, and probably something broke. DAMN.
>
>Eric, please look into this for us ?
>
>On Thu, 26 Feb 2004, Enrico Demarin wrote:
>
>
>
>>Hi everyone,
>>
>>I just checked, same message on a IBM x235 , it uses the
>>
>>Fusion MPT SCSI Host driver 2.05.11.03
>>
>>driver.
>>
>>Same message as you ( except the offsets vary ) when I reboot.
>>
>>- Enrico
>>
>>On Thu, 2004-02-26 at 18:48, Enrico Demarin wrote:
>>
>>
>>>I have the same here using the "partially opensource" drivers for a
>>>Promise TX2... no message on 2.4.24.I wonder if it also means it's
>>>corrupting the FS ? :(
>>>
>>>
>>>- Enrico
>>>
>>>On Thu, 2004-02-26 at 04:12, Jo Christian Buvarp wrote:
>>>
>>>
>>>>Just upgraded my server with the 2.4.25 kernel and I noticed an error :/
>>>>The server is an IBM 345 with a Serveraid 5I controller, when doing an
>>>>dmesg i get this error:
>>>>
>>>>attempt to access beyond end of device
>>>>08:05: rw=0, want=528036, limit=528034
>>>>attempt to access beyond end of device
>>>>08:09: rw=0, want=65208120, limit=65208118
>>>>
>>>>This error only shows up in 2.4.25, when rebooting to 2.4.24 everything
>>>>looks fine :)
>>>>I tried upgrading the serveraid bios to the newest version (6.11.07),
>>>>but i still got the error.
>>>>
>>>>So is this an bug in the kernel? Or do I have a problem on my server ?
>>>>Is it safe to run 2.4.25 with this error ? Or should i go back to 2.4.24
>>>>
>>>>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-27 7:16 ` Jo Christian Buvarp
@ 2004-02-27 14:36 ` Marcelo Tosatti
2004-03-01 2:10 ` Alain Fauconnet
0 siblings, 1 reply; 19+ messages in thread
From: Marcelo Tosatti @ 2004-02-27 14:36 UTC (permalink / raw)
To: Jo Christian Buvarp; +Cc: Enrico Demarin, Moore, Eric Dean, linux-kernel
On Fri, 27 Feb 2004, Jo Christian Buvarp wrote:
> No, I only got IBM ServeRAID support
Eric, my mistake. Nevermind it :)
Jo, Enrico,
The error is harmless, although it is a bug.
I suspect the ext2 2.6 compat updates on 2.4.25 might be causing this.
I'll send you a patch privately to revert those and confirm (or not).
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-02-27 14:36 ` Marcelo Tosatti
@ 2004-03-01 2:10 ` Alain Fauconnet
2004-03-01 3:10 ` Enrico Demarin
2004-03-01 15:51 ` Marcelo Tosatti
0 siblings, 2 replies; 19+ messages in thread
From: Alain Fauconnet @ 2004-03-01 2:10 UTC (permalink / raw)
To: Marcelo Tosatti
Cc: Jo Christian Buvarp, Enrico Demarin, Moore, Eric Dean,
linux-kernel
On Fri, Feb 27, 2004 at 11:36:51AM -0300, Marcelo Tosatti wrote:
>
>
> On Fri, 27 Feb 2004, Jo Christian Buvarp wrote:
>
> > No, I only got IBM ServeRAID support
>
> Eric, my mistake. Nevermind it :)
>
> Jo, Enrico,
>
> The error is harmless, although it is a bug.
>
> I suspect the ext2 2.6 compat updates on 2.4.25 might be causing this.
> I'll send you a patch privately to revert those and confirm (or not).
>
Folks,
Please followup to the list when you've drawn conclusions about this
issue.
I'm holding a 2.4.25 upgrade of a busy mail server because of this.
Greets,
_Alain_
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 2:10 ` Alain Fauconnet
@ 2004-03-01 3:10 ` Enrico Demarin
2004-03-01 3:30 ` Alain Fauconnet
2004-03-01 15:51 ` Marcelo Tosatti
1 sibling, 1 reply; 19+ messages in thread
From: Enrico Demarin @ 2004-03-01 3:10 UTC (permalink / raw)
To: Alain Fauconnet
Cc: Marcelo Tosatti, Jo Christian Buvarp, Moore, Eric Dean,
linux-kernel
Alain,
so far Jo went through all the pre2.4.24 and 25 and the bug appeared
in 2.4.24pre1.
- Enrico
On Sun, 2004-02-29 at 21:10, Alain Fauconnet wrote:
> On Fri, Feb 27, 2004 at 11:36:51AM -0300, Marcelo Tosatti wrote:
> >
> >
> > On Fri, 27 Feb 2004, Jo Christian Buvarp wrote:
> >
> > > No, I only got IBM ServeRAID support
> >
> > Eric, my mistake. Nevermind it :)
> >
> > Jo, Enrico,
> >
> > The error is harmless, although it is a bug.
> >
> > I suspect the ext2 2.6 compat updates on 2.4.25 might be causing this.
> > I'll send you a patch privately to revert those and confirm (or not).
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 3:10 ` Enrico Demarin
@ 2004-03-01 3:30 ` Alain Fauconnet
2004-03-01 15:01 ` Enrico Demarin
0 siblings, 1 reply; 19+ messages in thread
From: Alain Fauconnet @ 2004-03-01 3:30 UTC (permalink / raw)
To: Enrico Demarin
Cc: Marcelo Tosatti, Jo Christian Buvarp, Moore, Eric Dean,
linux-kernel
Enrico,
Thanks for the update, but...
On Sun, Feb 29, 2004 at 10:10:30PM -0500, Enrico Demarin wrote:
> Alain,
>
> so far Jo went through all the pre2.4.24 and 25 and the bug appeared
> in 2.4.24pre1.
Are you meaning that the bug was already present in the 2.4.24
release? I'm a bit confused here.
>
> - Enrico
>
>
> On Sun, 2004-02-29 at 21:10, Alain Fauconnet wrote:
> > On Fri, Feb 27, 2004 at 11:36:51AM -0300, Marcelo Tosatti wrote:
> > >
> > >
> > > On Fri, 27 Feb 2004, Jo Christian Buvarp wrote:
> > >
> > > > No, I only got IBM ServeRAID support
> > >
> > > Eric, my mistake. Nevermind it :)
> > >
> > > Jo, Enrico,
> > >
> > > The error is harmless, although it is a bug.
> > >
> > > I suspect the ext2 2.6 compat updates on 2.4.25 might be causing this.
> > > I'll send you a patch privately to revert those and confirm (or not).
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 3:30 ` Alain Fauconnet
@ 2004-03-01 15:01 ` Enrico Demarin
0 siblings, 0 replies; 19+ messages in thread
From: Enrico Demarin @ 2004-03-01 15:01 UTC (permalink / raw)
To: Alain Fauconnet; +Cc: linux-kernel
Alain , I am pasting you an email i got from Marcelo Tosatti, which I
think clarifies pretty well the history of 2.4.24 and 2.4.25 :
-- snip --
2.4.24 was under development (had -pre1, -pre2 and -pre3 released).
At that point, we had to release 2.4.24 without the "-pre" changes (only
with the security fixes).
So basically 2.4.24-pre was renamed to 2.4.25-pre, and 2.4.25-pre4 was
released.
-- snip --
- Enrico
On Sun, 2004-02-29 at 22:30, Alain Fauconnet wrote:
> Enrico,
>
> Thanks for the update, but...
>
> On Sun, Feb 29, 2004 at 10:10:30PM -0500, Enrico Demarin wrote:
> > Alain,
> >
> > so far Jo went through all the pre2.4.24 and 25 and the bug appeared
> > in 2.4.24pre1.
>
> Are you meaning that the bug was already present in the 2.4.24
> release? I'm a bit confused here.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 2:10 ` Alain Fauconnet
2004-03-01 3:10 ` Enrico Demarin
@ 2004-03-01 15:51 ` Marcelo Tosatti
2004-03-01 17:24 ` Chuck Lever
1 sibling, 1 reply; 19+ messages in thread
From: Marcelo Tosatti @ 2004-03-01 15:51 UTC (permalink / raw)
To: Alain Fauconnet; +Cc: Jo Christian Buvarp, Enrico Demarin, linux-kernel, cel
On Mon, 1 Mar 2004, Alain Fauconnet wrote:
> Please followup to the list when you've drawn conclusions about this
> issue.
> I'm holding a 2.4.25 upgrade of a busy mail server because of this.
We found out the guilty part, its the readahead modifications done by
Chuck Lever in -pre1.
The error is harmless though, you can safely move your server to 2.4.25.
Its just trying to readahead a page beyond the end device.
The following untested patch on top of 2.4.25 should fix it:
--- mm/filemap.c.orig 2004-03-01 12:47:41.000000000 -0300
+++ mm/filemap.c 2004-03-01 12:48:30.000000000 -0300
@@ -1346,7 +1346,7 @@
while (ahead < max_ahead) {
unsigned long ra_index = raend + ahead + 1;
- if (ra_index > end_index)
+ if (ra_index >= end_index)
break;
if (page_cache_read(filp, ra_index) < 0)
break;
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 15:51 ` Marcelo Tosatti
@ 2004-03-01 17:24 ` Chuck Lever
2004-03-01 18:23 ` Marcelo Tosatti
0 siblings, 1 reply; 19+ messages in thread
From: Chuck Lever @ 2004-03-01 17:24 UTC (permalink / raw)
To: Marcelo Tosatti
Cc: Alain Fauconnet, Jo Christian Buvarp, Enrico Demarin,
linux-kernel
hi marcelo-
your "fix" will break readahead again for NFS. with the ">=" as you
propose, the read ahead code will never be able to read the last page of
the file as a coalesced read, it will always be a separate 4KB read.
the problem is not the readahead code, it is the driver code that tries
to read beyond the end of the device. my change merely exposed this
misbehavior.
so there is a broken assumption somewhere about how the index of the last
page of a file/device is computed. i think it is a problem when the file
ends exactly on a page boundary.
alain, if you don't use the NFS client, marcelo's fix should work just
fine for you. but i believe that in general it is incorrect.
On Mon, 1 Mar 2004, Marcelo Tosatti wrote:
>
> On Mon, 1 Mar 2004, Alain Fauconnet wrote:
>
> > Please followup to the list when you've drawn conclusions about this
> > issue.
> > I'm holding a 2.4.25 upgrade of a busy mail server because of this.
>
> We found out the guilty part, its the readahead modifications done by
> Chuck Lever in -pre1.
>
> The error is harmless though, you can safely move your server to 2.4.25.
> Its just trying to readahead a page beyond the end device.
>
> The following untested patch on top of 2.4.25 should fix it:
>
> --- mm/filemap.c.orig 2004-03-01 12:47:41.000000000 -0300
> +++ mm/filemap.c 2004-03-01 12:48:30.000000000 -0300
> @@ -1346,7 +1346,7 @@
> while (ahead < max_ahead) {
> unsigned long ra_index = raend + ahead + 1;
>
> - if (ra_index > end_index)
> + if (ra_index >= end_index)
> break;
> if (page_cache_read(filp, ra_index) < 0)
> break;
>
>
- Chuck Lever
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 17:24 ` Chuck Lever
@ 2004-03-01 18:23 ` Marcelo Tosatti
2004-03-01 18:39 ` Chuck Lever
2004-03-01 18:41 ` Enrico Demarin
0 siblings, 2 replies; 19+ messages in thread
From: Marcelo Tosatti @ 2004-03-01 18:23 UTC (permalink / raw)
To: Chuck Lever; +Cc: linux-kernel
On Mon, 1 Mar 2004, Chuck Lever wrote:
> hi marcelo-
>
> your "fix" will break readahead again for NFS. with the ">=" as you
> propose, the read ahead code will never be able to read the last page of
> the file as a coalesced read, it will always be a separate 4KB read.
>
> the problem is not the readahead code, it is the driver code that tries
> to read beyond the end of the device. my change merely exposed this
> misbehavior.
>
> so there is a broken assumption somewhere about how the index of the last
> page of a file/device is computed. i think it is a problem when the file
> ends exactly on a page boundary.
>
> alain, if you don't use the NFS client, marcelo's fix should work just
> fine for you. but i believe that in general it is incorrect.
Okey, most drivers do no exhibit this problem indeed.
We should try to fix the problematic drivers, then.
If we can't do it easily and in a straightforward manner, I'm afraid we
will have to undo your change because even if the "read end beyond of
device" accesses are harmless (are they really harmless?), they must
fixed.
Agreed?
I'll take a look at them later today, but I'm no expert, so help is very
appreciated.
We know that these have problems:
- Promise ATA
- ips (serveraid)
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 18:23 ` Marcelo Tosatti
@ 2004-03-01 18:39 ` Chuck Lever
2004-03-01 18:41 ` Enrico Demarin
1 sibling, 0 replies; 19+ messages in thread
From: Chuck Lever @ 2004-03-01 18:39 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: linux-kernel
On Mon, 1 Mar 2004, Marcelo Tosatti wrote:
> On Mon, 1 Mar 2004, Chuck Lever wrote:
>
> > hi marcelo-
> >
> > your "fix" will break readahead again for NFS. with the ">=" as you
> > propose, the read ahead code will never be able to read the last page of
> > the file as a coalesced read, it will always be a separate 4KB read.
> >
> > the problem is not the readahead code, it is the driver code that tries
> > to read beyond the end of the device. my change merely exposed this
> > misbehavior.
> >
> > so there is a broken assumption somewhere about how the index of the last
> > page of a file/device is computed. i think it is a problem when the file
> > ends exactly on a page boundary.
> >
> > alain, if you don't use the NFS client, marcelo's fix should work just
> > fine for you. but i believe that in general it is incorrect.
>
> Okey, most drivers do no exhibit this problem indeed.
>
> We should try to fix the problematic drivers, then.
it may very well be that most drivers don't complain about reading past
the end of the device.
some have suggested that the end_index computation at the top of
generic_file_readahead is incorrect. that is not beyond the pale, and i
can take a look at that.
this calculation:
end_index = inode->i_size >> PAGE_CACHE_SHIFT;
i think the case where there are bytes in that last page work as i
intended. the problem is that sometimes the end_index value points to a
page with zero bytes (for example when the file is exactly an integral
number of pages in length; this is always the case for most devices).
i_size = 4095 end_index = 0 total_pages_in_file = 1
i_size = 4096 end_index = 1 total_pages_in_file = 1
i_size = 4097 end_index = 1 total_pages_in_file = 2
so right at the boundary we have a little problem.
> If we can't do it easily and in a straightforward manner, I'm afraid we
> will have to undo your change because even if the "read end beyond of
> device" accesses are harmless (are they really harmless?), they must
> fixed.
>
> Agreed?
understood, and thanks for the giving me the opportunity to try to help
you fix it.
> I'll take a look at them later today, but I'm no expert, so help is very
> appreciated.
>
> We know that these have problems:
>
> - Promise ATA
> - ips (serveraid)
i don't have either of those. can anyone who is willing to test a patch
on this hardware e-mail me so we can try this out?
- Chuck Lever
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 18:23 ` Marcelo Tosatti
2004-03-01 18:39 ` Chuck Lever
@ 2004-03-01 18:41 ` Enrico Demarin
2004-03-02 5:18 ` Chuck Lever
1 sibling, 1 reply; 19+ messages in thread
From: Enrico Demarin @ 2004-03-01 18:41 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: Chuck Lever, linux-kernel
Hi Marcelo,
Add mpt fusion driver to the list, it exhibits the problem as well.
- Enrico
On Mon, 2004-03-01 at 13:23, Marcelo Tosatti wrote:
> On Mon, 1 Mar 2004, Chuck Lever wrote:
>
> > hi marcelo-
> >
> > your "fix" will break readahead again for NFS. with the ">=" as you
> > propose, the read ahead code will never be able to read the last page of
> > the file as a coalesced read, it will always be a separate 4KB read.
> >
> > the problem is not the readahead code, it is the driver code that tries
> > to read beyond the end of the device. my change merely exposed this
> > misbehavior.
> >
> > so there is a broken assumption somewhere about how the index of the last
> > page of a file/device is computed. i think it is a problem when the file
> > ends exactly on a page boundary.
> >
> > alain, if you don't use the NFS client, marcelo's fix should work just
> > fine for you. but i believe that in general it is incorrect.
>
> Okey, most drivers do no exhibit this problem indeed.
>
> We should try to fix the problematic drivers, then.
>
> If we can't do it easily and in a straightforward manner, I'm afraid we
> will have to undo your change because even if the "read end beyond of
> device" accesses are harmless (are they really harmless?), they must
> fixed.
>
> Agreed?
>
> I'll take a look at them later today, but I'm no expert, so help is very
> appreciated.
>
> We know that these have problems:
>
> - Promise ATA
> - ips (serveraid)
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
2004-03-01 18:41 ` Enrico Demarin
@ 2004-03-02 5:18 ` Chuck Lever
0 siblings, 0 replies; 19+ messages in thread
From: Chuck Lever @ 2004-03-02 5:18 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: Linux Kernel Mailing List
hi marcelo-
this patch seems to address the extra read at the end of files or devices
that end exactly on a page boundary, while retaining the good readahead
characteristics of my original patch. i'd like to hear about any testing
from folks who have one of:
mpt fusion
ips (ibm serveraid)
promise ata (and maybe sata too)
this patch is against 2.4.26-pre1.
diff -X ../dont-diff -Naurp 00-stock/mm/filemap.c 01-readahead/mm/filemap.c
--- 00-stock/mm/filemap.c 2004-02-18 08:36:32.000000000 -0500
+++ 01-readahead/mm/filemap.c 2004-03-02 00:07:59.000000000 -0500
@@ -1285,7 +1285,8 @@ static void generic_file_readahead(int r
unsigned long raend;
int max_readahead = get_max_readahead(inode);
- end_index = inode->i_size >> PAGE_CACHE_SHIFT;
+ end_index = ((inode->i_size + ~PAGE_CACHE_MASK) >>
+ PAGE_CACHE_SHIFT) - 1;
raend = filp->f_raend;
max_ahead = 0;
- Chuck Lever
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
^ permalink raw reply [flat|nested] 19+ messages in thread
[parent not found: <Pine.LNX.4.44.0403011149560.4148-200000@dmt.cyclades>]
* Re: Ibm Serveraid Problem with 2.4.25
[not found] <Pine.LNX.4.44.0403011149560.4148-200000@dmt.cyclades>
@ 2004-03-01 15:38 ` Jo Christian Buvarp
0 siblings, 0 replies; 19+ messages in thread
From: Jo Christian Buvarp @ 2004-03-01 15:38 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: Enrico Demarin, linux-kernel
Wee :) That was it :)
Everything looks fine now :) Great Work :)
I did the -R against linux-2.4.25 :)
--------------------------------------------------------------
Med vennlig hilsen/Yours sincerely
Jo Christian Buvarp
Svorka Aksess
Notice:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If this e-mail is received by others than the intended recipient, please contact the sender and delete all copies.
Marcelo Tosatti wrote:
>On Sun, 29 Feb 2004, Jo Christian Buvarp wrote:
>
>
>
>>Okay :)
>>I've done some tests now, in the following order:
>>2.4.24-pre3 -> Same problem as before
>>2.4.24-pre2 -> Same problem as before
>>2.4.24-pre1 -> Same problem as before
>>
>>So it looks like the problematic change was added during 2.4.24-pre1
>>
>>To be sure i tested with 2.4.23, and it didn't show anything unusal :)
>>
>>
>
>Hi fellows,
>
>So it seems the problematic change was added -pre1. Thanks for tracking
>that down Jo!
>
>I suspect the problem is the attached "read last page of file"
>modification done by Chuck Lever.
>
>Can you guys please apply it with -R to revert and test again?
>
>Thank you so much for your help in this!!!
>
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Ibm Serveraid Problem with 2.4.25
@ 2004-03-01 21:38 Alan Swanson
0 siblings, 0 replies; 19+ messages in thread
From: Alan Swanson @ 2004-03-01 21:38 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Marcelo Tosatti wrote:
> On Mon, 1 Mar 2004, Chuck Lever wrote:
>
> > hi marcelo-
> >
> > your "fix" will break readahead again for NFS. with the ">=" as you
> > propose, the read ahead code will never be able to read the last page of
> > the file as a coalesced read, it will always be a separate 4KB read.
> >
> > the problem is not the readahead code, it is the driver code that tries
> > to read beyond the end of the device. my change merely exposed this
> > misbehavior.
> >
> > so there is a broken assumption somewhere about how the index of the last
> > page of a file/device is computed. i think it is a problem when the file
> > ends exactly on a page boundary.
> >
> > alain, if you don't use the NFS client, marcelo's fix should work just
> > fine for you. but i believe that in general it is incorrect.
>
> Okey, most drivers do no exhibit this problem indeed.
>
> We should try to fix the problematic drivers, then.
>
> If we can't do it easily and in a straightforward manner, I'm afraid we
> will have to undo your change because even if the "read end beyond of
> device" accesses are harmless (are they really harmless?), they must
> fixed.
>
> Agreed?
>
> I'll take a look at them later today, but I'm no expert, so help is very
> appreciated.
>
> We know that these have problems:
>
> - Promise ATA
> - ips (serveraid)
Also seeing this with the siimage driver with a 3112 SATA chipset.
--
Alan.
"One must never be purposelessnessnesslessness."
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2004-03-02 5:18 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-26 9:12 Ibm Serveraid Problem with 2.4.25 Jo Christian Buvarp
2004-02-26 23:48 ` Enrico Demarin
2004-02-27 1:48 ` Enrico Demarin
2004-02-27 3:14 ` Marcelo Tosatti
2004-02-27 2:37 ` Enrico Demarin
2004-02-27 7:16 ` Jo Christian Buvarp
2004-02-27 14:36 ` Marcelo Tosatti
2004-03-01 2:10 ` Alain Fauconnet
2004-03-01 3:10 ` Enrico Demarin
2004-03-01 3:30 ` Alain Fauconnet
2004-03-01 15:01 ` Enrico Demarin
2004-03-01 15:51 ` Marcelo Tosatti
2004-03-01 17:24 ` Chuck Lever
2004-03-01 18:23 ` Marcelo Tosatti
2004-03-01 18:39 ` Chuck Lever
2004-03-01 18:41 ` Enrico Demarin
2004-03-02 5:18 ` Chuck Lever
[not found] <Pine.LNX.4.44.0403011149560.4148-200000@dmt.cyclades>
2004-03-01 15:38 ` Jo Christian Buvarp
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 21:38 Alan Swanson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox