2.5.72 oops (scheduling while atomic)

2.5.72 oops (scheduling while atomic)

Post by Greg Norri » Wed, 18 Jun 2003 16:40:11



I'm getting the following oops when booting 2.5.72, preceded by a
quite a few "bad: scheduling while atomic!" messages.  My .config and
the decoded oops are attached.

Any insights and/or suggestions would be appreciated.  Thanx!

  oops-decoded
1K Download

  config_glitch.1
22K Download
 
 
 

2.5.72 oops (scheduling while atomic)

Post by Paul Larso » Wed, 18 Jun 2003 20:30:07



> I'm getting the following oops when booting 2.5.72, preceded by a
> quite a few "bad: scheduling while atomic!" messages.  My .config and
> the decoded oops are attached.

> Any insights and/or suggestions would be appreciated.  Thanx!

I submitted a bug on this a while back, bug #800 in bugme:
http://bugme.osdl.org/show_bug.cgi?id=800

I saw it starting with 2.5.70-bk15.  It looks like it did not have this
problem in 2.5.70-bk14.  Does this seem to be the case with you as
well?  I have not yet had time to hunt down more than is in that bug
report.

Thanks,
Paul Larson

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.72 oops (scheduling while atomic)

Post by Greg Norri » Wed, 18 Jun 2003 21:10:04



> I submitted a bug on this a while back, bug #800 in bugme:
> http://bugme.osdl.org/show_bug.cgi?id=800

> I saw it starting with 2.5.70-bk15.  It looks like it did not have this
> problem in 2.5.70-bk14.  Does this seem to be the case with you as
> well?  I have not yet had time to hunt down more than is in that bug
> report.

It certainly looks like the same problem.  I'll try out 2.5.70-bk14/15
sometime tonite if I have a chance, and see if that's where it breaks
for me as well.  In the meantime, I'm comparing our .config files.

Thanx!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.72 oops (scheduling while atomic)

Post by Brandon Lo » Thu, 19 Jun 2003 07:20:09


I've got a 'me too', I run -mm kernels, but it appears to match up,
first appeared on 2.5.70-mm9, previous mms didn't have it (I believe
-mm9 was just after -bk15)

--Brandon

On Tue, 06/17/03 at 09:35:51 -0500, Greg Norris wrote:
> I'm getting the following oops when booting 2.5.72, preceded by a
> quite a few "bad: scheduling while atomic!" messages.  My .config and
> the decoded oops are attached.

> Any insights and/or suggestions would be appreciated.  Thanx!
> ksymoops 2.4.8 on i686 2.4.21.  Options used
>      -v ./vmlinux (specified)
>      -K (specified)
>      -L (specified)
>      -o /lib/modules/2.5.72 (specified)
>      -m /boot/System.map-2.5.72 (specified)

> No modules in ksyms, skipping objects
> Unable to handle kernel paging request at virtual address bfffefec
> 0807823f
> *pde = 3fef3067
> Oops: 0007 [#4]
> CPU:    0
> EIP:    0073:[<0807823f>]    Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010207
> eax: 0000007b  ebx: 40166f60  ecx: 080fd208  edx: 080fd208
> esi: 400098b8  edi: bffff564  ebp: bffff0f8  esp: bfffefe0
> ds: 007b  es: 007b  ss: 007b
> Call Trace: [<c011a8de>] [<c0109c5a>] [<c0107089>] [<c0107089>] [<c0107143>] [<c0105000>] [<c02e0842>] [<c02e0432>]
> Warning (Oops_read): Code line not seen, dumping what data is available

> >>EIP; 0807823f <__crc_proc_ide_write_settings+6ccbab/917b7f>   <=====

> >>ebx; 40166f60 <__crc_param_set_short+120617/3a4b20>
> >>ecx; 080fd208 <__crc_proc_ide_write_settings+751b74/917b7f>
> >>edx; 080fd208 <__crc_proc_ide_write_settings+751b74/917b7f>
> >>esi; 400098b8 <__crc_usb_buffer_dmasync+5a6022/5e30b3>
> >>edi; bffff564 <__crc_posix_test_lock+96de13/9aaee6>
> >>ebp; bffff0f8 <__crc_posix_test_lock+96d9a7/9aaee6>
> >>esp; bfffefe0 <__crc_posix_test_lock+96d88f/9aaee6>

> Trace; c011a8de <schedule+542/547>
> Trace; c0109c5a <reschedule_interrupt+1a/20>
> Trace; c0107089 <default_idle+0/31>
> Trace; c0107089 <default_idle+0/31>
> Trace; c0107143 <cpu_idle+51/53>
> Trace; c0105000 <_stext+0/0>
> Trace; c02e0842 <start_kernel+16d/185>
> Trace; c02e0432 <unknown_bootoption+0/f8>

> 1 warning issued.  Results may not be reliable.
> #
> # Automatically generated make config: don't edit
> #
> CONFIG_X86=y
> CONFIG_MMU=y
> CONFIG_UID16=y
> CONFIG_GENERIC_ISA_DMA=y

> #
> # Code maturity level options
> #
> CONFIG_EXPERIMENTAL=y

> #
> # General setup
> #
> CONFIG_SWAP=y
> CONFIG_SYSVIPC=y
> CONFIG_BSD_PROCESS_ACCT=y
> CONFIG_SYSCTL=y
> CONFIG_LOG_BUF_SHIFT=15
> # CONFIG_EMBEDDED is not set
> CONFIG_FUTEX=y
> CONFIG_EPOLL=y

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

> #
> # Processor type and features
> #
> CONFIG_X86_PC=y
> # CONFIG_X86_VOYAGER is not set
> # CONFIG_X86_NUMAQ is not set
> # CONFIG_X86_SUMMIT is not set
> # CONFIG_X86_BIGSMP is not set
> # CONFIG_X86_VISWS is not set
> # CONFIG_X86_GENERICARCH is not set
> # CONFIG_X86_ES7000 is not set
> # CONFIG_M386 is not set
> # CONFIG_M486 is not set
> # CONFIG_M586 is not set
> # CONFIG_M586TSC is not set
> # CONFIG_M586MMX is not set
> # CONFIG_M686 is not set
> # CONFIG_MPENTIUMII is not set
> # CONFIG_MPENTIUMIII is not set
> CONFIG_MPENTIUM4=y
> # CONFIG_MK6 is not set
> # CONFIG_MK7 is not set
> # CONFIG_MK8 is not set
> # CONFIG_MELAN is not set
> # CONFIG_MCRUSOE is not set
> # CONFIG_MWINCHIPC6 is not set
> # CONFIG_MWINCHIP2 is not set
> # CONFIG_MWINCHIP3D is not set
> # CONFIG_MCYRIXIII is not set
> # CONFIG_MVIAC3_2 is not set
> # CONFIG_X86_GENERIC is not set
> CONFIG_X86_CMPXCHG=y
> CONFIG_X86_XADD=y
> CONFIG_X86_L1_CACHE_SHIFT=7
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_X86_WP_WORKS_OK=y
> CONFIG_X86_INVLPG=y
> CONFIG_X86_BSWAP=y
> CONFIG_X86_POPAD_OK=y
> CONFIG_X86_GOOD_APIC=y
> CONFIG_X86_INTEL_USERCOPY=y
> CONFIG_X86_USE_PPRO_CHECKSUM=y
> CONFIG_HUGETLB_PAGE=y
> CONFIG_SMP=y
> CONFIG_NR_CPUS=2
> CONFIG_PREEMPT=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
> CONFIG_X86_TSC=y
> CONFIG_X86_MCE=y
> CONFIG_X86_MCE_NONFATAL=y
> CONFIG_X86_MCE_P4THERMAL=y
> # CONFIG_TOSHIBA is not set
> # CONFIG_I8K is not set
> CONFIG_MICROCODE=m
> CONFIG_X86_MSR=m
> CONFIG_X86_CPUID=m
> # CONFIG_EDD is not set
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> CONFIG_HIGHPTE=y
> # CONFIG_MATH_EMULATION is not set
> CONFIG_MTRR=y
> CONFIG_HAVE_DEC_LOCK=y

> #
> # Power management options (ACPI, APM)
> #
> # CONFIG_PM is not set

> #
> # ACPI Support
> #
> CONFIG_ACPI=y
> CONFIG_ACPI_HT_ONLY=y
> CONFIG_ACPI_BOOT=y

> #
> # CPU Frequency scaling
> #
> # CONFIG_CPU_FREQ is not set

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

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

> #
> # PCI Hotplug Support
> #
> # CONFIG_HOTPLUG_PCI is not set

> #
> # Executable file formats
> #
> CONFIG_KCORE_ELF=y
> # CONFIG_KCORE_AOUT is not set
> CONFIG_BINFMT_AOUT=m
> CONFIG_BINFMT_ELF=y
> CONFIG_BINFMT_MISC=m

> #
> # 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 is not set
> # CONFIG_PARPORT_OTHER is not set
> CONFIG_PARPORT_1284=y

> #
> # Plug and Play support
> #
> # CONFIG_PNP is not set

> #
> # Block devices
> #
> CONFIG_BLK_DEV_FD=m
> # CONFIG_PARIDE is not set
> # CONFIG_BLK_CPQ_DA is not set
> # CONFIG_BLK_CPQ_CISS_DA is not set
> # CONFIG_BLK_DEV_DAC960 is not set
> # CONFIG_BLK_DEV_UMEM is not set
> CONFIG_BLK_DEV_LOOP=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
> # CONFIG_LBD is not set

> #
> # ATA/ATAPI/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_IDEDISK_STROKE is not set
> CONFIG_BLK_DEV_IDECD=m
> # CONFIG_BLK_DEV_IDEFLOPPY is not set
> CONFIG_BLK_DEV_IDESCSI=m
> # CONFIG_IDE_TASK_IOCTL is not set
> CONFIG_IDE_TASKFILE_IO=y

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

> #
> # SCSI device support
> #
> CONFIG_SCSI=m

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

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

> #
> # SCSI low-level drivers
> #
> # CONFIG_BLK_DEV_3W_XXXX_RAID is not set
> # CONFIG_SCSI_ACARD is not set
> # CONFIG_SCSI_AACRAID is not set
> # CONFIG_SCSI_AIC7XXX is not set
> # CONFIG_SCSI_AIC7XXX_OLD is not set
> # CONFIG_SCSI_AIC79XX is not set
> # CONFIG_SCSI_DPT_I2O is not set
> # CONFIG_SCSI_ADVANSYS is not set
> # CONFIG_SCSI_IN2000 is not set
> # CONFIG_SCSI_AM53C974 is not set
> # CONFIG_SCSI_MEGARAID is not set
> # CONFIG_SCSI_BUSLOGIC is not set
> # CONFIG_SCSI_CPQFCTS is not set
> # CONFIG_SCSI_DMX3191D is not set
> # CONFIG_SCSI_EATA is not set
> # CONFIG_SCSI_EATA_PIO is not set
> # CONFIG_SCSI_FUTURE_DOMAIN is not set
> # CONFIG_SCSI_GDTH is not set
> # CONFIG_SCSI_GENERIC_NCR5380 is not set
> # CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
> # CONFIG_SCSI_IPS is not set
> # CONFIG_SCSI_INITIO is not set
> # CONFIG_SCSI_INIA100 is not set
> # CONFIG_SCSI_PPA is not set
> # CONFIG_SCSI_IMM is not set
> # CONFIG_SCSI_NCR53C7xx is not set
> # CONFIG_SCSI_SYM53C8XX_2 is not set
> # CONFIG_SCSI_NCR53C8XX is not set
> # CONFIG_SCSI_SYM53C8XX is not set
> # CONFIG_SCSI_PCI2000 is not set
> # CONFIG_SCSI_PCI2220I is not set
> # CONFIG_SCSI_QLOGIC_ISP is not set
> # CONFIG_SCSI_QLOGIC_FC is not set
> # CONFIG_SCSI_QLOGIC_1280 is not set
> # CONFIG_SCSI_DC395x is not set
> # CONFIG_SCSI_DC390T is not set
> # CONFIG_SCSI_U14_34F is not set
> # CONFIG_SCSI_NSP32 is not set
> #

...

read more »

 
 
 

2.5.72 oops (scheduling while atomic)

Post by Greg Norri » Fri, 20 Jun 2003 04:00:07


I just re-tested with 2.5.72-bk1, which still experiences the problem.
I enabled all of the debugging options this time, however, and so
captured what I hope to be a more informative oops.  The .config was
otherwise unchanged.

Let me know if I can provide any additional information.

  oops-decoded
1K Download
 
 
 

2.5.72 oops (scheduling while atomic)

Post by Andrew Morto » Fri, 20 Jun 2003 04:10:10



> I just re-tested with 2.5.72-bk1, which still experiences the problem.
>  I enabled all of the debugging options this time, however, and so
>  captured what I hope to be a more informative oops.  The .config was
>  otherwise unchanged.

>  Let me know if I can provide any additional information.

Try booting with the `initcall_debug' kernel boot option.
All of the startup messages would be interesting.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.72 oops (scheduling while atomic)

Post by Andrew Morto » Fri, 20 Jun 2003 07:50:07



> I'm getting the following oops when booting 2.5.72, preceded by a
>  quite a few "bad: scheduling while atomic!" messages.  My .config and
>  the decoded oops are attached.

I was able to reproduce this.  Pid #0 (swapper) ends up with a preempt
count of two and everything goes pear-shaped.

This appears to be because you haven't selected any chip drivers in IDE
config.  I selected PIIX and things started working better.

Just to double-check I took my usual .config, enable preemption, disabled
all IDE chip drivers and the same thing happened.  Over to Bart ;)

Your .config seems broken in other ways btw.  Suggest you do

        cp arch/i386/defconfig .config

and start again.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.72 oops (scheduling while atomic)

Post by Bartlomiej Zolnierkiewic » Fri, 20 Jun 2003 12:40:08


Hi Andrew,

I think you wanted to cc: me not the other Bart :-).

I am aware of the problem and looking for solution.
Reverting to old non-taskfile code seems to help
(say N to IDE "Taskfile IO" option available in 2.5.72).

Thanks,
--
Bartlomiej
Linux IDE Maintainer



> > I'm getting the following oops when booting 2.5.72, preceded by a
> >  quite a few "bad: scheduling while atomic!" messages.  My .config and
> >  the decoded oops are attached.

> I was able to reproduce this.  Pid #0 (swapper) ends up with a preempt
> count of two and everything goes pear-shaped.

> This appears to be because you haven't selected any chip drivers in IDE
> config.  I selected PIIX and things started working better.

> Just to double-check I took my usual .config, enable preemption, disabled
> all IDE chip drivers and the same thing happened.  Over to Bart ;)

> Your .config seems broken in other ways btw.  Suggest you do

>    cp arch/i386/defconfig .config

> and start again.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

2.5.72 oops (scheduling while atomic)

Post by Greg Norri » Sat, 21 Jun 2003 01:40:08



> This appears to be because you haven't selected any chip drivers in IDE
> config.  I selected PIIX and things started working better.

Sure enough, Iafterenabling PIIX support I was able to boot successfully.
I had left it out because my understanding was that it doesn't support
my chipset... this was incorrect, at least in the case of 2.5.x.  Also,
my 2.4.21 kernel was perfectly happy with PIIX disabled.

Quote:> Your .config seems broken in other ways btw.  Suggest you do

>    cp arch/i386/defconfig .config

> and start again.

Could you provide any specifics, or point me to some information on the
requirements?  My approach was to start with a working 2.4.x config,
and enable everything which appeared to be necessary.

Thanx!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. PATCH 2.5.72 2/2] i_size atomic access

This adds i_seqcnt to the inode structure and then uses i_size_read()
and i_size_write() to provide atomic access to i_size.  This is a port
of Andrea Arcangeli's i_size atomic access patch from 2.4.  This only
uses the generic reader/writer consistent mechanism.

re-diff against 2.5.72.

This patch has been tested on 1 proc, 2 proc, 4 proc and 8 proc
machines.

This patch is available for download from OSDL's patch lifecycle
manager (PLM):

http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1940


  patch.2.5.72-isize.2
22K Download

2. Routine for tagging a file that x days old

3. Oops captured of 2.5.70-mm9, 2.5.71-mm1 and 2.5.72-mm1

4. Looking for 'ld_so_aix'

5. 2.5.72: oops with swsusp+ide

6. How to share dial-up internet connection within the LAN ?

7. 2.5.72-mm2+ACPI20030619: oops during boot @ scheduler-tick

8. how to make sh expand script...

9. 2.5.72-bk3 oops when loading aha152X(isapnp)

10. BENCHMARK] 2.5.72, 2.5.72-mm1, 2.5.71, 2.5.71-bk1, 2.5.71-mjb1

11. PnP Changes for 2.5.72

12. 2.5.72: sbni.c doesn't compile with gcc 3.3

13. new 2.5.72 breaks aumix