* 2.6.1 oops
From: Voicu Liviu @ 2004-01-28 21:33 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 5024 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Settings:
- -------------
liviu@starshooter mnt $ uname -a
Linux starshooter 2.6.1-gentoo #2 Wed Jan 28 22:23:52 IST 2004 i686
AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux
liviu@starshooter mnt $
My .config is attached
- ------------------------------
My lspci output:
- ----------------------
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different
version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1
(rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4
(rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3
(rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2
(rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5
(rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
Controller (rev a1)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97
Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge
(rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:09.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:0d.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61)
02:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
device 4150
02:00.1 Display controller: ATI Technologies Inc: Unknown device 4170
This is from /etc/fstab
- ------------------------------
/dev/fd0 /mnt/floppy supermount
user,rw,fs=auto,dev=/dev/fd0 0 0
While I tried to access a floppy I got on dmesg:
++++++++++++++++++++++++++++++++++++
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
Unable to handle kernel NULL pointer dereference at virtual address
00000000
~ printing eip:
c024df24
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c024df24>] Tainted: P
EFLAGS: 00210297
EIP is at parse_options+0xf4/0x1f0
eax: 00000000 ebx: ce133015 ecx: 00000005 edx: c03678c2
esi: de8d9e7c edi: cedd31c0 ebp: d4ff8a00 esp: de8d9e6c
ds: 007b es: 007b ss: 0068
Process mount (pid: 17519, threadinfo=de8d8000 task=df049980)
Stack: ce133015 c0396740 de8d9e7c 00200292 ce13300c ce133014 dffef290
000000d0
~ dffef548 000000d0 bf51b57f 00000006 d4ff8a00 cedd31c0 fffffff4
00000000
~ c024e157 00000000 d4ff8a00 00000000 fffffff4 d4ff8a00 00000000
fffffff4
Call Trace:
~ [<c024e157>] supermount_read_super+0x47/0x210
~ [<c015bc94>] get_sb_nodev+0x64/0xa0
~ [<c015be3e>] do_kern_mount+0x8e/0x100
~ [<c024e110>] supermount_read_super+0x0/0x210
~ [<c0171dd5>] do_add_mount+0x95/0x190
~ [<c0172151>] do_mount+0x171/0x1d0
~ [<c0171f5c>] copy_mount_options+0x8c/0x110
~ [<c0172567>] sys_mount+0xd7/0x140
~ [<c010949b>] syscall_call+0x7/0xb
Code: 80 38 00 75 0a ba ea ff ff ff e9 35 ff ff ff 89 04 24 e8 95
~ <1>Unable to handle kernel NULL pointer dereference at virtual
address 00000000
~ printing eip:
c024df24
*pde = 00000000
Oops: 0000 [#2]
CPU: 0
EIP: 0060:[<c024df24>] Tainted: P
EFLAGS: 00210297
EIP is at parse_options+0xf4/0x1f0
eax: 00000000 ebx: cff29015 ecx: 00000005 edx: c03678c2
esi: de8d9e7c edi: d3c7d8c0 ebp: c32e6600 esp: de8d9e6c
ds: 007b es: 007b ss: 0068
Process mount (pid: 17520, threadinfo=de8d8000 task=df049980)
Stack: cff29015 c0396740 de8d9e7c 00200292 cff2900c cff29014 dffef290
000000d0
~ dffef548 000000d0 bf51b57f 00000006 c32e6600 d3c7d8c0 fffffff4
00000000
~ c024e157 00000000 c32e6600 00000000 fffffff4 c32e6600 00000000
fffffff4
Call Trace:
~ [<c024e157>] supermount_read_super+0x47/0x210
~ [<c015bc94>] get_sb_nodev+0x64/0xa0
~ [<c015be3e>] do_kern_mount+0x8e/0x100
~ [<c024e110>] supermount_read_super+0x0/0x210
~ [<c0171dd5>] do_add_mount+0x95/0x190
~ [<c0172151>] do_mount+0x171/0x1d0
~ [<c0171f5c>] copy_mount_options+0x8c/0x110
~ [<c0172567>] sys_mount+0xd7/0x140
~ [<c010949b>] syscall_call+0x7/0xb
Code: 80 38 00 75 0a ba ea ff ff ff e9 35 ff ff ff 89 04 24 e8 95
~ <7>request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
request_module: failed /sbin/modprobe -- auto. error = 256
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAGCrAkj4I0Et8EMgRAhkbAKDba/fgt0Z+T/5FyWC3JaUlWkrWRgCePm5T
jk0Skcd9g/AGcTH1NxyrUSk=
=ozuw
-----END PGP SIGNATURE-----
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 22465 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=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
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 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# 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=6
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_X86_USE_3DNOW=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 is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
#
# 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 is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# 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_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
CONFIG_PNPBIOS=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD 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=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_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_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP 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 is not set
CONFIG_BLK_DEV_AMD74XX=y
# 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_IDE_CHIPSETS 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=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# 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_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_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 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_IN2000 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_DTC3280 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_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 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_SYM53C416 is not set
# CONFIG_SCSI_DC395x 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
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# 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 is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_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
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER 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_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_QOS=y
CONFIG_NET_ESTIMATOR=y
# CONFIG_NET_CLS is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA 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_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 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=y
# 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
# CONFIG_NET_POCKET 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_NET_BROADCOM 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_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
# 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 is not set
# 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_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_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# 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 is not set
#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
CONFIG_I2C_ISA=y
CONFIG_I2C_NFORCE2=y
# CONFIG_I2C_PIIX4 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_VIAPRO is not set
#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=y
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=y
# 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_VIA686A is not set
CONFIG_SENSORS_W83781D=y
#
# Linux InfraRed Controller
#
# CONFIG_LIRC_SUPPORT 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=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
CONFIG_AGP_NVIDIA=m
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
CONFIG_SPEAKUP_DEFAULT="none"
#
# 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_RTCTIMER is not set
# 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
#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# 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=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
# CONFIG_USB is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_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 is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
#
# 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=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW 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
CONFIG_SUPERMOUNT=y
# CONFIG_SUPERMOUNT_DEBUG is not set
#
# 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 is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
#
# 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_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_TEST=m
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
^ permalink raw reply
* Re: 2.2 kernel and ext3 filesystems
From: Andreas Dilger @ 2004-01-28 21:28 UTC (permalink / raw)
To: Chuck Campbell, Theodore Ts'o, linux-kernel
In-Reply-To: <20040128205810.GA8287@helium.inexs.com>
On Jan 28, 2004 14:58 -0600, Chuck Campbell wrote:
> I mounted this ext3 filesystem as ext2 on my 2.2.16 kernel system. I made
> some changes to some files (simple edits), and now when I reboot the box in
> 2.2.16, I get the following:
>
> mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
> or too many mounted filesystems
>
> in /var/log/messages I see:
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> EXT2-fs: ide0(3,66): couldn't mount because of unsupported optional features.
>
>
> I'm reticent to run any e2fsck as old as 2.2.16 kernel version against
> this filesystem, in fear of damaging it. Is this a sane thing to consider,
> or do I need to put this disk back into a more recent box and try to mount it/
> fsck it there?
e2fsck is not tied to any particular kernel version. You should be able to
see the features that ext2 is complaining about with "dumpe2fs -h /dev/hdb2"
in the "Features" line. I'm guessing it's "needs_recovery" that ext2 doesn't
like. That means that you didn't unmount the ext3 filesystem cleanly and
now ext2 can't mount it. Running any non-prehistoric version of e2fsck
will fix it, but as always newer versions are better. Once e2fsck has
cleaned up the journal, it can be mounted by older kernels as ext2 again.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Andrew Morton @ 2004-01-28 21:25 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: linux-kernel, linux-mm
In-Reply-To: <20040128073237.6e53d999.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> About kernel-janitors patches:
>
> Do you want to continue reviewing/merging the KJ patches one by one
> or just grab the complete patchset?
Please just send them to me in the usual manner when you think they're
ready. The reject rate has been fairly high, so we need to go through them
carefully.
^ permalink raw reply
* Re: [PATCH] PC300 update
From: Christoph Hellwig @ 2004-01-28 21:21 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: torvalds, linux-kernel
In-Reply-To: <Pine.LNX.4.58L.0401281741120.2088@logos.cnet>
> - Mark pci_device_id list with __devinitdata
This is bogus and can crash the kernel if you're unlucky.
> - Add #ifdef DEBUG around debug printk()
What about dprintk or friends instead?
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Grant Grundler @ 2004-01-28 21:14 UTC (permalink / raw)
To: Andi Kleen; +Cc: ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128201701.045670db.ak@suse.de>
On Wed, Jan 28, 2004 at 08:17:01PM +0100, Andi Kleen wrote:
> This would likely
> improve the quality of linux drivers long term and make your
> job as maintainer of an "anal IO error" platform easier.
yup. The key drivers we deal with reached that point last year.
Drivers could always be better. But those issues have been discussed
and presented:
o LinuxTag 2002 keynote by Alan Cox, "Submitting new Kernel drivers"
(http://gsyprf11.external.hp.com/porting_zx1/mgp/Code.mgp)
o OLS 2002 talk by Arjan van de Ven, "How not to write kernel drivers"
o OLS 2002 talk by Greg K-H, "Documentation/CodingStyle and Beyond"
o OLS 2002 talk by myself, "Porting Drivers to HP ZX1"
It helps to "enforce" driver quality through "anal IO Error containment"
but it's too late when it happens on a customer box.
> Just it should not be enabled by default in production kernels.
> And finding out where it works reliably will be some work.
agreed.
> There is no reason pci_map_single() has to panic on overflow. On x86-64
> it returns an unmapped address that is guaranteed to cause an bus abort
> for 128KB.
parisc and ia64 will also bus abort. And then HPMC/MCA respectively.
We could reserve a "safe page" and then hand that back I guess.
But that sounds like a very broken error containment strategy to me.
(ie outbound data will be garbage).
This really isn't an issue for HP ZX1/IA64 since most drivers (64-bit)
can bypass the IOMMU and directly address memory. parisc-linux still
isn't commercially interesting.
> And you have an macro to test for it (pci_dma_error()).
I didn't know about pci_dma_error.
Google found two references: One is:
http://www.x86-64.org/lists/discuss/msg03841.html
> I believe ppc64 has adopted it too. Of course most drivers don't
> use it yet.
<search 2.6.2-rc2 source tree>
grundler <502>find -name '*.[chS]' | xargs fgrep pci_dma_error
./include/asm-x86_64/pci.h:#define pci_dma_error(x) ((x) ==
bad_dma_address)
grundler <503>
That explains why most drivers don't use it yet.
It's only supported on one arch.
Maybe propose this to linux-pci mailing list?
grant
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 21:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281221320.28145@home.osdl.org>
On Wed, 28 Jan 2004 12:28:56 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
>
> Alternatively, if you get a lot of information at MCE time (CPU that did
> the access + some device data), just queue up the information in a per-CPU
> queue. You don't have to worry about overflow - you can just drop if if
That assumes that the access happened with preempt off ?
That's fine if it's guaranteed that the MCE still happened inside
readl/writel. But if it's delayed longer for some reason there is no guarantee
that you can find back to the CPU that caused the fault.
Putting it into the pci_dev and using RCU would be probably better.
-Andi
^ permalink raw reply
* [PATCH] PC300 update
From: Marcelo Tosatti @ 2004-01-28 19:42 UTC (permalink / raw)
To: torvalds; +Cc: linux-kernel
Hi Linus,
This patch forward ports some changes from latest 2.4 driver:
- Update maintainer email address
- Mark pci_device_id list with __devinitdata
- Set correct protocol type on packet receive (this caused the kernel to
drop all packets received)
- Add #ifdef DEBUG around debug printk()
Kudos to Ivan Passos / Daniela Squassoni
Please apply.
--- linux-2.6.1/drivers/net/wan/pc300_drv.c.orig 2004-01-28 12:48:48.000000000 -0200
+++ linux-2.6.1/drivers/net/wan/pc300_drv.c 2004-01-28 13:21:23.634860712 -0200
@@ -6,9 +6,9 @@
* pc300.c Cyclades-PC300(tm) Driver.
*
* Author: Ivan Passos <ivan@cyclades.com>
- * Maintainer: Henrique Gobbi <henrique@cyclades.com>
+ * Maintainer: PC300 Maintainer <pc300@cyclades.com>
*
- * Copyright: (c) 1999-2002 Cyclades Corp.
+ * Copyright: (c) 1999-2003 Cyclades Corp.
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
@@ -252,7 +252,7 @@
#undef PC300_DEBUG_RX
#undef PC300_DEBUG_OTHER
-static struct pci_device_id cpc_pci_dev_id[] = {
+static struct pci_device_id cpc_pci_dev_id[] __devinitdata = {
/* PC300/RSV or PC300/X21, 2 chan */
{0x120e, 0x300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0x300},
/* PC300/RSV or PC300/X21, 1 chan */
@@ -1961,7 +1961,7 @@
}
stats->rx_packets++;
skb->mac.raw = skb->data;
- skb->protocol = htons(ETH_P_HDLC);
+ skb->protocol = hdlc_type_trans(skb, dev);
netif_rx(skb);
}
}
@@ -2088,9 +2088,10 @@
}
}
if (!(dsr_rx = cpc_readb(scabase + DSR_RX(ch)) & DSR_DE)) {
-
-printk("%s: RX intr chan[%d] (st=0x%08lx, dsr=0x%02x, dsr2=0x%02x)\n",
- dev->name, ch, status, drx_stat, dsr_rx);
+#ifdef PC300_DEBUG_INTR
+ printk("%s: RX intr chan[%d] (st=0x%08lx, dsr=0x%02x, dsr2=0x%02x)\n",
+ dev->name, ch, status, drx_stat, dsr_rx);
+#endif
cpc_writeb(scabase + DSR_RX(ch), (dsr_rx | DSR_DE) & 0xfe);
}
}
@@ -3690,6 +3691,6 @@
MODULE_DESCRIPTION("Cyclades-PC300 cards driver");
MODULE_AUTHOR( "Author: Ivan Passos <ivan@cyclades.com>\r\n"
- "Maintainer: Henrique Gobbi <henrique.gobbi@cyclades.com");
+ "Maintainer: PC300 Maintainer <pc300@cyclades.com");
MODULE_LICENSE("GPL");
^ permalink raw reply
* Re: PATCH to access old-style FAT fs
From: OGAWA Hirofumi @ 2004-01-28 21:01 UTC (permalink / raw)
To: Frodo Looijaard; +Cc: H. Peter Anvin, linux-kernel
In-Reply-To: <20040128202443.GA9246@frodo.local>
Frodo Looijaard <frodol@dds.nl> writes:
> On Thu, Jan 29, 2004 at 05:08:32AM +0900, OGAWA Hirofumi wrote:
> >
> > "stop when DIR_Name[0] == 0" should be added after cleanup. The option
> > is not needed.
>
> OK. That would be nice. Like I said, I just hope it does not break other
> FAT implementations, but that is not very likely. At least, that would
> allow read-only mounted EPOC FAT partitions to be handled correctly.
This is spec as hpa saied. So this is right things, and other fat
driver also does, AFAIK.
> > Honestly, I wouldn't like to add the "add a new DIR_Name[0] = 0" part.
> > The option is added easy, but it is not removed easy. And we must
> > maintain it.
>
> I understand. I could always maintain that patch separately for those
> who need it (for read-write mounted EPOC FAT partitions).
Thanks.
> > (BTW, looks like that patch is buggy)
>
> Could well be. Any suggestions what to look out for?
@@ -200,4 +202,8 @@
parse_record:
long_slots = 0;
+ if (oldfat && (de->name[0] == EOD_FLAG))
+ last_entry = 1;
+ if (last_entry)
+ continue;
^^^^^^^^
if (de->name[0] == DELETED_FLAG)
continue;
The above should "goto EODir;". Likewise, another "contiure" of
fat_search_long().
@@ -709,7 +731,20 @@
}
- if (IS_FREE((*de)->name)) {
- if (++row == slots)
+ if ((oldfat && ((*de)->name[0] == EOD_FLAG)))
+ last_entry = 1;
+ if (last_entry || IS_FREE((*de)->name)) {
+ if (++row == slots) {
+ if (last_entry) {
+ /* If we encounter a last_entry, we
+ * need to mark the entry after the
+ * one to be inserted as last_entry
+ * now! */
+ if (fat_get_entry(dir,&curr,bh,de,i_pos) > -1) {
+ (*de)->name[0] = 0;
+ mark_inode_dirty(dir);
mark_inode_dirty(dir) is not needed, instead of it we should do
mark_buffer_dirty(bh).
And this fat_get_entry() updates bh and de, but it should be point to
allocated bh and de, not free entry. It's needed by msdos_add_entry().
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
^ permalink raw reply
* Re: [PATCH][2.6] PCI Scan all functions
From: Ivan Kokshaysky @ 2004-01-28 20:58 UTC (permalink / raw)
To: Greg KH
Cc: Andrew Morton, moilanen, johnrose, linux-kernel, torvalds,
Anton Blanchard
In-Reply-To: <20040127214444.GA27874@kroah.com>
On Tue, Jan 27, 2004 at 01:44:44PM -0800, Greg KH wrote:
> > - if (base && base <= limit) {
> > + if (base <= limit) {
I think the patch is safe. Architectures that don't accept
bridge windows (and regular BARs) at bus address 0 already have
that check elsewhere.
For example, in arch/i386/pci/i386.c:pcibios_allocate_bus_resources():
...
for (idx = PCI_BRIDGE_RESOURCES; idx < PCI_NUM_RESOURCES; idx++) {
r = &dev->resource[idx];
if (!r->start)
^^^^^^^^^
continue;
...
Ivan.
^ permalink raw reply
* Re: 2.2 kernel and ext3 filesystems
From: Chuck Campbell @ 2004-01-28 20:58 UTC (permalink / raw)
To: Theodore Ts'o, linux-kernel
In-Reply-To: <20040127012717.GA19704@thunk.org>
On Mon, Jan 26, 2004 at 08:27:17PM -0500, Theodore Ts'o wrote:
>
> There were also some bug fixes that I'm pretty sure were never
> backported into the 2.2 tree....
I may be being stung by this as we speak.
I mounted this ext3 filesystem as ext2 on my 2.2.16 kernel system. I made
some changes to some files (simple edits), and now when I reboot the box in
2.2.16, I get the following:
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
or too many mounted filesystems
in /var/log/messages I see:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs: ide0(3,66): couldn't mount because of unsupported optional features.
I'm reticent to run any e2fsck as old as 2.2.16 kernel version against
this filesystem, in fear of damaging it. Is this a sane thing to consider,
or do I need to put this disk back into a more recent box and try to mount it/
fsck it there?
Alternatively, where might I dig up an ext3 patch against linux-2.2.x, so
I can build a kernel that will support this? I assume I would need file
utilities that support it as well?
thanks,
-chuck
--
^ permalink raw reply
* Re: long long on 32-bit machines
From: Ulrich Weigand @ 2004-01-28 20:51 UTC (permalink / raw)
To: hpa, arnd; +Cc: linux-kernel
Arnd Bergmann wrote:
>Some architectures require long long arguments to be passed as an
>even/odd register pair. For example on s390,
>
> void f(int a, int b, long long x)
>
>uses registers 2, 3, 4 and 5, while
>
> void f(int a, long long x, int b)
>
>uses registers 2, 4, 5 and 6.
Actually, this isn't quite true -- the second case will also
use registers 2, 3, 4, and 5.
However, there is still a case where a single long long is
passed differently from a pair of longs: when there is only
a single register remaining for parameters.
This means that
void f(int a, int b, int c, int d, long e, long f)
is passed as
a-d in register 2-5
e in register 6
f on the stack (4 bytes)
while
void f(int a, int b, int c, int d, long long e)
is passed as
a-d in register 2-5
nothing in register 6
e on the stack (8 bytes)
Bye,
Ulrich
--
Dr. Ulrich Weigand
weigand@informatik.uni-erlangen.de
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Mike Fedyk @ 2004-01-28 20:46 UTC (permalink / raw)
To: Antony Suter; +Cc: linux-kernel
In-Reply-To: <1075302403.10057.5.camel@hikaru.lan>
On Thu, Jan 29, 2004 at 02:06:43AM +1100, Antony Suter wrote:
> On Tue, Jan 27, 2004 at 11:34:02PM -0800, Andrew Morton wrote:
> > If anyone has any more external trees which need similar treatment,
> > please let me know.
> >
>
> The WLI patchset. It has a small number of good improvements for NUMA
> machines and notebooks. A couple of the patches have already made it
> into the kernel.
Isn't that a bit much? The wli tree makes changes across the entire tree,
so it isn't very localized to any specific subsystem.
Though specific cleanups would be good to merge into -mm from -wli...
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Linus Torvalds @ 2004-01-28 20:30 UTC (permalink / raw)
To: Andi Kleen; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281221320.28145@home.osdl.org>
On Wed, 28 Jan 2004, Linus Torvalds wrote:
>
> If the real error is on the bridge somewhere but you don't even know which
> CPU did the access (and just "somebody" gets an MCE), just set a global
> flag, and have "read_pcix_error()" check the bridge (since it doesn't need
> to look anything up - it already knows the device).
>
> And in that case then you need to take the proper locks (per-bridge, or
> global, depending on just how much you care) in "clear_pcix_error()" and
> release them in "read_pcix_error()".
Note, in case this wasn't clear already: in this case, the "MCE flag" is
just a lazy flag saying "you need to check more deeply". It wouldn't cause
false positives, simply because the _real_ check ends up being
"read_pcix_error()" actually reading the error status from the bridge or
the device.
It's just that 99% of the time, you don't want to do even that.
Linus
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Linus Torvalds @ 2004-01-28 20:28 UTC (permalink / raw)
To: Andi Kleen; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128211554.0cc890fb.ak@suse.de>
On Wed, 28 Jan 2004, Andi Kleen wrote:
>
> Where would you put the flag?
>
> Doing it global may give false errors for the wrong device with async MCEs
> and on SMP.
That entirely depends on what the hardware supports. How much information
will you get about the error?
If the real error is on the bridge somewhere but you don't even know which
CPU did the access (and just "somebody" gets an MCE), just set a global
flag, and have "read_pcix_error()" check the bridge (since it doesn't need
to look anything up - it already knows the device).
And in that case then you need to take the proper locks (per-bridge, or
global, depending on just how much you care) in "clear_pcix_error()" and
release them in "read_pcix_error()".
Alternatively, if you get a lot of information at MCE time (CPU that did
the access + some device data), just queue up the information in a per-CPU
queue. You don't have to worry about overflow - you can just drop if if
you get many errors (or maybe maintain a count), since the only thing that
matters is "we got an error for this device" along with maybe some small
amount of info on what kind(s) of error(s).
Basically: it all boils down to what the hardware offers.
Linus
^ permalink raw reply
* Re: [PATCH] 2.4 ACPI dispatcher/dsmthdat.c warning fix
From: Len Brown @ 2004-01-28 20:27 UTC (permalink / raw)
To: Krzysztof Halasa; +Cc: marcelo.tosatti, lkml
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0020AE787@hdsmsx402.hd.intel.com>
Krzysztof,
You're correct, but the 2.4 and 2.6 trees already got this fix when they
updated to ACPICA 20041116 on Monday night.
thanks,
-Len
On Tue, 2004-01-27 at 16:54, Krzysztof Halasa wrote:
> Hi,
>
> I think this is what the author meant, i.e. we don't need to
> substitute
> obj_desc = new_obj_desc there as it is done later in the file.
>
> This patch doesn't change kernel behaviour, it only eliminates the
> warning message.
>
> Please apply to 2.4 kernel tree. Thanks.
> --
> Krzysztof Halasa, B*FH
>
>
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation II
From: Andi Kleen @ 2004-01-28 20:19 UTC (permalink / raw)
To: Andi Kleen; +Cc: torvalds, willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128211554.0cc890fb.ak@suse.de>
On Wed, 28 Jan 2004 21:15:54 +0100
Andi Kleen <ak@suse.de> wrote:
>
> >
> > Just set a flag aka "may need checking", and let the check be done by the
> > actual "read_pcix_error()" code.
>
> Where would you put the flag?
>
> Doing it global may give false errors for the wrong device with async MCEs
> and on SMP.
>
> For putting it into the pci_dev you need to take logs to walk the list.
> If you delay it to a softirq for safely getting the lock it would be set too late.
>
> Putting it into a different table indexed by pci index would be also racy
> with hotplug.
... to follow up myself ...
I suppose moving the pci_dev lists to RCU could make the flag in pci-dev work. But it would be still
a bit tricky with preemptive kernels.
-Andi
^ permalink raw reply
* Re: long long on 32-bit machines
From: Daniel Jacobowitz @ 2004-01-28 20:25 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <26879984$107531702940180925001758.71044950@config16.schlund.de>
On Wed, Jan 28, 2004 at 08:22:01PM +0100, Arnd Bergmann wrote:
>
> H.P.A wrote:
>
> > Does anyone happen to know if there are *any* 32-bit architectures (on
> > which Linux runs) for which the ABI for a "long long" is different from
> > passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian
> > or (lo,hi) for littleendian?
>
> Some architectures require long long arguments to be passed as an
> even/odd register pair. For example on s390,
>
> void f(int a, int b, long long x)
>
> uses registers 2, 3, 4 and 5, while
>
> void f(int a, long long x, int b)
>
> uses registers 2, 4, 5 and 6. AFAIK, mips does the same, probably others
> as well.
Yes. Also, IIRC, one of SH3 and SH4 requires the padding, and the
other doesn't.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply
* Re: PATCH to access old-style FAT fs
From: Frodo Looijaard @ 2004-01-28 20:24 UTC (permalink / raw)
To: OGAWA Hirofumi; +Cc: H. Peter Anvin, linux-kernel
In-Reply-To: <87y8rr7s5b.fsf@devron.myhome.or.jp>
On Thu, Jan 29, 2004 at 05:08:32AM +0900, OGAWA Hirofumi wrote:
>
> "stop when DIR_Name[0] == 0" should be added after cleanup. The option
> is not needed.
OK. That would be nice. Like I said, I just hope it does not break other
FAT implementations, but that is not very likely. At least, that would
allow read-only mounted EPOC FAT partitions to be handled correctly.
> Honestly, I wouldn't like to add the "add a new DIR_Name[0] = 0" part.
> The option is added easy, but it is not removed easy. And we must
> maintain it.
I understand. I could always maintain that patch separately for those
who need it (for read-write mounted EPOC FAT partitions).
> (BTW, looks like that patch is buggy)
Could well be. Any suggestions what to look out for?
Thanks,
Frodo
--
Frodo Looijaard <frodol@dds.nl> PGP key and more: http://huizen.dds.nl/~frodol
Defenestration n. (formal or joc.):
The act of removing Windows from your computer in disgust, usually followed
by the installation of Linux or some other Unix-like operating system.
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 20:15 UTC (permalink / raw)
To: Linus Torvalds; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281205250.28145@home.osdl.org>
On Wed, 28 Jan 2004 12:06:12 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Wed, 28 Jan 2004, Andi Kleen wrote:
> >
> > On Wed, 28 Jan 2004 11:33:33 -0800 (PST)
> > Linus Torvalds <torvalds@osdl.org> wrote:
> >
> > > For example, if checking for an error involves actually reading a value
> > > from a bridge register, then that implies some _serious_ amount of
> > > serialization and external CPU stuff.
> >
> > Which is _extremly_ hard to do from an MCE handler ...
>
> So don't do it in the MCE handler.
>
> Just set a flag aka "may need checking", and let the check be done by the
> actual "read_pcix_error()" code.
Where would you put the flag?
Doing it global may give false errors for the wrong device with async MCEs
and on SMP.
For putting it into the pci_dev you need to take logs to walk the list.
If you delay it to a softirq for safely getting the lock it would be set too late.
Putting it into a different table indexed by pci index would be also racy
with hotplug.
-Andi
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Olaf Hering @ 2004-01-28 20:04 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
In-Reply-To: <20040127233402.6f5d3497.akpm@osdl.org>
On Tue, Jan 27, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/
>
>
> - From now on, -mm kernels will contain the latest contents of:
>
> Linus's tree: linus.patch
> The ACPI tree: acpi.patch
> Vojtech's tree: input.patch
> Jeff's tree: netdev.patch
> The ALSA tree: alsa.patch
>
> If anyone has any more external trees which need similar treatment,
> please let me know.
The bigendian trees.
Here is a patch to fix compilation on ppc32.
pm_prepare_console returns int and linux/suspend.h is already included.
The ide object files can be found in a subdirectory.
diff -p -purN linux-2.6.2-rc2-mm1.orig/drivers/ide/Makefile linux-2.6.2-rc2-mm1/drivers/ide/Makefile
--- linux-2.6.2-rc2-mm1.orig/drivers/ide/Makefile 2004-01-28 19:30:54.000000000 +0000
+++ linux-2.6.2-rc2-mm1/drivers/ide/Makefile 2004-01-28 19:55:41.000000000 +0000
@@ -34,9 +34,9 @@ ide-core-$(CONFIG_BLK_DEV_MAC_IDE) += ma
ide-core-$(CONFIG_BLK_DEV_Q40IDE) += q40ide.o
# built-in only drivers from ppc/
-ide-core-$(CONFIG_BLK_DEV_MPC8xx_IDE) += mpc8xx.o
-ide-core-$(CONFIG_BLK_DEV_IDE_PMAC) += pmac.o
-ide-core-$(CONFIG_BLK_DEV_IDE_SWARM) += swarm.o
+ide-core-$(CONFIG_BLK_DEV_MPC8xx_IDE) += ppc/mpc8xx.o
+ide-core-$(CONFIG_BLK_DEV_IDE_PMAC) += ppc/pmac.o
+ide-core-$(CONFIG_BLK_DEV_IDE_SWARM) += ppc/swarm.o
obj-$(CONFIG_BLK_DEV_IDE) += ide-core.o
obj-$(CONFIG_IDE_GENERIC) += ide-generic.o
diff -p -purN linux-2.6.2-rc2-mm1.orig/drivers/macintosh/via-pmu.c linux-2.6.2-rc2-mm1/drivers/macintosh/via-pmu.c
--- linux-2.6.2-rc2-mm1.orig/drivers/macintosh/via-pmu.c 2004-01-28 19:30:54.000000000 +0000
+++ linux-2.6.2-rc2-mm1/drivers/macintosh/via-pmu.c 2004-01-28 20:00:00.000000000 +0000
@@ -2339,8 +2339,6 @@ restore_via_state(void)
}
extern long sys_sync(void);
-extern void pm_prepare_console(void);
-extern void pm_restore_console(void);
static int __pmac
pmac_suspend_devices(void)
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
^ permalink raw reply
* Re: PATCH to access old-style FAT fs
From: OGAWA Hirofumi @ 2004-01-28 20:08 UTC (permalink / raw)
To: Frodo Looijaard; +Cc: H. Peter Anvin, linux-kernel
In-Reply-To: <20040128115655.GA696@arda.frodo.local>
Frodo Looijaard <frodol@dds.nl> writes:
> As I said, I *think* it is safe to have my patch always applied (that
> is, stop when DIR_Name[0] == 0, and be careful to add a new DIR_Name[0] = 0
> entry when new entries are added at the back). It would conform to the
> standard. But I would not really be surprised if there was yet another
> FAT implementation somewhere out there that breaks the standard in some
> other subtle way, which works now but exhibits problems with my patch.
> That is why I made it a mount option.
"stop when DIR_Name[0] == 0" should be added after cleanup. The option
is not needed.
Honestly, I wouldn't like to add the "add a new DIR_Name[0] = 0" part.
The option is added easy, but it is not removed easy. And we must
maintain it. (BTW, looks like that patch is buggy)
Those stuff makes a change of the normal path difficult really. At the
same reason, I removed the fat_cvf stuff.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Linus Torvalds @ 2004-01-28 20:06 UTC (permalink / raw)
To: Andi Kleen; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128204049.627e6312.ak@suse.de>
On Wed, 28 Jan 2004, Andi Kleen wrote:
>
> On Wed, 28 Jan 2004 11:33:33 -0800 (PST)
> Linus Torvalds <torvalds@osdl.org> wrote:
>
> > For example, if checking for an error involves actually reading a value
> > from a bridge register, then that implies some _serious_ amount of
> > serialization and external CPU stuff.
>
> Which is _extremly_ hard to do from an MCE handler ...
So don't do it in the MCE handler.
Just set a flag aka "may need checking", and let the check be done by the
actual "read_pcix_error()" code.
Linus
^ permalink raw reply
* oops 2.6.1 adsl
From: rollor @ 2004-01-28 20:01 UTC (permalink / raw)
To: linux-kernel
hi,
I am testing the 2.6.1 kernel on a p4,
debian sarge. I tried to start my adsl
connection and received this:
Jan 28 17:40:54 rock pppd[913]: pppd
2.4.2 started by oot, uid 0
Jan 28 17:40:54 rock pppd[913]: Serial
connection established.
Jan 28 17:40:54 rock pppd[913]: Using
interface ppp0
Jan 28 17:40:54 rock pppd[913]:
Connect: ppp0 <--> /dev/pts/0
Jan 28 17:40:54 rock kernel: Badness
in local_bh_enable at kernel/softirq.c:121
Jan 28 17:40:54 rock kernel: Call Trace:
Jan 28 17:40:54 rock kernel:
[local_bh_enable+133/135]
local_bh_enable+0x85/0x87 Jan 28
17:40:54 rock kernel:
[ppp_async_push+158/373]
ppp_async_push+0x9e/0x175
Jan 28 17:40:54 rock kernel:
[ppp_asynctty_wakeup+45/94]
ppp_asynctty_wakeup+0x2d/0x5e
Jan 28 17:40:54 rock kernel:
[pty_unthrottle+88/90]
pty_unthrottle+0x58/0x5a Jan
28 17:40:54 rock kernel:
[check_unthrottle+57/59]
check_unthrottle+0x39/0x3b
Jan 28 17:40:54 rock kernel:
[n_tty_flush_buffer+19/85]
n_tty_flush_buffer+0x13/0x55
Jan 28 17:40:54 rock kernel:
[pty_flush_buffer+102/104]
pty_flush_buffer+0x66/0x68
Jan 28 17:40:54 rock kernel:
[do_tty_hangup+1146/1243]
do_tty_hangup+0x47a/0x4db
Jan 28 17:40:54 rock kernel:
[release_dev+1752/1796]
release_dev+0x6d8/0x704
Jan 28 17:40:54 rock kernel:
[unmap_page_range+67/105]
unmap_page_range+0x43/0x69 Jan 28
17:40:54 rock pppd[913]: Modem hangup
Jan 28 17:40:54 rock kernel:
[tty_release+45/102] tty_release+0x2d/0x66
Jan 28 17:40:54 rock pppd[913]:
Connection terminated.
Jan 28 17:40:54 rock kernel:
[__fput+258/276] __fput+0x102/0x114
Jan 28 17:40:54 rock kernel:
[filp_close+89/134] filp_close+0x59/0x86
Jan 28 17:40:54 rock kernel:
[put_files_struct+132/233]
put_files_struct+0x84/0xe9 Jan 28
17:40:54 rock kernel:
[do_exit+397/1034] do_exit+0x18d/0x40a
Jan 28 17:40:54 rock kernel:
[do_group_exit+58/172]
do_group_exit+0x3a/0xac
Jan 28 17:40:54 rock kernel:
[syscall_call+7/11] syscall_call+0x7/0xb
if someone needs more information,
please let me now.
PS: CC to me.
thanks.
__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.br/
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 20:01 UTC (permalink / raw)
To: davidm; +Cc: davidm, iod00d, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <16408.4597.123125.788631@napali.hpl.hp.com>
On Wed, 28 Jan 2004 11:48:05 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Wed, 28 Jan 2004 20:39:15 +0100, Andi Kleen <ak@suse.de> said:
>
> >> Yet they are a good indicator that something is wrong (not performing
> >> properly) or may be failing soon. I don't think putting on blinders
> >> for such problems is a good idea. Though I agree that the question of
>
> Andi> Most server class hardware should log it somewhere and allow
> Andi> to read the event log in the firmware. This even works for
> Andi> unhandleable errors unlike what the OS could do.
>
> And you'd want to reboot your server just so you can check on the soft
> failure rate? ;-)
Yep, I reboot my machines all the time ;-)
Seriously you can count it somewhere and present it in sysfs or /proc.
Or log it somewhere else and supply a special utility to show them
that makes it clear that the events are hardware and not software related.
I suppose if your server vendor is serious they will supply a tool
to read the firmware log from a running system.
But printks enabled by default are a bad idea (and a bug too BTW - printk called from
MCE handlers can randomly deadlock)
-Andi
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Torrey Hoffman @ 2004-01-28 19:55 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linux-Kernel List, linux-mm
In-Reply-To: <20040127233402.6f5d3497.akpm@osdl.org>
On Tue, 2004-01-27 at 23:34, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/
Got this during system startup, just before X came up.
System is Fedora Core 1 with lots of updates on a P4 HT.
(I include a few lines before and after from dmesg, in case context is
relevant?)
...
lp: driver loaded but no devices found
request_module: failed /sbin/modprobe -- char-major-4-72. error = 256
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49844 usecs
intel8x0: clocking to 48000
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c0243b74
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
CPU: 1
EIP: 0060:[<c0243b74>] Not tainted VLI
EFLAGS: 00010286
EIP is at vt_ioctl+0x14/0x1f80
eax: 00000000 ebx: f5dde000 ecx: 00005607 edx: f14cd480
esi: f5dde000 edi: 00005607 ebp: f6593f70 esp: f6593ea0
ds: 007b es: 007b ss: 0068
Process X (pid: 2378, threadinfo=f6592000 task=f11ca6c0)
Stack: 00000006 f7f00068 f7043005 00299a31 00000003 f7337280 f6593f14
f6593f6c
f6593f0c f7337280 f6e88480 f6593ee0 c0178bec f6593f0c f7043008
f6e88480
f6593f30 c016fdda 00000020 f6593f30 00001846 00000001 c047991e
f7177e00
Call Trace:
[<c0178bec>] dput+0x1c/0x2d0
[<c016fdda>] link_path_walk+0x6ba/0xa60
[<c016adc4>] cdev_get+0x54/0xc0
[<c016ae3f>] cdev_put+0xf/0x60
[<c01232f0>] schedule+0x3b0/0x740
[<c0243b60>] vt_ioctl+0x0/0x1f80
[<c023e885>] tty_ioctl+0x355/0x450
[<c0173e6b>] sys_ioctl+0x11b/0x2d0
[<c023e530>] tty_ioctl+0x0/0x450
[<c0160b96>] sys_open+0x56/0x70
[<c033c65a>] sysenter_past_esp+0x43/0x69
Code: ff e8 05 88 ec ff e9 70 ff ff ff 90 90 90 90 90 90 90 90 90 90 90
90 55 89 e5 57 56 53 81 ec c4 00 00 00 89 c6 8b 80 78 09 00 00 <8b> 00
89 85 30 ff ff ff 8b 04 85 20 9b 47 c0 89 45 8c 8b 85 30
<7>request_module: failed /sbin/modprobe -- char-major-10-134. error =
256
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
--
Torrey Hoffman <thoffman@arnor.net>
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox