lkml.org 
[lkml]   [2008]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: linux-next: Tree for December 9
    On Wed, 10 Dec 2008 01:31:13 +0100 "Kay Sievers" <kay.sievers@vrfy.org> wrote:

    > > akpm2:/home/akpm# udevmonitor
    > > udevmonitor prints the received event from the kernel [UEVENT]
    > > and the event which udev sends out after rule processing [UDEV]
    > >
    > > UDEV [1228867146.103334] add@/class/bdi/9:0
    > > UDEV [1228867146.107566] remove@/block/md0
    > > UDEV [1228867146.111969] remove@/class/bdi/9:0
    > > UEVENT[1228867146.119889] add@/block/md0
    > > UEVENT[1228867146.119964] add@/class/bdi/9:0
    > > UEVENT[1228867146.120162] remove@/class/bdi/9:0
    > > UEVENT[1228867146.120205] remove@/block/md0
    > > UDEV [1228867146.122839] add@/block/md0
    > > UDEV [1228867146.129125] add@/class/bdi/9:0
    > > UDEV [1228867146.133459] remove@/block/md0
    > > UDEV [1228867146.137813] remove@/class/bdi/9:0
    > > UEVENT[1228867146.145652] add@/block/md0
    >
    > Weird loop, something is accessing /dev/md0, i guess, which creates
    > the kernel device, and the event, which accesses /dev/md0 again and it
    > goes crazy. Maybe caused by changes Neil did.

    I knew an Australian was to blame - it's just a matter of determining
    which one.

    > Do you use md devices on that box?

    Nope.


    \
     
     \ /
      Last update: 2008-12-10 02:33    [W:0.030 / U:0.040 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site