From: "For@ll" <forall@stalowka.info>
To: xen-devel@lists.xensource.com
Subject: MPTSAS is broken in xen-3.4.x ?
Date: Thu, 18 Jun 2009 12:54:55 +0200 [thread overview]
Message-ID: <h1d6bk$ekf$1@ger.gmane.org> (raw)
I'm testing xen 3.4 on my servers, and I'm having problem with
controller driver, he can't load itself properly so the system isn't
booting. The system is debian 5.0 with kernel 2.6.26-2-xen from
distribution and 2.6.29-5 compiled, the problem occure with both kernels
ouput from debian 5.0/kernel 2.6.26-2-xen/xen-3.4.1-rc2
4.306723] PNP: No PS/2 controller found. Probing ports directly.
[ 4.323790] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 4.334853] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 4.346424] mice: PS/2 mouse device common for all mice
[ 4.361272] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 4.373302] rtc0: alarms up to one month, y3k
[ 4.384641] No iBFT detected.
[ 4.391310] TCP cubic registered
[ 4.398531] NET: Registered protocol family 17
[ 4.408450] Using IPI No-Shortcut mode
[ 4.417154] registered taskstats version 1
[ 4.425263] rtc_cmos 00:05: setting system clock to 2009-06-16
07:45:32 UTC (1245138332)
[ 4.442439] Freeing unused kernel memory: 196k freed
[ 4.490555] SCSI subsystem initialized
[ 4.502222] Fusion MPT base driver 3.04.06
[ 4.511363] Copyright (c) 1999-2007 LSI Corporation
[ 4.526520] Fusion MPT SAS Host driver 3.04.06
[ 4.536466] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level,
low) -> IRQ 16
[ 4.551871] mptbase: ioc0: Initiating bringup
[ 5.265020] ioc0: LSISAS1064E B2: Capabilities={Initiator}
[ 5.277276] no ownder
5.277276] no ownder
[ 5.282441] mptbase: ioc0: PCI-MSI enabled
[ 24.397417] mptbase: ioc0: Initiating recovery
[ 54.917063] mptbase: ioc0: Initiating recovery
[ 103.067093] scsi0 : ioc0: LSISAS1064E B2, FwRev=01182b00h, Ports=1,
MaxQ=286, IRQ=252
[ 113.084555] mptbase: ioc0: Initiating recovery
[ 143.599536] mptbase: ioc0: Initiating recovery
[ 163.416806] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 163.431202] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 163.472335] ACPI: ACPI0007:00 is registered as cooling_device0
[ 163.485371] ACPI: ACPI0007:01 is registered as cooling_device1
[ 163.498390] ACPI: ACPI0007:02 is registered as cooling_device2
[ 163.511391] ACPI: ACPI0007:03 is registered as cooling_device3
[ 163.524411] ACPI: ACPI0007:04 is registered as cooling_device4
[ 163.538190] ACPI: ACPI0007:05 is registered as cooling_device5
[ 163.551209] ACPI: ACPI0007:06 is registered as cooling_device6
[ 163.564227] ACPI: ACPI0007:07 is registered as cooling_device7
[ 163.828867] device-mapper: uevent: version 1.0.3
[ 163.842586] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18)
initialised: dm-devel@redhat.com
done
Begin: Waiting for root file system .... done
^^^^^^^^^ this is a last info from boot, system is waiting waiting
waiting, and after one minute system output info:
Gave up waiting for root device. Common problems:
ALERT! /dev/sda1 does not exist. Droping to a shell
OUTPUT from debian 5.0/kernel 2.6.29-5/xen-3.4.1-rc2
8.827982] Continuing...
[ 13.816968]
[ 13.857296] Fusion MPT base driver 3.04.07
[ 13.866466] Copyright (c) 1999-2008 LSI Corporation
[ 13.882142] Fusion MPT SAS Host driver 3.04.07
[ 13.892087] mptsas 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 13.907605] mptbase: ioc0: Initiating bringup
[ 14.620005] ioc0: LSISAS1064E B2: Capabilities={Initiator}
[ 23.755540] scsi4 : ioc0: LSISAS1064E B2, FwRev=01182b00h, Ports=1,
MaxQ=286, IRQ=16
[ 23.772844] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 23.788492] IP: [<e35027b6>] sas_host_setup+0x38/0x87
[scsi_transport_sas]
[ 23.803870] *pdpt = 000000015e06e001 *pde = 0000000000000000
[ 23.816828] Oops: 0002 [#1] SMP
[ 23.820333] last sysfs file:
[ 23.820333] Modules linked in: mptsas(+) mptscsih mptbase
scsi_transport_sas
[ 23.820333]
[ 23.820333] Pid: 542, comm: modprobe Not tainted (2.6.29.5 #1)
PRIMERGY RX100S5
[ 23.820333] EIP: 0061:[<e35027b6>] EFLAGS: 00010202 CPU: 0
[ 23.820333] EIP is at sas_host_setup+0x38/0x87 [scsi_transport_sas]
[ 23.820333] EAX: 00000008 EBX: 00000000 ECX: e3507ef4 EDX: e350448c
[ 23.820333] ESI: e04b3800 EDI: e04b38f0 EBP: e04b38f0 ESP: e0471e04
[ 23.820333] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069
[ 23.820333] Process modprobe (pid: 542, ti=e0470000 task=e18d6410
task.ti=e0470000)
[ 23.820333] Stack:
[ 23.820333] e350277e e04b9800 e04b9400 c0305179 e04b9800 e04b9414
c0305065 c0305167
[ 23.820333] e04b395c e04b38f0 e04b3800 e04b39fc e04b39fc c0334195
00000000 e04b3800
[ 23.820333] e04b38f0 c032c681 e04b3b14 00000044 e04b9600 e04b3800
e3556821 00000080
[ 23.820333] Call Trace:
[ 23.820333] [<e350277e>] sas_host_setup+0x0/0x87 [scsi_transport_sas]
[ 23.820333] [<c0305179>] transport_setup_classdev+0x12/0x17
[ 23.820333] [<c0305065>] attribute_container_add_device+0xb6/0xed
[ 23.820333] [<c0305167>] transport_setup_classdev+0x0/0x17
[ 23.820333] [<c0334195>] scsi_sysfs_add_host+0x46/0x5a
[ 23.820333] [<c032c681>] scsi_add_host+0x137/0x17c
[ 23.820333] [<e3556821>] mptsas_probe+0x2f6/0x38d [mptsas]
[ 23.820333] [<c02adaa1>] local_pci_probe+0xb/0xc
[ 23.820333] [<c02ae01a>] pci_device_probe+0x44/0x66
[ 23.820333] [<c030b00e>] pci_bus_probe_wrapper+0x3a/0x3e
[ 23.820333] [<c03031b8>] driver_probe_device+0x99/0x128
[ 23.820333] [<c0303290>] __driver_attach+0x49/0x67
[ 23.820333] [<c0302c28>] bus_for_each_dev+0x35/0x5b
[ 23.820333] [<c030306f>] driver_attach+0x11/0x13
[ 23.820333] [<c0303247>] __driver_attach+0x0/0x67
[ 23.820333] [<c03026ba>] bus_add_driver+0x91/0x1a1
[ 23.820333] [<e355d000>] mptsas_init+0x0/0xce [mptsas]
[ 23.820333] [<c0303411>] driver_register+0x7d/0xd3
[ 23.820333] [<e355d000>] mptsas_init+0x0/0xce [mptsas]
[ 23.820333] [<c02ae22a>] __pci_register_driver+0x32/0x60
[ 23.820333] [<e355d0ba>] mptsas_init+0xba/0xce [mptsas]
[ 23.820333] [<c0102044>] _stext+0x44/0x135
[ 23.820333] [<c0155fe1>] tracepoint_module_notify+0x21/0x24
[ 23.820333] [<c01366e6>] notifier_call_chain+0x2a/0x47
[ 23.820333] [<c013693b>] __blocking_notifier_call_chain+0x3f/0x49
[ 23.820333] [<c014178f>] sys_init_module+0x87/0x182
[ 23.820333] [<c010416e>] syscall_call+0x7/0xb
[ 23.820333] Code: db 75 04 31 f6 eb 11 89 d8 e8 cb 98 e2 dc 85 c0 74
ea 8d b3 10 ff ff ff 8b 9e 10 03 00 00 b9 f4 7e 50 e3 ba 8c 44 50 e3 8d
43 08 <89> 1b 89 5b 04 e8 08 2e c3 dc 31 d2 89 f0 c7 43 1c 00 00 00 00
[ 23.820333] EIP: [<e35027b6>] sas_host_setup+0x38/0x87
[scsi_transport_sas] SS:ESP 0069:e0471e04
[ 24.398885] ---[ end trace bacb629dbd15bdad ]---
[ 24.413968] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
My pci controller: 01:00.0 SCSI storage controller: LSI Logic / Symbios
Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 04)
If anyone had the same problem with mtpsas driver and xen 3.4. What has
been changed so it's not working on upper xen version.
The problem doesn't occure with xen 3.3.x
Albert
reply other threads:[~2009-06-18 10:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h1d6bk$ekf$1@ger.gmane.org' \
--to=forall@stalowka.info \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.