Re: [suse-security] Kernel update hangs system
I have upgraded from the default installed kernel 2.6.4-52-default to 2.6.4-75-default. When I read any data on my secondary disk (hdc) the system hangs. The messages in /var/log/messages are in the attached file kernel-2.6.4-75.txt. With the older kernel 2.6.4-52-default the same action produced the following messages in the errorlog: Jul 1 09:29:53 linux kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 09:29:53 linux kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 09:29:53 linux kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 09:29:53 linux kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 09:29:53 linux kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 09:29:53 linux kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 09:29:53 linux kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 09:29:53 linux kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 09:29:53 linux kernel: ide1: reset: success The sections from the boot.msg concerning the disks are: <6> ide0: BM-DMA at 0xa800-0xa807, BIOS settings: hda:DMA, hdb:pio <6> ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdc:DMA, hdd:DMA <4>hda: IBM-DJNA-352030, ATA DISK drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>hdc: IBM-DPTA-372050, ATA DISK drive <4>hdd: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>hda: max request size: 128KiB <6>hda: 39876480 sectors (20416 MB) w/1966KiB Cache, CHS=39560/16/63, UDMA(33) <6> hda: hda1 hda2 hda3 <4>hdc: max request size: 128KiB <6>hdc: 40088160 sectors (20525 MB) w/1961KiB Cache, CHS=39770/16/63, UDMA(66) <6> hdc: hdc1 .... <5>ReiserFS: hda3: found reiserfs format "3.6" with standard journal <5>ReiserFS: hda3: using ordered data mode <5>ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 1 8, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>ReiserFS: hda3: checking transaction log (hda3) <5>ReiserFS: hda3: Using r5 hash to sort names .... <5>ReiserFS: hdc1: found reiserfs format "3.5" with standard journal <5>ReiserFS: hdc1: using ordered data mode <5>ReiserFS: hdc1: journal params: device hdc1, size 8192, journal first block 1 8, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>ReiserFS: hdc1: checking transaction log (hdc1) <5>ReiserFS: hdc1: Using r5 hash to sort names <5>ReiserFS: hdc1: using 3.5.x disk format Best regards Ulrich -- +-----------------------------------------------------------+ | Ulrich Bernhard | | Informatikdienste Tel: (+41-44) 635 67 73 | | Universitaet Zuerich Fax: (+41-44) 635 45 05 | | Winterthurerstr. 190 | | CH-8057 Zuerich Email: ulrich.bernhard@id.unizh.ch | | Switzerland | +-----------------------------------------------------------+ Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 1 10:42:43 smb0 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jul 1 10:42:43 smb0 kernel: bad: scheduling while atomic! Jul 1 10:42:43 smb0 kernel: Call Trace: Jul 1 10:42:43 smb0 kernel: [schedule+1687/1744] schedule+0x697/0x6d0 Jul 1 10:42:43 smb0 kernel: [<c011cb37>] schedule+0x697/0x6d0 Jul 1 10:42:43 smb0 kernel: [schedule_timeout+86/176] schedule_timeout+0x56/0xb0 Jul 1 10:42:43 smb0 kernel: [<c01268e6>] schedule_timeout+0x56/0xb0 Jul 1 10:42:43 smb0 kernel: [process_timeout+0/16] process_timeout+0x0/0x10 Jul 1 10:42:43 smb0 kernel: [<c01260e0>] process_timeout+0x0/0x10 Jul 1 10:42:43 smb0 kernel: [ide_pin_hwgroup+52/96] ide_pin_hwgroup+0x34/0x60 Jul 1 10:42:43 smb0 kernel: [<c0243884>] ide_pin_hwgroup+0x34/0x60 Jul 1 10:42:43 smb0 kernel: [ide_set_xfer_rate+12/80] ide_set_xfer_rate+0xc/0x50 Jul 1 10:42:43 smb0 kernel: [<c0246b4c>] ide_set_xfer_rate+0xc/0x50 Jul 1 10:42:43 smb0 kernel: [check_dma_crc+46/80] check_dma_crc+0x2e/0x50 Jul 1 10:42:43 smb0 kernel: [<c024595e>] check_dma_crc+0x2e/0x50 Jul 1 10:42:43 smb0 kernel: [do_reset1+76/384] do_reset1+0x4c/0x180 Jul 1 10:42:43 smb0 kernel: [<c0245b2c>] do_reset1+0x4c/0x180 Jul 1 10:42:43 smb0 kernel: [idedisk_error+487/496] idedisk_error+0x1e7/0x1f0 Jul 1 10:42:43 smb0 kernel: [<c024ff07>] idedisk_error+0x1e7/0x1f0 Jul 1 10:42:43 smb0 kernel: [do_signal+1163/1488] do_signal+0x48b/0x5d0 Jul 1 10:42:43 smb0 kernel: [<c01075db>] do_signal+0x48b/0x5d0 Jul 1 10:42:43 smb0 kernel: [convert_fxsr_from_user+21/240] convert_fxsr_from_user+0x15/0xf0 Jul 1 10:42:43 smb0 kernel: [<c010ed45>] convert_fxsr_from_user+0x15/0xf0 Jul 1 10:42:43 smb0 kernel: [ide_dma_intr+120/128] ide_dma_intr+0x78/0x80 Jul 1 10:42:43 smb0 kernel: [<c024bc98>] ide_dma_intr+0x78/0x80 Jul 1 10:42:43 smb0 kernel: [ide_intr+256/400] ide_intr+0x100/0x190 Jul 1 10:42:43 smb0 kernel: [<c0244a00>] ide_intr+0x100/0x190 Jul 1 10:42:43 smb0 kernel: [ide_dma_intr+0/128] ide_dma_intr+0x0/0x80 Jul 1 10:42:43 smb0 kernel: [<c024bc20>] ide_dma_intr+0x0/0x80 Jul 1 10:42:43 smb0 kernel: [handle_IRQ_event+47/96] handle_IRQ_event+0x2f/0x60 Jul 1 10:42:43 smb0 kernel: [<c010a79f>] handle_IRQ_event+0x2f/0x60 Jul 1 10:42:43 smb0 kernel: [do_IRQ+136/416] do_IRQ+0x88/0x1a0 Jul 1 10:42:43 smb0 kernel: [<c010a858>] do_IRQ+0x88/0x1a0 Jul 1 10:42:43 smb0 kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Jul 1 10:42:43 smb0 kernel: [<c0108d48>] common_interrupt+0x18/0x20 Jul 1 10:42:43 smb0 kernel: Jul 1 10:42:43 smb0 kernel: bad: scheduling while atomic! Jul 1 10:42:43 smb0 kernel: Call Trace: Jul 1 10:42:43 smb0 kernel: [schedule+1687/1744] schedule+0x697/0x6d0 Jul 1 10:42:43 smb0 kernel: [<c011cb37>] schedule+0x697/0x6d0 Jul 1 10:42:43 smb0 kernel: [schedule_timeout+86/176] schedule_timeout+0x56/0xb0 Jul 1 10:42:43 smb0 kernel: [<c01268e6>] schedule_timeout+0x56/0xb0 Jul 1 10:42:43 smb0 kernel: [process_timeout+0/16] process_timeout+0x0/0x10 Jul 1 10:42:43 smb0 kernel: [<c01260e0>] process_timeout+0x0/0x10 Jul 1 10:42:43 smb0 kernel: [ide_pin_hwgroup+52/96] ide_pin_hwgroup+0x34/0x60 Jul 1 10:42:43 smb0 kernel: [<c0243884>] ide_pin_hwgroup+0x34/0x60 Jul 1 10:42:43 smb0 kernel: [ide_set_xfer_rate+12/80] ide_set_xfer_rate+0xc/0x50 Jul 1 10:42:43 smb0 kernel: [<c0246b4c>] ide_set_xfer_rate+0xc/0x50 and so on .....
I have upgraded from the default installed kernel 2.6.4-52-default to 2.6.4-75-default. When I read any data on my secondary disk (hdc) the system hangs. The messages in /var/log/messages are in the attached file kernel-2.6.4-75.txt.
This should be gone with kernel-default-2.6.5-7.95.i586.rpm, to be found on the ftp server. There is going to be an announcement in 10 minutes about it. You seem to be one of those rare conditions where the system could freeze, get sluggish and then freeze or some other condition. We think we were able to isolate those cases, while we could not clearly reproduce the reports. Thanks, Roman.
participants (2)
-
Roman Drahtmueller
-
Ulrich Bernhard