2.5.1-pre5 not easy to boot with devfs

2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

As far as I can see,

when CONFIG_DEBUG_KERNEL is set
  and 
when devfsd is started at boot time
I get an Oops when remounting, rw the root fs :

Unable to handle kernel request at va 5a5a5a5e
...
EIP: 0010:[<c01516f9>] Not tainted
...
Process devfsd(pid:15,stackpage=cfd33000)
...

It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
can be started after login).

PIII 650 256Mb devfsd-v1.3.20

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Alexander Viro]

On Sat, 1 Dec 2001, Pierre Rousselet wrote:

> As far as I can see,
> 
> when CONFIG_DEBUG_KERNEL is set
>   and 
> when devfsd is started at boot time
> I get an Oops when remounting, rw the root fs :
> 
> Unable to handle kernel request at va 5a5a5a5e
> ...
> EIP: 0010:[<c01516f9>] Not tainted

Umm...  How about a stack trace?

Re: 2.5.1-pre5 not easy to boot with devfs

[Linus Torvalds]

In article <3C085FF3.813BAA57@wanadoo.fr>,
Pierre Rousselet  <pierre.rousselet@wanadoo.fr> wrote:
>As far as I can see,
>
>when CONFIG_DEBUG_KERNEL is set
>  and 
>when devfsd is started at boot time
>I get an Oops when remounting, rw the root fs :
>
>Unable to handle kernel request at va 5a5a5a5e

POISON_BYTE is 0x5a. Something in devfs is using a pointer from a data
structure that was already free'd, and was thus corrupted by poisoning.

(the above is almost certainly just a pointer dereference off 0x5a5a5a5a
with an offset of 4 for some entry at the beginning of a structure,
which is why you get the final "5e" in the page fault address). 

>It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
>It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
>can be started after login).

Well, not poisoning the free'd memory makes it "work" only in the sense
that usually the free'd memory hasn't been re-allocated yet, so you
don't see the bug even if it is still there.

Richard Gooch probably wants a full stack trace, with symbols. Which
should show it fairly clearly. At least EIP and the first few "stack
trace" entries..

		Linus

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Linus Torvalds writes:
> In article <3C085FF3.813BAA57@wanadoo.fr>,
> Pierre Rousselet  <pierre.rousselet@wanadoo.fr> wrote:
> >As far as I can see,
> >
> >when CONFIG_DEBUG_KERNEL is set
> >  and 
> >when devfsd is started at boot time
> >I get an Oops when remounting, rw the root fs :
> >
> >Unable to handle kernel request at va 5a5a5a5e
> 
> POISON_BYTE is 0x5a. Something in devfs is using a pointer from a data
> structure that was already free'd, and was thus corrupted by poisoning.
> 
> (the above is almost certainly just a pointer dereference off 0x5a5a5a5a
> with an offset of 4 for some entry at the beginning of a structure,
> which is why you get the final "5e" in the page fault address). 
> 
> >It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
> >It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
> >can be started after login).
> 
> Well, not poisoning the free'd memory makes it "work" only in the sense
> that usually the free'd memory hasn't been re-allocated yet, so you
> don't see the bug even if it is still there.
> 
> Richard Gooch probably wants a full stack trace, with symbols. Which
> should show it fairly clearly. At least EIP and the first few "stack
> trace" entries..

Indeed I do. Please Cc: me on devfs related stuff. And please apply
devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
knowing the behaviour with 2.4.17-pre1.

I also need your full .config and boot messages. And booting with
"devfs=dall" is required as well.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Richard Gooch wrote:
> 
> Linus Torvalds writes:
> > In article <3C085FF3.813BAA57@wanadoo.fr>,
> > Pierre Rousselet  <pierre.rousselet@wanadoo.fr> wrote:
> > >As far as I can see,
> > >
> > >when CONFIG_DEBUG_KERNEL is set
> > >  and
> > >when devfsd is started at boot time
> > >I get an Oops when remounting, rw the root fs :
> > >
> > >Unable to handle kernel request at va 5a5a5a5e
> >
> > POISON_BYTE is 0x5a. Something in devfs is using a pointer from a data
> > structure that was already free'd, and was thus corrupted by poisoning.
> >
> > (the above is almost certainly just a pointer dereference off 0x5a5a5a5a
> > with an offset of 4 for some entry at the beginning of a structure,
> > which is why you get the final "5e" in the page fault address).
> >
> > >It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
> > >It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
> > >can be started after login).
> >
> > Well, not poisoning the free'd memory makes it "work" only in the sense
> > that usually the free'd memory hasn't been re-allocated yet, so you
> > don't see the bug even if it is still there.
> >
> > Richard Gooch probably wants a full stack trace, with symbols. Which
> > should show it fairly clearly. At least EIP and the first few "stack
> > trace" entries..
> 
> Indeed I do. Please Cc: me on devfs related stuff. And please apply
> devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
> knowing the behaviour with 2.4.17-pre1.

Unable to handle kernel request at virtual address 5a5a5a5e
  printing eip :
c01516f9
*pde=00000000
Oops: 0002
CPU: 0
EIP: 010:[<c01516f9>] Not tainted
EFLAGS: 00010206
eax: 5a5a5a5a ebx: 5a5a5a5a ecx: 00000014 edx: 5a5a5a5a
esi: 00000000 edi: 00000026 ebp: 00000000 esp: cfd33f40
ds: 0018 es: 018 ss: 0018
Process devfsd(pid:15,stackpage=cfd33000)
Stack: 00000026 c015419c 5a5a5a5a c15c65e4 ffffffea 00000000 00000420
cfdcb000
c01e7200 cfd16240 5a5a5a5a 000003fa 00000000 00000000 00000001 00000000
cfd30000 00000000 00000000 00000000 cfd30000 c01e722c c01e722c c012f5e6
Call Trace: [<c015419c>] [<c012f5e6>] [<c0106b2b>]

Code: ff 46 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 36 1d 00 15 21 c0


> 
> I also need your full .config 
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

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

#
# Processor type and features
#
# 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_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_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_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set

#
# 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_PCI_NAMES is not set
# 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=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF 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=y
CONFIG_PARPORT_PC_SUPERIO=y
# 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_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# 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_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set

#
# 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=m
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK is not set
# CONFIG_NETFILTER is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
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_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK 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 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 is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING 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_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=y
CONFIG_BLK_DEV_PIIX=y
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS 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_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# 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 is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN 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_SUNLANCE 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
# 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_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT 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 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_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_VIA_RHINE_MMIO is not set
# 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_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# 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=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

#
# 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

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=m
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_UNIX98_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=m
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD 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

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_I810 is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# 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_BFS_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# 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 is not set
CONFIG_TMPFS=y
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# 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=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# 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

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
# 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=m
CONFIG_ZLIB_FS_INFLATE=m

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

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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_1251 is not set
CONFIG_NLS_ISO8859_1=m
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
CONFIG_SOUND=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_MIDI_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
CONFIG_SOUND_ES1370=m
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_MIDI_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_TVMIXER is not set

#
# USB support
#
# CONFIG_USB is not set

#
# USB Controllers
#
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_STORAGE is not set
# 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_JUMPSHOT is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# USB Human Interface Devices (HID)
#

#
#   Input core support is needed for USB HID
#

#
# 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_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
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_RIO500 is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_BUGVERBOSE=y

> and boot messages. And booting with

Difficult, I have no log in this case. I don't see unusual message
before the oops except :

none already mounted on /dev

/dev is only a mountpoint on my system. I have no other fallback without
devfs but a working kernel (thanksfully there are plenty).

> "devfs=dall" is required as well.

No option appended (no 'devfs='). grub.


Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Bongani Hlope]

I am using Mandrake 8.1 (I think it loads devfs on startup)
I have compiled  2.4.17-pre1 and i get the same oops.

Pierre Rousselet wrote:

> Richard Gooch wrote:
> 
>>Linus Torvalds writes:
>>
>>>In article <3C085FF3.813BAA57@wanadoo.fr>,
>>>Pierre Rousselet  <pierre.rousselet@wanadoo.fr> wrote:
>>>
>>>>As far as I can see,
>>>>
>>>>when CONFIG_DEBUG_KERNEL is set
>>>> and
>>>>when devfsd is started at boot time
>>>>I get an Oops when remounting, rw the root fs :
>>>>
>>>>Unable to handle kernel request at va 5a5a5a5e
>>>>
>>>POISON_BYTE is 0x5a. Something in devfs is using a pointer from a data
>>>structure that was already free'd, and was thus corrupted by poisoning.
>>>
>>>(the above is almost certainly just a pointer dereference off 0x5a5a5a5a
>>>with an offset of 4 for some entry at the beginning of a structure,
>>>which is why you get the final "5e" in the page fault address).
>>>
>>>
>>>>It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
>>>>It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
>>>>can be started after login).
>>>>
>>>Well, not poisoning the free'd memory makes it "work" only in the sense
>>>that usually the free'd memory hasn't been re-allocated yet, so you
>>>don't see the bug even if it is still there.
>>>
>>>Richard Gooch probably wants a full stack trace, with symbols. Which
>>>should show it fairly clearly. At least EIP and the first few "stack
>>>trace" entries..
>>>
>>Indeed I do. Please Cc: me on devfs related stuff. And please apply
>>devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
>>knowing the behaviour with 2.4.17-pre1.


<snip very long config file>
.......
</snip>

I am using Mandrake 8.1 (I think it loads devfs on startup)
I have compiled  2.4.17-pre1 and i get the same oops.
2.4.16-pre1 does not seem to have a problem. I will try
2.4.17-pre2 and see how it goes.
-Bongani

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

This Oops comes after starting devfsd by hand, it is possibly more
reliable than the previous one :

Unable to handle kernel paging request at virtual address 5a5a5a5e 
 printing eip: 
c01516f9 
*pde = 00000000 
Oops: 0002 
CPU:    0 
EIP:    0010:[devfs_put+13/188]    Tainted: P  
EFLAGS: 00013206 
eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000016   edx: 5a5a5a5a 
esi: 00000000   edi: 00000026   ebp: 00000000   esp: cf631f40 
ds: 0018   es: 0018   ss: 0018 
Process devfsd (pid: 144, stackpage=cf631000) 
Stack: 00000026 c015419c 5a5a5a5a cf96ba34 ffffffea 00000000 00000420
cfb80800  
c01e7200 cf4f2240 5a5a5a5a 000003fa 00000000 00000000 00000001 00000000  
cf630000 00000000 00000000 00000000 cf630000 c01e722c c01e722c c012f5e6  
Call Trace: [devfsd_read+852/972] [sys_read+150/204]
[system_call+51/56]  
 
Code: ff 4b 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 3b 1d 00 15 21 c0  

ksymoops 2.4.3 on i686 2.5.1-pre5.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.1-pre5/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Unable to handle kernel paging request at virtual address 5a5a5a5e 
c01516f9 
*pde = 00000000 
Oops: 0002 
CPU:    0 
EIP:    0010:[devfs_put+13/188]    Tainted: P  
EFLAGS: 00013206 
eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000016   edx: 5a5a5a5a 
esi: 00000000   edi: 00000026   ebp: 00000000   esp: cf631f40 
ds: 0018   es: 0018   ss: 0018 
Process devfsd (pid: 144, stackpage=cf631000) 
Stack: 00000026 c015419c 5a5a5a5a cf96ba34 ffffffea 00000000 00000420
cfb80800  
c01e7200 cf4f2240 5a5a5a5a 000003fa 00000000 00000000 00000001 00000000  
cf630000 00000000 00000000 00000000 cf630000 c01e722c c01e722c c012f5e6  
Call Trace: [devfsd_read+852/972] [sys_read+150/204]
[system_call+51/56]  
Code: ff 4b 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 3b 1d 00 15 21 c0  
Using defaults from ksymoops -t elf32-i386 -a i386

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   ff 4b 04                  decl   0x4(%ebx)
Code;  00000002 Before first symbol
   3:   0f 94 c0                  sete   %al
Code;  00000006 Before first symbol
   6:   84 c0                     test   %al,%al
Code;  00000008 Before first symbol
   8:   0f 84 9e 00 00 00         je     ac <_EIP+0xac> 000000ac Before
first symbol
Code;  0000000e Before first symbol
   e:   3b 1d 00 15 21 c0         cmp    0xc0211500,%ebx


1 warning issued.  Results may not be reliable.

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Pierre Rousselet writes:
> Richard Gooch wrote:
> > Indeed I do. Please Cc: me on devfs related stuff. And please apply
> > devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
> > knowing the behaviour with 2.4.17-pre1.

Did you apply devfs-patch-v200?

> > and boot messages. And booting with
> 
> Difficult, I have no log in this case. I don't see unusual message
> before the oops except :

I need those boot messages.

> none already mounted on /dev

Edit your /etc/fstab and remove the line for devfs. You don't
need/want that if you have CONFIG_DEVFS_MOUNT=y.

> /dev is only a mountpoint on my system. I have no other fallback without
> devfs but a working kernel (thanksfully there are plenty).
> 
> > "devfs=dall" is required as well.
> 
> No option appended (no 'devfs='). grub.

I know nothing about grub. Somehow, you need to pass "devfs=dall" to
the kernel when booting. And I need to see the boot messages when this
option is given to the kernel. If it's too verbose, you can try
"devfs=dreg,dunreg,dfree" instead. Copy the messages down by hand if
you need to, but I need to see them. Do yourself a favour and set up a
serial console so you can capture boot messages easily.

Also, make sure you are not using any proprietary drivers (like
NVidia). If you have such drivers, move them to another directory to
prevent their being loaded. Even if you load but don't use such
drivers, they still make debugging information unreliable.

I've had a look at the code, and I see no reason for devfs to fail in
this way, unless some driver is abusing it.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Richard Gooch wrote:
> 
> Pierre Rousselet writes:
> > Richard Gooch wrote:
> > > Indeed I do. Please Cc: me on devfs related stuff. And please apply
> > > devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
> > > knowing the behaviour with 2.4.17-pre1.
> 
> Did you apply devfs-patch-v200?
> 
Well, I am now back with 2.4.16 and devfsd-1.3.18. Playing with devfs is
a risky game.

I applied devfs-patch-v200 against 2.5.1-pre5 :

patching file linux/Documentation/filesystems/devfs/ChangeLog
patching file linux/drivers/char/pty.c
patching file linux/drivers/char/tty_io.c
Hunk #1 succeeded at 1339 (offset -4 lines).
patching file linux/fs/devfs/base.c
patching file linux/include/linux/devfs_fs_kernel.h

And I got an oops when booting with devfsd-1.3.20. Luckily, I get the
same oops when booting without devfsd and starting it after loging in.
Here it is

ksymoops 2.4.3 on i686 2.5.1-pre5.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.1-pre5/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

 Unable to handle kernel paging request at virtual address 5a5a5a5e 
 c01516f9 
 *pde = 00000000 
 Oops: 0002 
 CPU:    0 
 EIP:    0010:[devfs_put+13/188]    Not tainted 
 EFLAGS: 00010206 
 eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000017   edx: 5a5a5a5a 
 esi: 00000000   edi: 00000026   ebp: 00000000   esp: cf4f7f40 
 ds: 0018   es: 0018   ss: 0018 
 Process devfsd (pid: 167, stackpage=cf4f7000) 
 Stack: 00000026 c015420c 5a5a5a5a cf7a25e4 ffffffea 00000000 00000420
cfb80800  
        c01e7280 cf33c240 5a5a5a5a 000003fa 00000000 00000000 00000001
00000000  
        cf4f6000 00000000 00000000 00000000 cf4f6000 c01e72ac c01e72ac
c012f5e6  
 Call Trace: [devfsd_read+964/972] [sys_read+150/204]
[system_call+51/56]  
 Code: ff 4b 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 3b 1d 00 15 21 c0  
Using defaults from ksymoops -t elf32-i386 -a i386

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   ff 4b 04                  decl   0x4(%ebx)
Code;  00000002 Before first symbol
   3:   0f 94 c0                  sete   %al
Code;  00000006 Before first symbol
   6:   84 c0                     test   %al,%al
Code;  00000008 Before first symbol
   8:   0f 84 9e 00 00 00         je     ac <_EIP+0xac> 000000ac Before
first symbol
Code;  0000000e Before first symbol
   e:   3b 1d 00 15 21 c0         cmp    0xc0211500,%ebx


1 warning issued.  Results may not be reliable.

> > > and boot messages. And booting with
> >
> > Difficult, I have no log in this case. I don't see unusual message
> > before the oops except :
> 
> I need those boot messages.

Here is a log of a successful boot with devfs-patch-v200 but without
starting devfsd. 

Dec  1 18:47:20 milou kernel: Linux version 2.5.1-pre5 (root@milou) (gcc
version 2.95.3 20010315 (release)) #3 sam déc 1 18:21:42 CET 2001 
Dec  1 18:47:20 milou kernel: BIOS-provided physical RAM map: 
Dec  1 18:47:20 milou kernel:  BIOS-e820: 0000000000000000 -
000000000009fc00 (usable) 
Dec  1 18:47:20 milou kernel:  BIOS-e820: 000000000009fc00 -
00000000000a0000 (reserved) 
Dec  1 18:47:20 milou kernel:  BIOS-e820: 00000000000f0000 -
0000000000100000 (reserved) 
Dec  1 18:47:20 milou kernel:  BIOS-e820: 0000000000100000 -
0000000010000000 (usable) 
Dec  1 18:47:20 milou kernel:  BIOS-e820: 00000000ffff0000 -
0000000100000000 (reserved) 
Dec  1 18:47:20 milou kernel: On node 0 totalpages: 65536 
Dec  1 18:47:20 milou kernel: zone(0): 4096 pages. 
Dec  1 18:47:20 milou kernel: zone(1): 61440 pages. 
Dec  1 18:47:20 milou kernel: zone(2): 0 pages. 
Dec  1 18:47:20 milou kernel: Kernel command line: vga=4
root=/dev/discs/disc0/part2 ro mem=262144K 
Dec  1 18:47:20 milou kernel: Initializing CPU#0 
Dec  1 18:47:20 milou kernel: Detected 670.105 MHz processor. 
Dec  1 18:47:20 milou kernel: Console: colour VGA+ 80x30 
Dec  1 18:47:20 milou kernel: Calibrating delay loop... 1336.93 BogoMIPS 
Dec  1 18:47:20 milou kernel: Memory: 256424k/262144k available (733k
kernel code, 5332k reserved, 222k data, 68k init, 0k highmem) 
Dec  1 18:47:20 milou kernel: Dentry-cache hash table entries: 32768
(order: 6, 262144 bytes) 
Dec  1 18:47:20 milou kernel: Inode-cache hash table entries: 16384
(order: 5, 131072 bytes) 
Dec  1 18:47:20 milou kernel: Mount-cache hash table entries: 4096
(order: 3, 32768 bytes) 
Dec  1 18:47:20 milou kernel: Buffer-cache hash table entries: 16384
(order: 4, 65536 bytes) 
Dec  1 18:47:20 milou kernel: Page-cache hash table entries: 65536
(order: 6, 262144 bytes) 
Dec  1 18:47:20 milou kernel: CPU: Before vendor init, caps: 0383f9ff
00000000 00000000, vendor = 0 
Dec  1 18:47:20 milou kernel: CPU: L1 I cache: 16K, L1 D cache: 16K 
Dec  1 18:47:20 milou kernel: CPU: L2 cache: 256K 
Dec  1 18:47:20 milou kernel: Intel machine check architecture
supported. 
Dec  1 18:47:20 milou kernel: Intel machine check reporting enabled on
CPU#0. 
Dec  1 18:47:20 milou kernel: CPU: After vendor init, caps: 0383f9ff
00000000 00000000 00000000 
Dec  1 18:47:20 milou kernel: CPU:     After generic, caps: 0383f9ff
00000000 00000000 00000000 
Dec  1 18:47:20 milou kernel: CPU:             Common caps: 0383f9ff
00000000 00000000 00000000 
Dec  1 18:47:20 milou kernel: CPU: Intel Pentium III (Coppermine)
stepping 01 
Dec  1 18:47:20 milou kernel: Enabling fast FPU save and restore...
done. 
Dec  1 18:47:20 milou kernel: Enabling unmasked SIMD FPU exception
support... done. 
Dec  1 18:47:20 milou kernel: Checking 'hlt' instruction... OK. 
Dec  1 18:47:20 milou kernel: POSIX conformance testing by UNIFIX 
Dec  1 18:47:20 milou kernel: mtrr: v1.40 (20010327) Richard Gooch
(rgooch@atnf.csiro.au) 
Dec  1 18:47:20 milou kernel: mtrr: detected mtrr type: Intel 
Dec  1 18:47:20 milou kernel: PCI: PCI BIOS revision 2.10 entry at
0xfb380, last bus=1 
Dec  1 18:47:20 milou kernel: PCI: Using configuration type 1 
Dec  1 18:47:20 milou kernel: PCI: Probing PCI hardware 
Dec  1 18:47:20 milou kernel: Unknown bridge resource 0: assuming
transparent 
Dec  1 18:47:20 milou kernel: PCI: Using IRQ router PIIX [8086/7110] at
00:07.0 
Dec  1 18:47:20 milou kernel: Limiting direct PCI/PCI transfers. 
Dec  1 18:47:20 milou kernel: Linux NET4.0 for Linux 2.4 
Dec  1 18:47:20 milou kernel: Based upon Swansea University Computer
Society NET3.039 
Dec  1 18:47:20 milou kernel: apm: BIOS version 1.2 Flags 0x07 (Driver
version 1.15) 
Dec  1 18:47:20 milou kernel: Starting kswapd 
Dec  1 18:47:20 milou kernel: BIO: pool of 256 setup, 14Kb (56
bytes/bio) 
Dec  1 18:47:20 milou kernel: biovec: init pool 0, 1 entries, 12 bytes 
Dec  1 18:47:20 milou kernel: biovec: init pool 1, 4 entries, 48 bytes 
Dec  1 18:47:20 milou kernel: biovec: init pool 2, 16 entries, 192 bytes 
Dec  1 18:47:20 milou kernel: biovec: init pool 3, 64 entries, 768 bytes 
Dec  1 18:47:20 milou kernel: biovec: init pool 4, 128 entries, 1536
bytes 
Dec  1 18:47:20 milou kernel: biovec: init pool 5, 256 entries, 3072
bytes 
Dec  1 18:47:20 milou kernel: devfs: v1.2 (20011127) Richard Gooch
(rgooch@atnf.csiro.au) 
Dec  1 18:47:20 milou kernel: devfs: boot_options: 0x1 
Dec  1 18:47:20 milou kernel: block: 256 slots per queue, batch=32 
Dec  1 18:47:20 milou kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.32 
Dec  1 18:47:20 milou kernel: ide: Assuming 33MHz system bus speed for
PIO modes; override with idebus=xx 
Dec  1 18:47:20 milou kernel: PIIX4: IDE controller on PCI slot 00:07.1 
Dec  1 18:47:20 milou kernel: PIIX4: chipset revision 1 
Dec  1 18:47:20 milou kernel: PIIX4: not 100% native mode: will probe
irqs later 
Dec  1 18:47:20 milou kernel:     ide0: BM-DMA at 0xf000-0xf007, BIOS
settings: hda:pio, hdb:pio 
Dec  1 18:47:20 milou kernel:     ide1: BM-DMA at 0xf008-0xf00f, BIOS
settings: hdc:pio, hdd:pio 
Dec  1 18:47:20 milou kernel: HPT366: onboard version of chipset, pin1=1
pin2=2 
Dec  1 18:47:20 milou kernel: HPT366: IDE controller on PCI slot 00:13.0 
Dec  1 18:47:20 milou kernel: PCI: Found IRQ 11 for device 00:13.0 
Dec  1 18:47:20 milou kernel: PCI: Sharing IRQ 11 with 00:13.1 
Dec  1 18:47:20 milou kernel: HPT366: chipset revision 1 
Dec  1 18:47:20 milou kernel: HPT366: not 100% native mode: will probe
irqs later 
Dec  1 18:47:20 milou kernel:     ide2: BM-DMA at 0xd400-0xd407, BIOS
settings: hde:pio, hdf:pio 
Dec  1 18:47:20 milou kernel: HPT366: IDE controller on PCI slot 00:13.1 
Dec  1 18:47:20 milou kernel: PCI: Found IRQ 11 for device 00:13.1 
Dec  1 18:47:20 milou kernel: PCI: Sharing IRQ 11 with 00:13.0 
Dec  1 18:47:20 milou kernel: HPT366: chipset revision 1 
Dec  1 18:47:20 milou kernel: HPT366: not 100% native mode: will probe
irqs later 
Dec  1 18:47:20 milou kernel:     ide3: BM-DMA at 0xe000-0xe007, BIOS
settings: hdg:pio, hdh:pio 
Dec  1 18:47:20 milou kernel: hdc: CRD-8240B, ATAPI CD/DVD-ROM drive 
Dec  1 18:47:20 milou kernel: hde: ST310212A, ATA DISK drive 
Dec  1 18:47:20 milou kernel: hdg: SAMSUNG SV0322A, ATA DISK drive 
Dec  1 18:47:20 milou kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Dec  1 18:47:20 milou kernel: ide2 at 0xcc00-0xcc07,0xd002 on irq 11 
Dec  1 18:47:20 milou kernel: ide3 at 0xd800-0xd807,0xdc02 on irq 11 
Dec  1 18:47:20 milou kernel: blk: queue c0227dd4, I/O limit 4095Mb
(mask 0xffffffff) 
Dec  1 18:47:20 milou kernel: hde: 20005650 sectors (10243 MB) w/512KiB
Cache, CHS=19846/16/63, UDMA(66) 
Dec  1 18:47:20 milou kernel: blk: queue c022814c, I/O limit 4095Mb
(mask 0xffffffff) 
Dec  1 18:47:20 milou kernel: hdg: 6250608 sectors (3200 MB) w/478KiB
Cache, CHS=11024/9/63, UDMA(33) 
Dec  1 18:47:20 milou kernel: Partition check: 
Dec  1 18:47:20 milou kernel:  /dev/ide/host2/bus0/target0/lun0: [PTBL]
[1245/255/63] p1 p2 p3 p4 
Dec  1 18:47:20 milou kernel:  /dev/ide/host3/bus0/target0/lun0: p1 
Dec  1 18:47:20 milou kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann 
Dec  1 18:47:20 milou kernel: agpgart: Maximum main memory to use for
agp memory: 204M 
Dec  1 18:47:20 milou kernel: agpgart: Detected Intel 440BX chipset 
Dec  1 18:47:20 milou kernel: agpgart: AGP aperture is 256M @ 0xc0000000 
Dec  1 18:47:20 milou kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Dec  1 18:47:20 milou kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Dec  1 18:47:20 milou kernel: IP: routing cache hash table of 2048
buckets, 16Kbytes 
Dec  1 18:47:20 milou kernel: TCP: Hash tables configured (established
16384 bind 16384) 
Dec  1 18:47:20 milou kernel: NET4: Unix domain sockets 1.0/SMP for
Linux NET4.0. 
Dec  1 18:47:20 milou kernel: VFS: Mounted root (ext2 filesystem)
readonly. 
Dec  1 18:47:20 milou kernel: Mounted devfs on /dev 
Dec  1 18:47:20 milou kernel: Freeing unused kernel memory: 68k freed 
Dec  1 18:47:20 milou kernel: Adding Swap: 80316k swap-space (priority
-1) 
Dec  1 18:47:20 milou kernel: Real Time Clock Driver v1.10e 
Dec  1 18:47:20 milou kernel: es1370: version v0.37 time 18:25:27 Dec  1
2001 
Dec  1 18:47:20 milou kernel: PCI: Found IRQ 9 for device 00:09.0 
Dec  1 18:47:20 milou kernel: PCI: Sharing IRQ 9 with 00:07.2 
Dec  1 18:47:20 milou kernel: es1370: found adapter at io 0xc400 irq 9 
Dec  1 18:47:20 milou kernel: es1370: features: joystick off, line out,
mic impedance 0 
Dec  1 18:47:20 milou kernel: Serial driver version 5.05c (2001-07-08)
with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled 
Dec  1 18:47:20 milou kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Dec  1 18:47:20 milou kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Dec  1 18:47:20 milou kernel: ne2k-pci.c:v1.02 10/19/2000 D. Becker/P.
Gortmaker 
Dec  1 18:47:20 milou kernel:  
http://www.scyld.com/network/ne2k-pci.html 
Dec  1 18:47:20 milou kernel: PCI: Found IRQ 10 for device 00:0d.0 
Dec  1 18:47:20 milou kernel: eth0: RealTek RTL-8029 found at 0xc800,
IRQ 10, 00:40:05:E4:DB:3F. 
Dec  1 18:47:20 milou kernel: hdc: ATAPI CD-ROM drive, 0kB Cache, DMA 
Dec  1 18:47:20 milou kernel: Uniform CD-ROM driver Revision: 3.12 
Dec  1 18:47:20 milou kernel: parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE] 
Dec  1 18:47:20 milou kernel: parport0: cpp_daisy: aa5500ff(98) 
Dec  1 18:47:20 milou kernel: parport0: assign_addrs: aa5500ff(98) 
Dec  1 18:47:20 milou kernel: parport0: Printer, HEWLETT-PACKARD DESKJET
930C 
Dec  1 18:47:20 milou kernel: lp0: using parport0 (interrupt-driven). 

> 
> > none already mounted on /dev
> 
> Edit your /etc/fstab and remove the line for devfs. You don't
> need/want that if you have CONFIG_DEVFS_MOUNT=y.

no problem

> 
> > /dev is only a mountpoint on my system. I have no other fallback without
> > devfs but a working kernel (thanksfully there are plenty).
> >
> > > "devfs=dall" is required as well.
> >
> > No option appended (no 'devfs='). grub.
> 
> I know nothing about grub. Somehow, you need to pass "devfs=dall" to

maybe I should pass an option but so far it was working without any, as
you can see it in the command line from the log above.

> the kernel when booting. And I need to see the boot messages when this
> option is given to the kernel. If it's too verbose, you can try
> "devfs=dreg,dunreg,dfree" instead. Copy the messages down by hand if
> you need to, but I need to see them. Do yourself a favour and set up a
> serial console so you can capture boot messages easily.

I'll try my best, I like devfs.
> 
> Also, make sure you are not using any proprietary drivers (like
> NVidia). If you have such drivers, move them to another directory to

no chance

> prevent their being loaded. Even if you load but don't use such
> drivers, they still make debugging information unreliable.
> 
> I've had a look at the code, and I see no reason for devfs to fail in
> this way, unless some driver is abusing it.

I would suspect 1st devfsd. 2.4.16 is not happy at all with
devfsd-1.3.20, even rxvt fails to find a terminal.

> 
>                                 Regards,
> 
>                                         Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Pierre Rousselet writes:
> Richard Gooch wrote:
> > 
> > Pierre Rousselet writes:
> > > Richard Gooch wrote:
> > > > Indeed I do. Please Cc: me on devfs related stuff. And please apply
> > > > devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
> > > > knowing the behaviour with 2.4.17-pre1.
> > 
> > Did you apply devfs-patch-v200?
> > 
> Well, I am now back with 2.4.16 and devfsd-1.3.18. Playing with
> devfs is a risky game.

I assume if you use kernel 2.4.16 with devfsd-1.3.20 that there is no
Oops?

> I applied devfs-patch-v200 against 2.5.1-pre5 :
> And I got an oops when booting with devfsd-1.3.20. Luckily, I get the
> same oops when booting without devfsd and starting it after loging in.
> Here it is
> 
> ksymoops 2.4.3 on i686 2.5.1-pre5.  Options used
>      -V (default)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.5.1-pre5/ (default)
>      -m /usr/src/linux/System.map (default)

Did you install the appropriate System.map in /usr/src/linux? If not,
please use the -m option to specify the correct System.map file.

> > > > and boot messages. And booting with
> > >
> > > Difficult, I have no log in this case. I don't see unusual message
> > > before the oops except :
> > 
> > I need those boot messages.
> 
> Here is a log of a successful boot with devfs-patch-v200 but without
> starting devfsd. 

Well, that doesn't help. I need to see the boot messages with when it
fails. And I need the debugging output from passing "devfs=dall" to
the kernel as well.

> > > none already mounted on /dev
> > 
> > Edit your /etc/fstab and remove the line for devfs. You don't
> > need/want that if you have CONFIG_DEVFS_MOUNT=y.
> 
> no problem

I assume that didn't help. It would be helpful if you said so
explicitely.

> > > /dev is only a mountpoint on my system. I have no other fallback without
> > > devfs but a working kernel (thanksfully there are plenty).
> > >
> > > > "devfs=dall" is required as well.
> > >
> > > No option appended (no 'devfs='). grub.
> > 
> > I know nothing about grub. Somehow, you need to pass "devfs=dall" to
> 
> maybe I should pass an option but so far it was working without any,
> as you can see it in the command line from the log above.

Argh! I want to see the boot messages when "devfs=dall" is passed,
*for the failure case*! Otherwise I don't know exactly at which point
it fails, nor do I know what has happened prior to the failure point.
These kinds of bugs are usually the result of a chain of events, so I
need to see what's been going on, a step at a time. Hence
"devfs=dall".

> > the kernel when booting. And I need to see the boot messages when this
> > option is given to the kernel. If it's too verbose, you can try
> > "devfs=dreg,dunreg,dfree" instead. Copy the messages down by hand if
> > you need to, but I need to see them. Do yourself a favour and set up a
> > serial console so you can capture boot messages easily.
> 
> I'll try my best, I like devfs.

Great. That will help in getting full debugging information.

> > Also, make sure you are not using any proprietary drivers (like
> > NVidia). If you have such drivers, move them to another directory to
> 
> no chance

I'm not asking you to give up using NVidia drivers forever, but it's
very important that those drivers are not loaded until the Oops has
happened, you've captured the boot messages, run them through ksymoops
and either mailed them to me, or at the very least saved them to a
file for later emailing. By moving the NVidia drivers, you ensure that
they aren't autoloaded prior to Oops generation and debug capturing.

If you're unwilling to move those drivers elsewhere (I don't see why
this is a problem for you: you can live without them for a few
minutes), then neither I nor anyone else on this list can or will help
you. Binary-only drivers like NVidia cause no end of problems, and
kernels with them loaded (or even once loaded and then unloaded) are
not debuggable by the community. For all I know, the NVidia driver
abuses devfs in some way, and there isn't a bug in devfs itself. But
not having the source, *I can't be sure*. And since I don't know, I
can't help.

Just why are you unwilling to move those drivers?

> > prevent their being loaded. Even if you load but don't use such
> > drivers, they still make debugging information unreliable.
> > 
> > I've had a look at the code, and I see no reason for devfs to fail in
> > this way, unless some driver is abusing it.
> 
> I would suspect 1st devfsd. 2.4.16 is not happy at all with
> devfsd-1.3.20, even rxvt fails to find a terminal.

Devfsd is just a user-space process, and can't cause an Oops unless
there is a kernel bug (i.e. a devfs bug, or maybe a driver bug). I
believe that devfsd-v1.3.20 should not make it more likely to get an
Oops than when using devfsd-1.3.18. If devfsd-v1.3.20 really does
trigger an Oops while 1.3.18 doesn't then please try 1.3.19 and report
the results.

A separate issue is why rxvt doesn't work. Again, it's important to
try devfsd-v1.3.19 to see if that also breaks rxvt. If so, report and
also send a strace output of rxvt so I can see what's going wrong
there.

Finally, please try kernel 2.4.17-pre1, which has the latest version
of devfs. The 2.5.1-pre kernels have a lot of new experimental code
which could be causing some of the problems. By using 2.4.17, it
limits the changes to (mostly) devfs, so limits the variables. When
you use 2.5.1, I can't tell if there is a bug in devfs, or perhaps
some driver which is doing something illegal with devfs.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Richard Gooch wrote:

 
> I assume if you use kernel 2.4.16 with devfsd-1.3.20 that there is no
> Oops?

No there is no oops with 2.4.16, BUT I am sure CONFIG_DEBUG_KERNEL is
not set in my kernel 2.4.16. I shall try to re-compile it with it.

2.5.1-pre5 is fine as well, provided that you don't say yes to
CONFIG_DEBUG_KERNEL.

>ksymoops 2.4.3 on i686 2.5.1-pre5.  Options used
>     -V (default)
>     -k /proc/ksyms (default)
>     -l /proc/modules (default)
>     -o /lib/modules/2.5.1-pre5/ (default)
>     -m /usr/src/linux/System.map (default)
> Did you install the appropriate System.map in /usr/src/linux? If not,

I am building linux in /usr/gnu/linux. There is only one file in
/usr/src/linux, the System.map I put before running ksymoops.

> > > Edit your /etc/fstab and remove the line for devfs. You don't
> > > need/want that if you have CONFIG_DEVFS_MOUNT=y.
> >
> > no problem
> I assume that didn't help. It would be helpful if you said so
> explicitely.

I have now removed this line in fstab. It was useful when /dev had
permanent device files. With devfs only it's not needed but it doesn't
improve.
 
> I'm not asking you to give up using NVidia drivers forever, but it's
> very important that those drivers are not loaded until the Oops has
> happened, you've captured the boot messages, run them through ksymoops
> and either mailed them to me, or at the very least saved them to a
> file for later emailing. By moving the NVidia drivers, you ensure that
> they aren't autoloaded prior to Oops generation and debug capturing.
> 
> If you're unwilling to move those drivers elsewhere (I don't see why
> this is a problem for you: you can live without them for a few
> minutes), then neither I nor anyone else on this list can or will help
> you. Binary-only drivers like NVidia cause no end of problems, and
> kernels with them loaded (or even once loaded and then unloaded) are
> not debuggable by the community. For all I know, the NVidia driver
> abuses devfs in some way, and there isn't a bug in devfs itself. But
> not having the source, *I can't be sure*. And since I don't know, I
> can't help.
> 
> Just why are you unwilling to move those drivers?

You misundertood me. I would never include in the kernel a binary driver
which would break at each new release of linux. 
 
> > > prevent their being loaded. Even if you load but don't use such
> > > drivers, they still make debugging information unreliable.
> > >
> > > I've had a look at the code, and I see no reason for devfs to fail in
> > > this way, unless some driver is abusing it.
> >
> > I would suspect 1st devfsd. 2.4.16 is not happy at all with
> > devfsd-1.3.20, even rxvt fails to find a terminal.
> 
> Devfsd is just a user-space process, and can't cause an Oops unless
> there is a kernel bug (i.e. a devfs bug, or maybe a driver bug). I
> believe that devfsd-v1.3.20 should not make it more likely to get an
> Oops than when using devfsd-1.3.18. If devfsd-v1.3.20 really does
> trigger an Oops while 1.3.18 doesn't then please try 1.3.19 and report
> the results.
> 
> A separate issue is why rxvt doesn't work. Again, it's important to
> try devfsd-v1.3.19 to see if that also breaks rxvt. If so, report and
> also send a strace output of rxvt so I can see what's going wrong
> there.
> 
> Finally, please try kernel 2.4.17-pre1, which has the latest version
> of devfs. The 2.5.1-pre kernels have a lot of new experimental code
> which could be causing some of the problems. By using 2.4.17, it
> limits the changes to (mostly) devfs, so limits the variables. When
> you use 2.5.1, I can't tell if there is a bug in devfs, or perhaps
> some driver which is doing something illegal with devfs.


Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Pierre Rousselet wrote:
> 
> Richard Gooch wrote:
> 
> 
> > I assume if you use kernel 2.4.16 with devfsd-1.3.20 that there is no
> > Oops?

> > Finally, please try kernel 2.4.17-pre1, which has the latest version
> > of devfs. The 2.5.1-pre kernels have a lot of new experimental code

Here is the final (i hope) verdict of my devfs testbox :

2.4.16 with devfsd-1.3.18/1.3.20 : OK
2.4.17-pre1         "            : Broken
2.5.1-pre1          "            : OK
2.5.1-pre2 with or without v200  : Broken
2.5.1-pre5          "            : Broken

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Alexander Viro]

On Sun, 2 Dec 2001, Pierre Rousselet wrote:

> Here is the final (i hope) verdict of my devfs testbox :
> 
> 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> 2.4.17-pre1         "            : Broken
> 2.5.1-pre1          "            : OK
> 2.5.1-pre2 with or without v200  : Broken
> 2.5.1-pre5          "            : Broken

IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT).

We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set.  Otherwise
we'll be getting tons of bug reports due to silent memory corruption.

Keith, is there a decent way to do that?  For 2.4.17 it would help a lot...

Re: 2.5.1-pre5 not easy to boot with devfs

[Alan Cox]

> > Here is the final (i hope) verdict of my devfs testbox :
> > 
> > 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> > 2.4.17-pre1         "            : Broken
> > 2.5.1-pre1          "            : OK

Sounds like the new devfs code should be backed out of 2.4 until fixed
in 2.5 

Alan

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Alan Cox writes:
> > > Here is the final (i hope) verdict of my devfs testbox :
> > > 
> > > 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> > > 2.4.17-pre1         "            : Broken
> > > 2.5.1-pre1          "            : OK
> 
> Sounds like the new devfs code should be backed out of 2.4 until
> fixed in 2.5

Hey! It's a pre-patch. There's time before 2.4.17-rc is released.
Having it in a pre-patch is the only way to get decent testing,
unfortunately. Not enough people bother downloading extra patches.
All known issues were resolved before the merge.

And 2.5 isn't going to get a lot of testing until the breakage caused
by the bio changes is fixed. At the moment, I can't even test it
myself.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Jens Axboe]

On Sun, Dec 02 2001, Richard Gooch wrote:
> And 2.5 isn't going to get a lot of testing until the breakage caused
> by the bio changes is fixed. At the moment, I can't even test it
> myself.

I'll just go read your bug rapport and fix it right up.

-- 
Jens Axboe

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Jens Axboe writes:
> On Sun, Dec 02 2001, Richard Gooch wrote:
> > And 2.5 isn't going to get a lot of testing until the breakage caused
> > by the bio changes is fixed. At the moment, I can't even test it
> > myself.
> 
> I'll just go read your bug rapport and fix it right up.

It wasn't meant as a criticism of the changes. I'm glad to see someone
working on fixing the bio layer. It's just not ready for widespread
testing yet (crude measurement: if it breaks for me, it's not ready
for the masses ;-). Once I surface from this round of devfs cleanups,
I'll pause for breath and try again with 2.5. If I still have
problems, I'll let you know.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Jens Axboe]

On Mon, Dec 03 2001, Richard Gooch wrote:
> Jens Axboe writes:
> > On Sun, Dec 02 2001, Richard Gooch wrote:
> > > And 2.5 isn't going to get a lot of testing until the breakage caused
> > > by the bio changes is fixed. At the moment, I can't even test it
> > > myself.
> > 
> > I'll just go read your bug rapport and fix it right up.
> 
> It wasn't meant as a criticism of the changes. I'm glad to see someone
> working on fixing the bio layer. It's just not ready for widespread
> testing yet (crude measurement: if it breaks for me, it's not ready
> for the masses ;-). Once I surface from this round of devfs cleanups,
> I'll pause for breath and try again with 2.5. If I still have
> problems, I'll let you know.

No seriously, I want to know if something is broken so it can get fixed.
bio core is indeed stable, if something breaks it's drivers. And they
need fixing right away.

At least until I break every single block driver out there again in a
few days. And no, I'm not kidding.

-- 
Jens Axboe

Re: 2.5.1-pre5 not easy to boot with devfs

[Keith Owens]

On Sun, 2 Dec 2001 11:59:34 -0500 (EST), 
Alexander Viro <viro@math.psu.edu> wrote:
>On Sun, 2 Dec 2001, Pierre Rousselet wrote:
>
>> Here is the final (i hope) verdict of my devfs testbox :
>> 
>> 2.4.16 with devfsd-1.3.18/1.3.20 : OK
>> 2.4.17-pre1         "            : Broken
>> 2.5.1-pre1          "            : OK
>> 2.5.1-pre2 with or without v200  : Broken
>> 2.5.1-pre5          "            : Broken
>
>IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT).
>
>We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set.  Otherwise
>we'll be getting tons of bug reports due to silent memory corruption.
>
>Keith, is there a decent way to do that?  For 2.4.17 it would help a lot...

Against 2.4.17-pre2, untested.  Revert before 2.4.17.

Index: 17-pre2.1/fs/Config.in
--- 17-pre2.1/fs/Config.in Tue, 13 Nov 2001 08:45:38 +1100 kaos (linux-2.4/m/b/39_Config.in 1.2.1.2.1.7 644)
+++ 17-pre2.1(w)/fs/Config.in Mon, 03 Dec 2001 09:54:58 +1100 kaos (linux-2.4/m/b/39_Config.in 1.2.1.2.1.7 644)
@@ -63,7 +63,10 @@ bool '/proc file system support' CONFIG_
 
 dep_bool '/dev file system support (EXPERIMENTAL)' CONFIG_DEVFS_FS $CONFIG_EXPERIMENTAL
 dep_bool '  Automatically mount at boot' CONFIG_DEVFS_MOUNT $CONFIG_DEVFS_FS
-dep_bool '  Debug devfs' CONFIG_DEVFS_DEBUG $CONFIG_DEVFS_FS
+if [ "$CONFIG_DEVFS_FS" = "y" ] ; then \
+   define_bool CONFIG_DEVFS_DEBUG y
+fi
+# dep_bool '  Debug devfs' CONFIG_DEVFS_DEBUG $CONFIG_DEVFS_FS
 
 # It compiles as a module for testing only.  It should not be used
 # as a module in general.  If we make this "tristate", a bunch of people

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

I think the point is to force CONFIG_DEBUG_KERNEL CONFIG_DEBUG_SLAB ...

DEVFS_DEBUG is quite verbose when enabled by devfs=dall : dmesg shows
15kb of devfs messages with no room for anything else.


Keith Owens wrote:
> 
> On Sun, 2 Dec 2001 11:59:34 -0500 (EST),
> Alexander Viro <viro@math.psu.edu> wrote:
> >On Sun, 2 Dec 2001, Pierre Rousselet wrote:
> >
> >> Here is the final (i hope) verdict of my devfs testbox :
> >>
> >> 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> >> 2.4.17-pre1         "            : Broken
> >> 2.5.1-pre1          "            : OK
> >> 2.5.1-pre2 with or without v200  : Broken
> >> 2.5.1-pre5          "            : Broken
> >
> >IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT).
> >
> >We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set.  Otherwise
> >we'll be getting tons of bug reports due to silent memory corruption.
> >
> >Keith, is there a decent way to do that?  For 2.4.17 it would help a lot...
> 
> Against 2.4.17-pre2, untested.  Revert before 2.4.17.
> 
> Index: 17-pre2.1/fs/Config.in
> --- 17-pre2.1/fs/Config.in Tue, 13 Nov 2001 08:45:38 +1100 kaos (linux-2.4/m/b/39_Config.in 1.2.1.2.1.7 644)
> +++ 17-pre2.1(w)/fs/Config.in Mon, 03 Dec 2001 09:54:58 +1100 kaos (linux-2.4/m/b/39_Config.in 1.2.1.2.1.7 644)
> @@ -63,7 +63,10 @@ bool '/proc file system support' CONFIG_
> 
>  dep_bool '/dev file system support (EXPERIMENTAL)' CONFIG_DEVFS_FS $CONFIG_EXPERIMENTAL
>  dep_bool '  Automatically mount at boot' CONFIG_DEVFS_MOUNT $CONFIG_DEVFS_FS
> -dep_bool '  Debug devfs' CONFIG_DEVFS_DEBUG $CONFIG_DEVFS_FS
> +if [ "$CONFIG_DEVFS_FS" = "y" ] ; then \
> +   define_bool CONFIG_DEVFS_DEBUG y
> +fi
> +# dep_bool '  Debug devfs' CONFIG_DEVFS_DEBUG $CONFIG_DEVFS_FS
> 
>  # It compiles as a module for testing only.  It should not be used
>  # as a module in general.  If we make this "tristate", a bunch of people

-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Alexander Viro writes:
> 
> 
> On Sun, 2 Dec 2001, Pierre Rousselet wrote:
> 
> > Here is the final (i hope) verdict of my devfs testbox :
> > 
> > 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> > 2.4.17-pre1         "            : Broken
> > 2.5.1-pre1          "            : OK
> > 2.5.1-pre2 with or without v200  : Broken
> > 2.5.1-pre5          "            : Broken
> 
> IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT).
> 
> We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set.  Otherwise
> we'll be getting tons of bug reports due to silent memory corruption.
> 
> Keith, is there a decent way to do that?  For 2.4.17 it would help a
> lot...

Is that worth the effort? Hopefully by 2.4.17-rc I'll have fixed the
bug, so it won't be an issue.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Alexander Viro]

On Sun, 2 Dec 2001, Richard Gooch wrote:

> Is that worth the effort? Hopefully by 2.4.17-rc I'll have fixed the
> bug, so it won't be an issue.

<boggle>

Let me get it straight - you had just merged an alpha-quality code into
the tree.  It has a chance to get debugged, but right now we have a _big_
change turning a lot of allocations into dynamic, yodda, yodda.  And it's
one big step - not split into gradual massage of code.  And you expect
that there will be no leaks/dangling pointers aside of that one?

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Richard Gooch wrote:


> I assume if you use kernel 2.4.16 with devfsd-1.3.20 that there is no
> Oops?

2.4.16 not patched, with debug options below, is booting nicely with
devfsd-v1.3.18 or devfsd-v1.3.20. I don't succeed to reproduce the
problem with rxvt nor xterm.

CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_DEVFS_DEBUG=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_BUGVERBOSE=y

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

  I should also point out that you need to compile with
CONFIG_DEVFS_DEBUG=y. Otherwise passing "devfs=dall" will have no
effect.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

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

Richard Gooch wrote:
> 
>   I should also point out that you need to compile with
> CONFIG_DEVFS_DEBUG=y. Otherwise passing "devfs=dall" will have no
> effect.

2.5.1-pre5 with devfs-patch-v200
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_DEVFS_DEBUG=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_BUGVERBOSE=y

The oops comes shortly after booting, loging in, starting devfsd-v1.3.20
and playing with mc.
The attached file is the same; it may be easier to read. The last line
is the last entry of the log before <SysRq U>, <SysRq B>.


Dec  2 07:39:29 milou kernel: devfs: devfs_unregister(): de->name: "s3"
de: cf6ddf3c 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dentry: cf6c4c8c 
inode: cf6c1a0c  devfs_entry: c14d0a94 
Dec  2 07:39:29 milou kernel: devfs: unlink(ttyp3) 
Dec  2 07:39:29 milou kernel: devfs: d_iput(): dentry: cf45d654 inode:
cf378454 de: cf6ddd1c  de->dentry: cf45d654 
Dec  2 07:39:29 milou kernel: devfs: devfs_put(ttyp3): de: cf6ddd1c,
parent: c1419724 "" 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dropping negative
dentry: cf45d654 
Dec  2 07:39:29 milou kernel: devfs: d_release(): dentry: cf45d654
inode: 00000000 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dentry: cf45d5e0 
inode: cf37826c  devfs_entry: cf6ddf3c 
Dec  2 07:39:29 milou kernel: devfs: d_iput(): dentry: cf45d5e0 inode:
cf37826c de: cf6ddf3c  de->dentry: cf45d5e0 
Dec  2 07:39:29 milou kernel: devfs: devfs_put(s3): de: cf6ddf3c,
parent: c14d0874 "pty" 
Dec  2 07:39:29 milou kernel: devfs: d_release(): dentry: cf45d5e0
inode: 00000000 
Dec  2 07:39:32 milou kernel: devfs: devfs_unregister(): de->name: "s2"
de: cf6da18c 
Dec  2 07:39:32 milou kernel: devfs: d_delete(): dentry: cf6c4ba4 
inode: cf6c163c  devfs_entry: c14d0a0c 
Dec  2 07:39:32 milou kernel: devfs: d_delete(): dentry: cf45d410 
inode: cf463bd4  devfs_entry: cf6da18c 
Dec  2 07:39:32 milou kernel: devfs: d_iput(): dentry: cf45d410 inode:
cf463bd4 de: cf6da18c  de->dentry: cf45d410 
Dec  2 07:39:32 milou kernel: devfs: d_release(): dentry: cf45d410
inode: 00000000 
Dec  2 07:39:32 milou kernel: devfs: devfs_put(s2): de: cf6da18c,
parent: c14d0874 "pty" 
Dec  2 07:39:32 milou kernel: Unable to handle kernel paging request at
virtual address 5a5a5a5e 
Dec  2 07:39:32 milou kernel:  printing eip: 
Dec  2 07:39:32 milou kernel: c01516f9 
Dec  2 07:39:32 milou kernel: *pde = 00000000 
Dec  2 07:39:32 milou kernel: Oops: 0002 
Dec  2 07:39:32 milou kernel: CPU:    0 
Dec  2 07:39:32 milou kernel: EIP:    0010:[devfs_put+13/296]    Not
tainted 
Dec  2 07:39:32 milou kernel: EFLAGS: 00010206 
Dec  2 07:39:32 milou kernel: eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx:
00000001   edx: 5a5a5a5a 
Dec  2 07:39:32 milou kernel: esi: 00000000   edi: 00000027   ebp:
00000000   esp: cf657f40 
Dec  2 07:39:32 milou kernel: ds: 0018   es: 0018   ss: 0018 
Dec  2 07:39:32 milou kernel: Process devfsd-new (pid: 130,
stackpage=cf657000) 
Dec  2 07:39:32 milou kernel: Stack: 00000027 c015465c 5a5a5a5a cf978484
ffffffea 00000000 00000420 cfb97800  
Dec  2 07:39:32 milou kernel:        c01e7f40 cf4fc224 5a5a5a5a 000003f9
00000000 00000000 00000001 00000000  
Dec  2 07:39:32 milou kernel:        cf656000 00000000 00000000 00000000
cf656000 c01e7f6c c01e7f6c c012f5e6  
Dec  2 07:39:32 milou kernel: Call Trace: [devfsd_read+856/976]
[sys_read+150/204] [system_call+51/56]  
Dec  2 07:39:32 milou kernel:  
Dec  2 07:39:32 milou kernel: Code: ff 4b 04 0f 94 c0 84 c0 0f 84 09 01
00 00 3b 1d 00 15 21 c0  
Dec  2 07:39:39 milou kernel:  devfs: devfs_unregister(): de->name: "s1"
de: cf6da3ac 
Dec  2 07:39:39 milou kernel: devfs: d_delete(): dentry: cf6c4abc 
inode: cf6c126c  devfs_entry: c14d0984 
Dec  2 07:39:39 milou kernel: devfs: d_delete(): dentry: cf45d240 
inode: cf46361c  devfs_entry: cf6da3ac 
Dec  2 07:39:39 milou kernel: devfs: d_iput(): dentry: cf45d240 inode:
cf46361c de: cf6da3ac  de->dentry: cf45d240 
Dec  2 07:39:39 milou kernel: devfs: d_release(): dentry: cf45d240
inode: 00000000 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cff25294 
inode: cff2122c  devfs_entry: c14d512c 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf6cbe3c 
inode: cf6c50a4  devfs_entry: c15d45ac 
Dec  2 07:39:42 milou kernel: devfs: devfs_unregister(): de->name: "s0"
de: cf6da5cc 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf6c49d4 
inode: cf6c2dbc  devfs_entry: c14d08fc 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf620d00 
inode: cf52824c  devfs_entry: cf6da5cc 
Dec  2 07:39:42 milou kernel: devfs: d_iput(): dentry: cf620d00 inode:
cf52824c de: cf6da5cc  de->dentry: cf620d00 
Dec  2 07:39:42 milou kernel: devfs: d_release(): dentry: cf620d00
inode: 00000000 
Dec  2 07:39:56 milou kernel: devfs: d_delete(): dentry: cf6cbeb0 
inode: cf6c528c  devfs_entry: cf6c625c 
Dec  2 07:39:56 milou kernel: devfs: lookup(ptmx): dentry: cf620878
parent: c1419724 by: "mc" 



-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

[-- Attachment #2: Oops-devfs-v200-2.5.1-pre5 --]
[-- Type: text/plain, Size: 4361 bytes --]

Dec  2 07:39:29 milou kernel: devfs: devfs_unregister(): de->name: "s3" de: cf6ddf3c 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dentry: cf6c4c8c  inode: cf6c1a0c  devfs_entry: c14d0a94 
Dec  2 07:39:29 milou kernel: devfs: unlink(ttyp3) 
Dec  2 07:39:29 milou kernel: devfs: d_iput(): dentry: cf45d654 inode: cf378454 de: cf6ddd1c  de->dentry: cf45d654 
Dec  2 07:39:29 milou kernel: devfs: devfs_put(ttyp3): de: cf6ddd1c, parent: c1419724 "" 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dropping negative dentry: cf45d654 
Dec  2 07:39:29 milou kernel: devfs: d_release(): dentry: cf45d654 inode: 00000000 
Dec  2 07:39:29 milou kernel: devfs: d_delete(): dentry: cf45d5e0  inode: cf37826c  devfs_entry: cf6ddf3c 
Dec  2 07:39:29 milou kernel: devfs: d_iput(): dentry: cf45d5e0 inode: cf37826c de: cf6ddf3c  de->dentry: cf45d5e0 
Dec  2 07:39:29 milou kernel: devfs: devfs_put(s3): de: cf6ddf3c, parent: c14d0874 "pty" 
Dec  2 07:39:29 milou kernel: devfs: d_release(): dentry: cf45d5e0 inode: 00000000 
Dec  2 07:39:32 milou kernel: devfs: devfs_unregister(): de->name: "s2" de: cf6da18c 
Dec  2 07:39:32 milou kernel: devfs: d_delete(): dentry: cf6c4ba4  inode: cf6c163c  devfs_entry: c14d0a0c 
Dec  2 07:39:32 milou kernel: devfs: d_delete(): dentry: cf45d410  inode: cf463bd4  devfs_entry: cf6da18c 
Dec  2 07:39:32 milou kernel: devfs: d_iput(): dentry: cf45d410 inode: cf463bd4 de: cf6da18c  de->dentry: cf45d410 
Dec  2 07:39:32 milou kernel: devfs: d_release(): dentry: cf45d410 inode: 00000000 
Dec  2 07:39:32 milou kernel: devfs: devfs_put(s2): de: cf6da18c, parent: c14d0874 "pty" 
Dec  2 07:39:32 milou kernel: Unable to handle kernel paging request at virtual address 5a5a5a5e 
Dec  2 07:39:32 milou kernel:  printing eip: 
Dec  2 07:39:32 milou kernel: c01516f9 
Dec  2 07:39:32 milou kernel: *pde = 00000000 
Dec  2 07:39:32 milou kernel: Oops: 0002 
Dec  2 07:39:32 milou kernel: CPU:    0 
Dec  2 07:39:32 milou kernel: EIP:    0010:[devfs_put+13/296]    Not tainted 
Dec  2 07:39:32 milou kernel: EFLAGS: 00010206 
Dec  2 07:39:32 milou kernel: eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000001   edx: 5a5a5a5a 
Dec  2 07:39:32 milou kernel: esi: 00000000   edi: 00000027   ebp: 00000000   esp: cf657f40 
Dec  2 07:39:32 milou kernel: ds: 0018   es: 0018   ss: 0018 
Dec  2 07:39:32 milou kernel: Process devfsd-new (pid: 130, stackpage=cf657000) 
Dec  2 07:39:32 milou kernel: Stack: 00000027 c015465c 5a5a5a5a cf978484 ffffffea 00000000 00000420 cfb97800  
Dec  2 07:39:32 milou kernel:        c01e7f40 cf4fc224 5a5a5a5a 000003f9 00000000 00000000 00000001 00000000  
Dec  2 07:39:32 milou kernel:        cf656000 00000000 00000000 00000000 cf656000 c01e7f6c c01e7f6c c012f5e6  
Dec  2 07:39:32 milou kernel: Call Trace: [devfsd_read+856/976] [sys_read+150/204] [system_call+51/56]  
Dec  2 07:39:32 milou kernel:  
Dec  2 07:39:32 milou kernel: Code: ff 4b 04 0f 94 c0 84 c0 0f 84 09 01 00 00 3b 1d 00 15 21 c0  
Dec  2 07:39:39 milou kernel:  devfs: devfs_unregister(): de->name: "s1" de: cf6da3ac 
Dec  2 07:39:39 milou kernel: devfs: d_delete(): dentry: cf6c4abc  inode: cf6c126c  devfs_entry: c14d0984 
Dec  2 07:39:39 milou kernel: devfs: d_delete(): dentry: cf45d240  inode: cf46361c  devfs_entry: cf6da3ac 
Dec  2 07:39:39 milou kernel: devfs: d_iput(): dentry: cf45d240 inode: cf46361c de: cf6da3ac  de->dentry: cf45d240 
Dec  2 07:39:39 milou kernel: devfs: d_release(): dentry: cf45d240 inode: 00000000 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cff25294  inode: cff2122c  devfs_entry: c14d512c 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf6cbe3c  inode: cf6c50a4  devfs_entry: c15d45ac 
Dec  2 07:39:42 milou kernel: devfs: devfs_unregister(): de->name: "s0" de: cf6da5cc 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf6c49d4  inode: cf6c2dbc  devfs_entry: c14d08fc 
Dec  2 07:39:42 milou kernel: devfs: d_delete(): dentry: cf620d00  inode: cf52824c  devfs_entry: cf6da5cc 
Dec  2 07:39:42 milou kernel: devfs: d_iput(): dentry: cf620d00 inode: cf52824c de: cf6da5cc  de->dentry: cf620d00 
Dec  2 07:39:42 milou kernel: devfs: d_release(): dentry: cf620d00 inode: 00000000 
Dec  2 07:39:56 milou kernel: devfs: d_delete(): dentry: cf6cbeb0  inode: cf6c528c  devfs_entry: cf6c625c 
Dec  2 07:39:56 milou kernel: devfs: lookup(ptmx): dentry: cf620878 parent: c1419724 by: "mc" 

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Pierre Rousselet writes:
> The oops comes shortly after booting, loging in, starting devfsd-v1.3.20
> and playing with mc.
> The attached file is the same; it may be easier to read. The last line
> is the last entry of the log before <SysRq U>, <SysRq B>.
> 
> Dec  2 07:39:29 milou kernel: devfs: devfs_unregister(): de->name: "s3"
> de: cf6ddf3c 
> Dec  2 07:39:29 milou kernel: devfs: d_delete(): dentry: cf6c4c8c 
> inode: cf6c1a0c  devfs_entry: c14d0a94 
[...]

This isn't the complete kernel messages! You've edited it. These first
two lines should be related, yet the devfs entries are different. If I
had the complete kernel messages, I could see what devfs_entry
c14d0a94 is supposed to be. And there might be other clues related to
the dentry values. Also, please changed the second printk() in
devfs_d_delete() to this:
    if (devfs_debug & DEBUG_D_DELETE)
	printk ("%s: d_delete(%s): dentry: %p  inode: %p  devfs_entry: %p pp: %p \"%s\"\n",
		DEVFS_NAME, de->name, dentry, inode, de, de->parent, de->parent->name);


Please, edit nothing. If the output is big, just send it to me so you
don't spam the list.

Also, please send me the output of lsmod prior to the Oops.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

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

Richard Gooch wrote:
> 
> Pierre Rousselet writes:
> > Richard Gooch wrote:
> > > Indeed I do. Please Cc: me on devfs related stuff. And please apply
> > > devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
> > > knowing the behaviour with 2.4.17-pre1.

Same looking Oops with 2.4.17-pre1 as with 2.5.1-pre5. A log with devfs
debug message is attached. I was able to reboot from the command line
after this oops.

Dec  2 10:04:31 milou kernel: Unable to handle kernel paging request at
virtual address 5a5a5a5e 
Dec  2 10:04:31 milou kernel: c014f509 
Dec  2 10:04:31 milou kernel: *pde = 00000000 
Dec  2 10:04:31 milou kernel: Oops: 0002 
Dec  2 10:04:31 milou kernel: CPU:    0 
Dec  2 10:04:31 milou kernel: EIP:    0010:[ext2_remount+105/312]    Not
tainted 
Dec  2 10:04:31 milou kernel: EFLAGS: 00010206 
Dec  2 10:04:31 milou kernel: eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx:
0000000b   edx: 5a5a5a5a 
Dec  2 10:04:31 milou kernel: esi: 00000000   edi: 00000027   ebp:
00000000   esp: c7f61f40 
Dec  2 10:04:31 milou kernel: ds: 0018   es: 0018   ss: 0018 
Dec  2 10:04:31 milou kernel: Process devfsd (pid: 129,
stackpage=c7f61000) 
Dec  2 10:04:31 milou kernel: Stack: 00000027 c015246c 5a5a5a5a c8282414
ffffffea 00000000 00000420 c847a800  
Dec  2 10:04:31 milou kernel:        c01e5280 c7e16224 5a5a5a5a 000003f9
00000000 00000000 00000001 00000000  
Dec  2 10:04:31 milou kernel:        c7f60000 00000000 00000000 00000000
c7f60000 c01e52ac c01e52ac c012e926  
Dec  2 10:04:31 milou kernel: Call Trace: [devfs_read_super+144/212]
[sys_read+150/204] [system_call+51/56]  
Dec  2 10:04:31 milou kernel: Code: ff 4b 04 0f 94 c0 84 c0 0f 84 09 01
00 00 3b 1d 40 e4 20 c0  
Using defaults from ksymoops -t elf32-i386 -a i386

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   ff 4b 04                  decl   0x4(%ebx)
Code;  00000002 Before first symbol
   3:   0f 94 c0                  sete   %al
Code;  00000006 Before first symbol
   6:   84 c0                     test   %al,%al
Code;  00000008 Before first symbol
   8:   0f 84 09 01 00 00         je     117 <_EIP+0x117> 00000116
Before first symbol
Code;  0000000e Before first symbol
   e:   3b 1d 40 e4 20 c0         cmp    0xc020e440,%ebx


Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

[-- Attachment #2: oops-2.4.17-pre1 --]
[-- Type: text/plain, Size: 11494 bytes --]

Dec  2 10:03:33 milou kernel: devfs: d_delete(): dentry: c7f41a48  inode: c7e6f9cc  devfs_entry: c7fe75cc 
Dec  2 10:04:21 milou kernel: devfs: lookup(ptmx): dentry: c7d96d94 parent: c1419724 by: "mc" 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dropping negative dentry: c7d96d94 
Dec  2 10:04:21 milou kernel: devfs: d_release(): dentry: c7d96d94 inode: 00000000 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7fd78cc  inode: c7fd4804  devfs_entry: c7fd30c4 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7fd79b4  inode: c7fd4bd4  devfs_entry: c7fd314c 
Dec  2 10:04:21 milou kernel: devfs: devfs_register(pty/s1): de: c7fe74bc dir: c14db8dc "pty"  pp: c1419724 
Dec  2 10:04:21 milou kernel: devfs: lookup(ttyp1): dentry: c7d96d94 parent: c1419724 by: "devfsd" 
Dec  2 10:04:21 milou kernel: devfs: devfs_do_symlink(ttyp1) 
Dec  2 10:04:21 milou kernel: devfs: get_vfs_inode(817): VFS inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs:   mode: 0120555  uid: 0  gid: 0 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs: lookup(s1): dentry: c7d96e7c parent: c14db8dc by: "mc" 
Dec  2 10:04:21 milou kernel: devfs: get_vfs_inode(816): VFS inode: c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:21 milou kernel: devfs:   mode: 020600  uid: 0  gid: 0 
Dec  2 10:04:21 milou kernel: devfs: lookup(): new VFS inode(816): c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96e7c  inode: c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96e7c  inode: c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96e7c  inode: c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:21 milou kernel: devfs: d_delete(): dentry: c7d96d94  inode: c7d9c9cc  devfs_entry: c7fe73ac 
Dec  2 10:04:26 milou kernel: devfs: devfs_unregister(): de->name: "s1" de: c7fe74bc 
Dec  2 10:04:26 milou kernel: devfs: d_delete(): dentry: c7fd7940  inode: c7fd49ec  devfs_entry: c14db9ec 
Dec  2 10:04:26 milou kernel: devfs: unlink(ttyp1) 
Dec  2 10:04:26 milou kernel: devfs: d_iput(): dentry: c7d96d94 inode: c7d9c9cc de: c7fe73ac  de->dentry: c7d96d94 
Dec  2 10:04:26 milou kernel: devfs: devfs_put(ttyp1): de: c7fe73ac, parent: c1419724 "" 
Dec  2 10:04:26 milou kernel: devfs: d_delete(): dropping negative dentry: c7d96d94 
Dec  2 10:04:26 milou kernel: devfs: d_release(): dentry: c7d96d94 inode: 00000000 
Dec  2 10:04:26 milou kernel: devfs: d_delete(): dentry: c7d96e7c  inode: c7d9c7e4  devfs_entry: c7fe74bc 
Dec  2 10:04:26 milou kernel: devfs: d_iput(): dentry: c7d96e7c inode: c7d9c7e4 de: c7fe74bc  de->dentry: c7d96e7c 
Dec  2 10:04:26 milou kernel: devfs: devfs_put(s1): de: c7fe74bc, parent: c14db8dc "pty" 
Dec  2 10:04:26 milou kernel: devfs: d_release(): dentry: c7d96e7c inode: 00000000 
Dec  2 10:04:31 milou kernel: devfs: d_delete(): dentry: cff34138  inode: cff6cc14  devfs_entry: c14ea23c 
Dec  2 10:04:31 milou kernel: devfs: d_delete(): dentry: c7f74634  inode: c7f73bf4  devfs_entry: c15e86bc 
Dec  2 10:04:31 milou kernel: devfs: devfs_unregister(): de->name: "s0" de: c7fe76dc 
Dec  2 10:04:31 milou kernel: devfs: d_delete(): dentry: c7fd7858  inode: c7fd461c  devfs_entry: c14db964 
Dec  2 10:04:31 milou kernel: devfs: d_delete(): dentry: c7f41ba4  inode: c7e6fbb4  devfs_entry: c7fe76dc 
Dec  2 10:04:31 milou kernel: devfs: d_iput(): dentry: c7f41ba4 inode: c7e6fbb4 de: c7fe76dc  de->dentry: c7f41ba4 
Dec  2 10:04:31 milou kernel: devfs: d_release(): dentry: c7f41ba4 inode: 00000000 
Dec  2 10:04:31 milou kernel: devfs: devfs_put(s0): de: c7fe76dc, parent: c14db8dc "pty" 
Dec  2 10:04:31 milou kernel: Unable to handle kernel paging request at virtual address 5a5a5a5e 
Dec  2 10:04:31 milou kernel:  printing eip: 
Dec  2 10:04:31 milou kernel: c014f509 
Dec  2 10:04:31 milou kernel: *pde = 00000000 
Dec  2 10:04:31 milou kernel: Oops: 0002 
Dec  2 10:04:31 milou kernel: CPU:    0 
Dec  2 10:04:31 milou kernel: EIP:    0010:[ext2_remount+105/312]    Not tainted 
Dec  2 10:04:31 milou kernel: EFLAGS: 00010206 
Dec  2 10:04:31 milou kernel: eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 0000000b   edx: 5a5a5a5a 
Dec  2 10:04:31 milou kernel: esi: 00000000   edi: 00000027   ebp: 00000000   esp: c7f61f40 
Dec  2 10:04:31 milou kernel: ds: 0018   es: 0018   ss: 0018 
Dec  2 10:04:31 milou kernel: Process devfsd (pid: 129, stackpage=c7f61000) 
Dec  2 10:04:31 milou kernel: Stack: 00000027 c015246c 5a5a5a5a c8282414 ffffffea 00000000 00000420 c847a800  
Dec  2 10:04:31 milou kernel:        c01e5280 c7e16224 5a5a5a5a 000003f9 00000000 00000000 00000001 00000000  
Dec  2 10:04:31 milou kernel:        c7f60000 00000000 00000000 00000000 c7f60000 c01e52ac c01e52ac c012e926  
Dec  2 10:04:31 milou kernel: Call Trace: [devfs_read_super+144/212] [sys_read+150/204] [system_call+51/56]  
Dec  2 10:04:31 milou kernel:  
Dec  2 10:04:31 milou kernel: Code: ff 4b 04 0f 94 c0 84 c0 0f 84 09 01 00 00 3b 1d 40 e4 20 c0  
Dec  2 10:04:53 milou kernel:  devfs: d_delete(): dentry: c141b4b8  inode: c155d434  devfs_entry: c14ea2c4 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c141b4b8  inode: c155d434  devfs_entry: c14ea2c4 
Dec  2 10:04:53 milou last message repeated 6 times
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "6" de: c84799cc 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74e5c  inode: c7f70064  devfs_entry: c84799cc 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74e5c inode: c7f70064 de: c84799cc  de->dentry: c7f74e5c 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74e5c inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "a6" de: c8479a54 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74f44  inode: c7f70434  devfs_entry: c8479a54 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74f44 inode: c7f70434 de: c8479a54  de->dentry: c7f74f44 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74f44 inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c8306b30  inode: c8319a2c  devfs_entry: c14ea67c 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "5" de: c15f69ec 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74abc  inode: c7f71044  devfs_entry: c15f69ec 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74abc inode: c7f71044 de: c15f69ec  de->dentry: c7f74abc 
Dec  2 10:04:53 milou init: Switching to runlevel: 6
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74abc inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "a5" de: c15f6eb4 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74ba4  inode: c7f71414  devfs_entry: c15f6eb4 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74ba4 inode: c7f71414 de: c15f6eb4  de->dentry: c7f74ba4 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74ba4 inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c8306abc  inode: c8319844  devfs_entry: c14ea5f4 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "4" de: c15f6a74 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74c8c  inode: c7f717e4  devfs_entry: c15f6a74 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74c8c inode: c7f717e4 de: c15f6a74  de->dentry: c7f74c8c 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74c8c inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "a4" de: c8479944 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74d74  inode: c7f71bb4  devfs_entry: c8479944 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74d74 inode: c7f71bb4 de: c8479944  de->dentry: c7f74d74 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74d74 inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c8306a48  inode: c831965c  devfs_entry: c14ea56c 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "3" de: c15f6e2c 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f748ec  inode: c7f72844  devfs_entry: c15f6e2c 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f748ec inode: c7f72844 de: c15f6e2c  de->dentry: c7f748ec 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f748ec inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "a3" de: c15f6d1c 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f749d4  inode: c7f72c14  devfs_entry: c15f6d1c 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f749d4 inode: c7f72c14 de: c15f6d1c  de->dentry: c7f749d4 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f749d4 inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c83069d4  inode: c8319474  devfs_entry: c14ea4e4 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "2" de: c15f6da4 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f7471c  inode: c7f720a4  devfs_entry: c15f6da4 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f7471c inode: c7f720a4 de: c15f6da4  de->dentry: c7f7471c 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f7471c inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: devfs_unregister(): de->name: "a2" de: c15f6f3c 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c7f74804  inode: c7f72474  devfs_entry: c15f6f3c 
Dec  2 10:04:53 milou kernel: devfs: d_iput(): dentry: c7f74804 inode: c7f72474 de: c15f6f3c  de->dentry: c7f74804 
Dec  2 10:04:53 milou kernel: devfs: d_release(): dentry: c7f74804 inode: 00000000 
Dec  2 10:04:53 milou kernel: devfs: d_delete(): dentry: c8306960  inode: c831928c  devfs_entry: c14ea45c 
Dec  2 10:04:58 milou kernel: devfs: d_delete(): dentry: c141b4b8  inode: c155d434  devfs_entry: c14ea2c4 
Dec  2 10:04:58 milou last message repeated 2 times
Dec  2 10:04:58 milou kernel: devfs: devfs_unregister(): de->name: "1" de: c15e8634 
Dec  2 10:04:58 milou kernel: devfs: d_delete(): dentry: c7f7454c  inode: c7f73824  devfs_entry: c15e8634 
Dec  2 10:04:58 milou kernel: devfs: d_iput(): dentry: c7f7454c inode: c7f73824 de: c15e8634  de->dentry: c7f7454c 
Dec  2 10:04:58 milou kernel: devfs: d_release(): dentry: c7f7454c inode: 00000000 
Dec  2 10:04:58 milou kernel: devfs: devfs_unregister(): de->name: "a1" de: c15e86bc 
Dec  2 10:04:58 milou kernel: devfs: d_delete(): dentry: c7f74634  inode: c7f73bf4  devfs_entry: c15e86bc 
Dec  2 10:04:58 milou kernel: devfs: d_iput(): dentry: c7f74634 inode: c7f73bf4 de: c15e86bc  de->dentry: c7f74634 
Dec  2 10:04:58 milou kernel: devfs: d_release(): dentry: c7f74634 inode: 00000000 
Dec  2 10:04:58 milou kernel: devfs: d_delete(): dentry: c83068ec  inode: c83190a4  devfs_entry: c14ea3d4 
Dec  2 10:04:59 milou kernel: devfs: devfs_register(1): de: c7fe729c dir: c14d1ba4 "vcc"  pp: c1419724 
Dec  2 10:04:59 milou exiting on signal 15

Re: 2.5.1-pre5 not easy to boot with devfs

[Richard Gooch]

Pierre Rousselet writes:
> As far as I can see,
> 
> when CONFIG_DEBUG_KERNEL is set
>   and 
> when devfsd is started at boot time
> I get an Oops when remounting, rw the root fs :
> 
> Unable to handle kernel request at va 5a5a5a5e
> ...
> EIP: 0010:[<c01516f9>] Not tainted
> ...
> Process devfsd(pid:15,stackpage=cfd33000)

Ah, ha! I've found the problem. Perversely, I wasn't able to reproduce
this bug until I booted a UP kernel. I've appended the fix. Please try
this out. I have sufficient confidence in this fix that I'll make a
proper release in a few minutes.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

diff -urN linux-2.4.17-pre2/Documentation/filesystems/devfs/ChangeLog linux/Documentation/filesystems/devfs/ChangeLog
--- linux-2.4.17-pre2/Documentation/filesystems/devfs/ChangeLog	Sat Dec  1 10:48:46 2001
+++ linux/Documentation/filesystems/devfs/ChangeLog	Sun Dec  2 23:23:12 2001
@@ -1805,3 +1805,7 @@
 
 - Do not send CREATE, CHANGE, ASYNC_OPEN or DELETE events from devfsd
   or children
+===============================================================================
+Changes for patch v199.1
+
+- Fixed bug in <devfsd_read>: was dereferencing freed pointer
diff -urN linux-2.4.17-pre2/fs/devfs/base.c linux/fs/devfs/base.c
--- linux-2.4.17-pre2/fs/devfs/base.c	Sat Dec  1 10:48:46 2001
+++ linux/fs/devfs/base.c	Sun Dec  2 23:21:10 2001
@@ -569,6 +569,9 @@
 	       Do not send CREATE, CHANGE, ASYNC_OPEN or DELETE events from
 	       devfsd or children.
   v1.2
+    20011202   Richard Gooch <rgooch@atnf.csiro.au>
+	       Fixed bug in <devfsd_read>: was dereferencing freed pointer.
+  v1.3
 */
 #include <linux/types.h>
 #include <linux/errno.h>
@@ -601,7 +604,7 @@
 #include <asm/bitops.h>
 #include <asm/atomic.h>
 
-#define DEVFS_VERSION            "1.2 (20011127)"
+#define DEVFS_VERSION            "1.3 (20011202)"
 
 #define DEVFS_NAME "devfs"
 
@@ -3243,11 +3246,17 @@
     tlen = rpos - *ppos;
     if (done)
     {
+	devfs_handle_t parent;
+
 	spin_lock (&fs_info->devfsd_buffer_lock);
 	fs_info->devfsd_first_event = entry->next;
 	if (entry->next == NULL) fs_info->devfsd_last_event = NULL;
 	spin_unlock (&fs_info->devfsd_buffer_lock);
-	for (; de != NULL; de = de->parent) devfs_put (de);
+	for (; de != NULL; de = parent)
+	{
+	    parent = de->parent;
+	    devfs_put (de);
+	}
 	kmem_cache_free (devfsd_buf_cache, entry);
 	if (ival > 0) atomic_sub (ival, &fs_info->devfsd_overrun_count);
 	*ppos = 0;

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre ROUSSELET]

We have to be patient, my linux box is at home. I'll test your patch in a few hours.

Pierre

>Messsage du 03/12/2001 08:33
>De : Richard Gooch <rgooch@ras.ucalgary.ca>
>A : Pierre Rousselet <pierre.rousselet@wanadoo.fr>
>Copie à :  <linux-kernel@vger.kernel.org>,  <wli@holomorphy.com>
>Objet : Re: 2.5.1-pre5 not easy to boot with devfs  
>
> Pierre Rousselet writes:
> > As far as I can see,
> > 
> > when CONFIG_DEBUG_KERNEL is set
> >   and 
> > when devfsd is started at boot time
> > I get an Oops when remounting, rw the root fs :
> > 
> > Unable to handle kernel request at va 5a5a5a5e
> > ...
> > EIP: 0010:[<c01516f9>] Not tainted
> > ...
> > Process devfsd(pid:15,stackpage=cfd33000)
> 
> Ah, ha! I've found the problem. Perversely, I wasn't able to reproduce
> this bug until I booted a UP kernel. I've appended the fix. Please try
> this out. I have sufficient confidence in this fix that I'll make a
> proper release in a few minutes.
> 
> 				Regards,
> 
> 					Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca
> 
> diff -urN linux-2.4.17-pre2/Documentation/filesystems/devfs/ChangeLog linux/Documentation/filesystems/devfs/ChangeLog
> --- linux-2.4.17-pre2/Documentation/filesystems/devfs/ChangeLog	Sat Dec  1 10:48:46 2001
> +++ linux/Documentation/filesystems/devfs/ChangeLog	Sun Dec  2 23:23:12 2001
> @@ -1805,3 +1805,7 @@
>  
>  - Do not send CREATE, CHANGE, ASYNC_OPEN or DELETE events from devfsd
>    or children
> +===============================================================================
> +Changes for patch v199.1
> +
> +- Fixed bug in <devfsd_read>: was dereferencing freed pointer
> diff -urN linux-2.4.17-pre2/fs/devfs/base.c linux/fs/devfs/base.c
> --- linux-2.4.17-pre2/fs/devfs/base.c	Sat Dec  1 10:48:46 2001
> +++ linux/fs/devfs/base.c	Sun Dec  2 23:21:10 2001
> @@ -569,6 +569,9 @@
>  	       Do not send CREATE, CHANGE, ASYNC_OPEN or DELETE events from
>  	       devfsd or children.
>    v1.2
> +    20011202   Richard Gooch <rgooch@atnf.csiro.au>
> +	       Fixed bug in <devfsd_read>: was dereferencing freed pointer.
> +  v1.3
>  */
>  #include <linux/types.h>
>  #include <linux/errno.h>
> @@ -601,7 +604,7 @@
>  #include <asm/bitops.h>
>  #include <asm/atomic.h>
>  
> -#define DEVFS_VERSION            "1.2 (20011127)"
> +#define DEVFS_VERSION            "1.3 (20011202)"
>  
>  #define DEVFS_NAME "devfs"
>  
> @@ -3243,11 +3246,17 @@
>      tlen = rpos - *ppos;
>      if (done)
>      {
> +	devfs_handle_t parent;
> +
>  	spin_lock (&fs_info->devfsd_buffer_lock);
>  	fs_info->devfsd_first_event = entry->next;
>  	if (entry->next == NULL) fs_info->devfsd_last_event = NULL;
>  	spin_unlock (&fs_info->devfsd_buffer_lock);
> -	for (; de != NULL; de = de->parent) devfs_put (de);
> +	for (; de != NULL; de = parent)
> +	{
> +	    parent = de->parent;
> +	    devfs_put (de);
> +	}
>  	kmem_cache_free (devfsd_buf_cache, entry);
>  	if (ival > 0) atomic_sub (ival, &fs_info->devfsd_overrun_count);
>  	*ppos = 0;
> 

Re: 2.5.1-pre5 not easy to boot with devfs

[Pierre Rousselet]

Richard Gooch wrote:

 
> @@ -3243,11 +3246,17 @@
>      tlen = rpos - *ppos;
>      if (done)
>      {
> +       devfs_handle_t parent;
> +
>         spin_lock (&fs_info->devfsd_buffer_lock);
>         fs_info->devfsd_first_event = entry->next;
>         if (entry->next == NULL) fs_info->devfsd_last_event = NULL;
>         spin_unlock (&fs_info->devfsd_buffer_lock);
> -       for (; de != NULL; de = de->parent) devfs_put (de);
> +       for (; de != NULL; de = parent)
> +       {
> +           parent = de->parent;
> +           devfs_put (de);
> +       }
>         kmem_cache_free (devfsd_buf_cache, entry);
>         if (ival > 0) atomic_sub (ival, &fs_info->devfsd_overrun_count);
>         *ppos = 0;

I have just edited the fs/devfs/base.c in the 2.4.17-pre2 tree with the
change in the above lines. 

It boots and looks OK.

I have to switch off devfs=dall it keeps repeating the same message
endlessly. I'm going to be short in HD capacity.

Regards 

Pierre
_________________________________________________________
Dec  3 13:07:34 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:34 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:34 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:34 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:34 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:35 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:36 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:36 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
Dec  3 13:07:36 milou kernel: devfs: d_delete(): dentry: cfd45484 
inode: cfc13bf4  devfs_entry: cfc143ac 
Dec  3 13:07:36 milou kernel: devfs: d_delete(): dentry: cd15bba4 
inode: ccdb2d9c  devfs_entry: cfc14324 
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------