[Bug 14786] New: Hoary SMP Kernel on Dell Poweredge 6450 crashes on reboot

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Tue Sep 6 03:51:59 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14786
Ubuntu | linux

           Summary: Hoary SMP Kernel on Dell Poweredge 6450 crashes on
                    reboot
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: linux
        AssignedTo: ben.collins at ubuntu.com
        ReportedBy: joe at k12s.phast.umass.edu
         QAContact: kernel-bugs at lists.ubuntu.com


If you use the newest hoary kernel for x86 (2.6.10-5-686-smp) on a Dell
Poweredge 6450 (4 cpu, P-III Cascades Xeon) you will not be able to reboot the
server.  

The hoary installation CD will also have this problem.  I have tried with no
kernel parameters and tried with reboot=b,s.  The previous version of the kernel
from ubuntu (from maybe like 3 weeks ago), had different problems.  When that
kernel booted, kswapd0 would spin 100% system time on one cpu.  Setting acpi=off
for the kernel would fix that problem.  That older kernel, however, would reboot
if you used reboot=b,s.  It would not reboot normally.

On the new kernel with reboot=b,s you'll get this kernel error when rebooting:

 * Cleaning up ifupdown...                                               [ ok ]
 * Deactivating swap...
umount: none busy - remounted read-only                                  [ ok ]
 * Unmounting local filesystems...
umount: none busy - remounted read-only
   ...done.
 * Shutting down LVM Volume Groups... 
   ...done.
 * Rebooting... 
md: stopping all md devices.
psmouse.c: bad data from KBC - timeout
psmouse.c: bad data from KBC - timeout
Restarting system.                    
Badness in smp_call_function at arch/i386/kernel/smp.c:523
 [<c0111872>] smp_call_function+0x10b/0x110               
 [<c01396d5>] handle_IRQ_event+0x2e/0x64   
 [<c01118ce>] smp_send_stop+0x27/0x32   
 [<c0111877>] stop_this_cpu+0x0/0x30 
 [<c011125f>] machine_restart+0x8b/0x10d
 [<c0111924>] smp_call_function_interrupt+0x40/0x60
 [<c010394c>] call_function_interrupt+0x1c/0x24    
 [<c013007b>] futex_wake+0x5b/0xbe             
 [<c02901f8>] lock_kernel+0x95/0xa0
 [<c018ad4f>] proc_lookup+0x1c/0xc3
 [<c013f537>] __alloc_pages+0x1c3/0x355
 [<c0188322>] proc_root_lookup+0x31/0x79
 [<c0165f21>] real_lookup+0xc2/0xe3     
 [<c0166195>] do_lookup+0x96/0xa1  
 [<c0166848>] link_path_walk+0x6a8/0xd5c
 [<c01671a8>] path_lookup+0x93/0x155    
 [<c0114ae7>] do_page_fault+0x3a6/0x5cf
 [<c0167960>] open_namei+0x85/0x61f    
 [<c015812b>] filp_open+0x3e/0x64  
 [<c015840c>] get_unused_fd+0x81/0xd5
 [<c015855c>] sys_open+0x51/0xda     
 [<c0102f1d>] sysenter_past_esp+0x52/0x75


The reboot issue happens on the newest breezy live CD aswell (9/2 build I think).

The kswapd0 issue didn't occour on the newest breezy live CD, but that wasn't an
SMP kernel
anyway.

Ofcourse the ability of rebooting a server that is not physically accessible is
fairly important :)  This machine is now in production, but I do have some
limited ability to run tests on the weekends (and ofcourse I have to physically
get to the server first).

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list