Bug#325726: marked as done (kernel-image-2.6.8-11-amd64-generic: kernel panics/hangs (SATA related?))
Your message dated Tue, 25 Apr 2006 13:05:10 +0100
with message-id <CB7CFFB81937E3498D2DC1A738D29867048212BA@EX1.gmnews.co.uk>
and subject line Fixed probably
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kernel-image-2.6.8-11-amd64-generic: kernel panics/hangs (SATA related?)
- From: Carl Johnstone <carl.johnstone@gmgrd.co.uk>
- Date: Tue, 30 Aug 2005 15:09:06 +0100
- Message-id: <E1EA6nS-0000YO-Td@boromir.gmnews.co.uk>
Package: kernel-image-2.6.8-11-amd64-generic
Version: 2.6.8-14
Severity: critical
Justification: breaks the whole system
Keep getting lockups, in particular whilst trying to sync a RAID5 array across several SATA drives.
Setting a RAID1 partition across the same drives seems to work OK though. I've managed to get one set of errors from the syslog:
Aug 30 13:20:18 boromir kernel: ata6: command 0x25 timeout, stat 0x50 host_stat 0x61
Aug 30 13:20:18 boromir kernel: Assertion failed! qc->flags & ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=2315
Aug 30 13:20:18 boromir kernel: ----------- [cut here ] --------- [please bite here ] ---------
Aug 30 13:20:18 boromir kernel: Kernel BUG at scsi:284
Aug 30 13:20:18 kernel: invalid operand: 0000 [1]
Aug 30 13:20:18 kernel: CPU 0
Aug 30 13:20:18 kernel: Modules linked in: nls_cp437 isofs evdev 8139cp shpchp pciehp pci_hotplug forcedeth ide_scsi psmouse genrtc
ext3 jbd raid5 xor raid0 eth1394 8139too mii sr_mod sbp2 sd_mod ide_cd cdrom ide_disk ide_generic pdc202xx_new aec62xx alim15x3 amd74xx atii
xp cmd64x cs5520 cs5530 cy82c693 generic hpt34x ns87415 opti621 pdc202xx_old piix rz1000 sc1200 serverworks siimage sis5513 slc90e66 triflex
trm290 via82cxxx floppy usb_storage ide_core ohci1394 ieee1394 fbcon vga16fb vgastate usbserial usbkbd ehci_hcd ohci_hcd thermal processor
fan sata_sis sata_nv libata scsi_mod raid1 md unix font vesafb cfbcopyarea cfbimgblt cfbfillrect
Aug 30 13:20:18 kernel: Pid: 221, comm: scsi_eh_5 Not tainted 2.6.8-11-amd64-generic
Aug 30 13:20:18 kernel: RIP: 0010:[_end+533152296/2133114880] <ffffffffa0028228>{:scsi_mod:scsi_put_command+27}
Aug 30 13:20:18 kernel: RSP: 0018:000001003f82bd98 EFLAGS: 00010046
Aug 30 13:20:18 kernel: RAX: 000001003f9df000 RBX: 000001003f9e09b0 RCX: 000001003e9b6ae0
Aug 30 13:20:18 kernel: RDX: 000001003e9b6ae0 RSI: 000001003f9e2000 RDI: 000001003e9b6ac0
Aug 30 13:20:18 kernel: RBP: 000001003e9b6ac0 R08: 0000000000000000 R09: 0000000000800150
Aug 30 13:20:18 kernel: R10: 0000000000000246 R11: ffffffff80146787 R12: 0000000000000001
Aug 30 13:20:18 kernel: R13: 0000000000000001 R14: 000001003f9e09b0 R15: 0000000000000000
Aug 30 13:20:18 kernel: FS: 0000002a958ab640(0000) GS:ffffffff80391580(0000) knlGS:0000000000000000
Aug 30 13:20:18 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 30 13:20:18 kernel: CR2: 0000002a955b2000 CR3: 0000000000101000 CR4: 00000000000006e0
Aug 30 13:20:18 kernel: Process scsi_eh_5 (pid: 221, threadinfo 000001003f82a000, task 000001003f8049c0)
Aug 30 13:20:18 kernel: Stack: 0000000000000206 ffffffffa002c739 0000010039948990 ffffffffa002c815
Aug 30 13:20:18 kernel: 0000010039948990 0000000000000206 0000000000000001 000001003e9b6ac0
Aug 30 13:20:18 kernel: 0000010039948990 0000000000000000
Aug 30 13:20:18 kernel: Call Trace:<ffffffffa002c739>{:scsi_mod:scsi_next_command+14}
Aug 30 13:20:18 kernel: <ffffffffa002c815>{:scsi_mod:scsi_end_request+167}
Aug 30 13:20:18 kernel: <ffffffffa002ca9a>{:scsi_mod:scsi_io_completion+493}
Aug 30 13:20:18 kernel: <ffffffffa004b8cf>{:libata:ata_scsi_qc_complete+63}
Aug 30 13:20:18 kernel: <ffffffffa0049409>{:libata:ata_qc_complete+278} <ffffffffa004b6ad>{:libata:ata_scsi_error+16}
Aug 30 13:20:18 kernel: <ffffffffa002b609>{:scsi_mod:scsi_error_handler+284}
Aug 30 13:20:18 kernel: <ffffffff80110687>{child_rip+8} <ffffffffa002b4ed>{:scsi_mod:scsi_error_handler+0}
Aug 30 13:20:18 kernel: <ffffffff8011067f>{child_rip+0}
Aug 30 13:20:18 kernel:
Aug 30 13:20:18 kernel: Code: 0f 0b 8d 1a 03 a0 ff ff ff ff 1c 01 48 8b 42 08 48 89 41 08
Aug 30 13:20:18 kernel: RIP <ffffffffa0028228>{:scsi_mod:scsi_put_command+27} RSP <000001003f82bd98>
-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-11-amd64-generic
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages kernel-image-2.6.8-11-amd64-generic depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii e2fsprogs 1.37-2sarge1 ext2 file system utilities and lib
ii initrd-tools 0.1.81.1 tools to create initrd image for p
ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
Sorry I haven't closed the bug.
Seems that at least in part the issue was with the hardware - after some
testing with another OS we determined there was a problem on the
motherboard. We've ended up using another motherboard, which works fine
with both the kernel on the current testing install CD, and the kernel
in stable.
Thanks
Carl
--------------------------------------------------------
GMG Regional Digital is part of the Guardian Media Group plc.
CONFIDENTIALITY NOTICE. The information contained in this e-mail is intended only for 325726-done@bugs.debian.org. It may contain privileged and confidential information that is exempt from disclosure by law and if you are not an intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this e-mail in error, you may notify us by telephone on 44 (0)161 832 7200. E-mail transmission cannot be guaranteed to be secure or error-free. The sender (carl.johnstone@gmgrd.co.uk) therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
--- End Message ---
Reply to: