Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 May 2013 15:15:49 +0100
From:      "Steven Hartland" <>
To:        "Saxena, Sumit" <>, <>
Subject:   Re: LSI megaRAID controller: Kernel panic on virtual disk creation
Message-ID:  <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
That indeed doesn't look like look like an issue unrelated to driver.

Could you provide information on which version your running and what
the exact command you where running to create the panic?

While I'm here IIRC 9286 is a 2208 chipset card, so MegaRAI based,
which I did some significant fixes for our MFI driver in r247367 &
r247369 so might be worth reviewing to see if any of thats needed
in mrsas?

----- Original Message ----- 
> Hi ,
> While doing some testing on "mrsas" driver(LSIs' latest driver for next generation MegaRAID controllers- which will soon be 
> submitted to upstream kernel), I am facing kernel panic  while creating Virtual drive(RAID0) on LSI controller-9286-e (6 Gb/s 
> RAID controller). I am using latest upstream kernel.  The error message seen on panic is:
> "reboot after panic: Provider da1 lacks sectorsize"
> Below is the call stack:
> ----------------------------------------------
> kdb_enter() at kdb_enter+0x3e/frame 0xffffff8000285920
> vpanic() at vpanic+0x146/frame 0xffffff8000285960
> kassert_panic() at kassert_panic+0x136/frame 0xffffff80002859d0
> g_access() at g_access+0x3ba/frame 0xffffff8000285a60
> g_raid_md_taste_jmicron() at g_raid_md_taste_jmicron+0x6d/frame 0xffffff8000285b00
> g_raid_taste() at g_raid_taste+0x17f/frame 0xffffff8000285b50
> g_new_provider_event() at g_new_provider_event+0xda/frame 0xffffff8000285b70
> g_run_events() at g_run_events+0x1a7/frame 0xffffff8000285bb0
> fork_exit() at fork_exit+0x84/frame 0xffffff8000285bf0
> fork_trampoline() at fork_trampoline+0xe/frame 0xffffff8000285bf0
> --- trap 0, rip = 0, rsp = 0xffffff8000285cb0, rbp = 0 ---
> -------------------------------------------------
> "/dev/da1" is virtual drive created.
> The problem does not seems to be related to <mrsas> driver. call stack indicates that panic is observed  in GEOM module.
> Has someone face such issue earlier related to GEOM module?

This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to

Want to link to this message? Use this URL: <>