On Friday 01 Oct 2004 16:08, Miguel Albuquerque wrote:

Hi all,

I'm facing this strange system hang when someone connects to my computer to a samba share :

syslogd takes over 88% of CPU usage and kswapd0 the same. I've stopped and removed smb services from the boot process and now it works fine. I have changed CD-Rom's and Hard Disks thinking that i might had a faulty device (IDE, argh!). Also disabling DMA had no impact on the problem.

Here is the stack trace <snipped> Oct 1 04:17:01 rider2 syslogd 1.4.1: restart. Oct 1 04:17:19 rider2 su: (to nobody) root on none Oct 1 04:17:19 rider2 su: pam_unix2: session started for user nobody, service su Oct 1 04:19:06 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:06 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:06 rider2 kernel: klogd 1.4.1, ---------- state change ---------- Oct 1 04:19:06 rider2 kernel: Inspecting /boot/System.map-2.6.5-7.108-default Oct 1 04:19:07 rider2 kernel: Loaded 23748 symbols from /boot/System.map-2.6.5-7.108-default. Oct 1 04:19:07 rider2 kernel: Symbols match kernel version 2.6.5. Oct 1 04:19:07 rider2 kernel: No module symbols loaded - kernel modules not enabled. Oct 1 04:19:07 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:07 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 1 04:19:12 rider2 kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 1 04:19:12 rider2 kernel: bad: scheduling while atomic! Oct 1 04:19:12 rider2 kernel: Call Trace: Oct 1 04:19:12 rider2 kernel: [schedule+1687/1744] schedule+0x697/0x6d0 Oct 1 04:19:12 rider2 kernel: [<c011cf17>] schedule+0x697/0x6d0 Oct 1 04:19:12 rider2 kernel: [schedule_timeout+86/176] schedule_timeout+0x56/0xb0 Oct 1 04:19:12 rider2 kernel: [<c0126cc6>] schedule_timeout+0x56/0xb0 Oct 1 04:19:12 rider2 kernel: [process_timeout+0/16] process_timeout+0x0/0x10 Oct 1 04:19:12 rider2 kernel: [<c01264c0>] process_timeout+0x0/0x10 Oct 1 04:19:12 rider2 kernel: [ide_pin_hwgroup+52/96] ide_pin_hwgroup+0x34/0x60 Oct 1 04:19:12 rider2 kernel: [<c0244354>] ide_pin_hwgroup+0x34/0x60 Oct 1 04:19:12 rider2 kernel: [ide_set_xfer_rate+12/80] ide_set_xfer_rate+0xc/0x50 Oct 1 04:19:12 rider2 kernel: [<c024761c>] ide_set_xfer_rate+0xc/0x50 Oct 1 04:19:12 rider2 kernel: [check_dma_crc+46/80] check_dma_crc+0x2e/0x50 Oct 1 04:19:12 rider2 kernel: [<c024642e>] check_dma_crc+0x2e/0x50 Oct 1 04:19:12 rider2 kernel: [do_reset1+76/384] do_reset1+0x4c/0x180 Oct 1 04:19:12 rider2 kernel: [<c02465fc>] do_reset1+0x4c/0x180 Oct 1 04:19:12 rider2 kernel: [idedisk_error+487/496] idedisk_error+0x1e7/0x1f0 Oct 1 04:19:12 rider2 kernel: [<c0250a57>] idedisk_error+0x1e7/0x1f0 Oct 1 04:19:12 rider2 kernel: [start_request+517/576] start_request+0x205/0x240 Oct 1 04:19:12 rider2 kernel: [<c0244f85>] start_request+0x205/0x240 Oct 1 04:19:12 rider2 kernel: [ide_dma_intr+120/128] ide_dma_intr+0x78/0x80 Oct 1 04:19:12 rider2 kernel: [<c024c798>] ide_dma_intr+0x78/0x80 Oct 1 04:19:12 rider2 kernel: [ide_intr+256/400] ide_intr+0x100/0x190 Oct 1 04:19:12 rider2 kernel: [<c02454d0>] ide_intr+0x100/0x190 Oct 1 04:19:12 rider2 kernel: [ide_dma_intr+0/128] ide_dma_intr+0x0/0x80 Oct 1 04:19:12 rider2 kernel: [<c024c720>] ide_dma_intr+0x0/0x80 Oct 1 04:19:12 rider2 kernel: [handle_IRQ_event+47/96] handle_IRQ_event+0x2f/0x60 Oct 1 04:19:12 rider2 kernel: [<c010a79f>] handle_IRQ_event+0x2f/0x60 Oct 1 04:19:12 rider2 kernel: [do_IRQ+136/416] do_IRQ+0x88/0x1a0 Oct 1 04:19:12 rider2 kernel: [<c010a858>] do_IRQ+0x88/0x1a0 Oct 1 04:19:12 rider2 kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Oct 1 04:19:12 rider2 kernel: [<c0108d48>] common_interrupt+0x18/0x20 Oct 1 04:19:12 rider2 kernel: [default_idle+0/48] default_idle+0x0/0x30 Oct 1 04:19:12 rider2 kernel: [<c0106290>] default_idle+0x0/0x30 Oct 1 04:19:12 rider2 kernel: [default_idle+35/48] default_idle+0x23/0x30 Oct 1 04:19:12 rider2 kernel: [<c01062b3>] default_idle+0x23/0x30 Oct 1 04:19:12 rider2 kernel: [cpu_idle+28/64] cpu_idle+0x1c/0x40 Oct 1 04:19:12 rider2 kernel: [<c0106dac>] cpu_idle+0x1c/0x40 Oct 1 04:19:12 rider2 kernel: [start_kernel+665/768] start_kernel+0x299/0x300 Oct 1 04:19:12 rider2 kernel: [<c039a629>] start_kernel+0x299/0x300 </snipped>

What's wrong ?

Thanx -- Macintosh for Productivity, Linux for Development Palm for Mobility, Windows for Solitaire

.-. Datacorp IT /v\ We Run SuSE // \\ *The LINUX Experts* Miguel Albuquerque /( )\ 15 Chemin Bessinge ^^-^^ 1223 Cologny,GE - CH Mobile +41 79 543 1935 http://counter.li.org Linux user #301007 http://www.datacorp.ch

Do you NOT KNOW how to start a new thread or just to freakin lazey ..? -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..

On Friday 01 Oct 2004 21:51, Patrick Shanahan wrote:

* peter Nikolic [10-01-04 12:02]:

...

Do you NOT KNOW how to start a new thread or just to freakin lazey ..?

Why couldn't you post the entire off-thread message?

What you do is as bad, as he is ignorant of what he does. You know and do it anyway.

:0

* ^From.*p.nikolic /dev/null

-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Dont even think of tryin to flam e less U got you flame proof on NO need to waste time postin the entire thing it's ther for all to read so WHY repost ?. yea FLAME THROWER AT THE READY .. yhbw -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..