Mailinglist Archive: opensuse-bugs (10053 mails)
| < Previous | Next > |
[Bug 237675] New: System hangs when copy files in SLES9 SP3
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 23 Jan 2007 01:23:02 -0700 (MST)
- Message-id: <bug-237675-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=237675
Summary: System hangs when copy files in SLES9 SP3
Product: SUSE Linux 10.1
Version: Final
Platform: x86-64
OS/Version: SLES 9
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: Tom.gao@xxxxxxxxxx
QAContact: qa@xxxxxxx
I have several AMD dual core systems sufferring this issue that when creating
a software raid 1(using sles mdadm) or doing a regular "cp", or dd from disk0
to /dev/null, I/O stops. We start getting errors on screen.
hde: dma_timer_expiry: dma status == 0x24
hde: DMA interrupt recovery
hde: lost interrupt
hde: dma_timer_expiry: dma status == 0x24
hdg: dma_timer_expiry: dma status == 0x24 .....
After ctl +c have to wait 5 minutes until I/O begins to answer.
OR
To reboot have to unplug one of the disks or wait for about 5 minutes.
a normal dd if=/dev/hde of=/dev/null or a cp -r / /mnt/newroot (mounted on
hdg) puts the system unresponsive
It can be easily duplicated with a soft raid(mount on /raid) built when os
installed, then cp -r / /raid, error message are showed in dmesg within 5 min,
system hangs then. I found that use PIC instead of APIC can fix this and i
don't know why...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Summary: System hangs when copy files in SLES9 SP3
Product: SUSE Linux 10.1
Version: Final
Platform: x86-64
OS/Version: SLES 9
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: Tom.gao@xxxxxxxxxx
QAContact: qa@xxxxxxx
I have several AMD dual core systems sufferring this issue that when creating
a software raid 1(using sles mdadm) or doing a regular "cp", or dd from disk0
to /dev/null, I/O stops. We start getting errors on screen.
hde: dma_timer_expiry: dma status == 0x24
hde: DMA interrupt recovery
hde: lost interrupt
hde: dma_timer_expiry: dma status == 0x24
hdg: dma_timer_expiry: dma status == 0x24 .....
After ctl +c have to wait 5 minutes until I/O begins to answer.
OR
To reboot have to unplug one of the disks or wait for about 5 minutes.
a normal dd if=/dev/hde of=/dev/null or a cp -r / /mnt/newroot (mounted on
hdg) puts the system unresponsive
It can be easily duplicated with a soft raid(mount on /raid) built when os
installed, then cp -r / /raid, error message are showed in dmesg within 5 min,
system hangs then. I found that use PIC instead of APIC can fix this and i
don't know why...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |