On Tue, 2009-03-17 at 17:04 -0700, Robert Love wrote: > On Tue, 2009-03-17 at 16:56 -0700, Vasu Dev wrote: > > On Tue, 2009-03-17 at 13:28 -0700, Robert Love wrote: > > > I'm encountering a BUG in our -features tree. I'm not sure why my > > > pre-posting testing didn't catch it and I don't know the root-cause yet > > > as I just started investigating. > > > > > > It happens immediately when attempting to 'create' an interface which > > > has a link to a non-FIP FCF. > > > > The latest fcoe-feature tree works for me with non-FIP FCF for basic > > testing, my each basic testing had some bs=512 bytes read and write > > working after create interface and then unloading stack. > > > > I had problem in pulling latest fcoe-feature tree, the git-pull failed > > with merge conflict errors. The pull failed due to merging this fix from > > Joe http://www.open-fcoe.org/pipermail/devel/2009-March/002046.html to > > existing fcoe cpu hotplug patches on tip. I reset my tree skipping all > > cpu hotplug patches and then pulled again to get-pull working on > > fcoe-feature again and same would be required for any pre-existing > > fcoe-feature unless they do fresh clone of fcoe-feature. > > > > how frequent you see this BUG ? If it happens on every create then very > > strange since I don't see same in my setup for several my BAT running. > > > > I'm seeing this every time I try to create an interface and I'm pretty > baffled as to why. I just finished the following- > > 1) clone scsi-misc > > 2) rebase to Linus' tip > > 3) apply 14 fcoe patches from linux-scsi > > 4) test > > 5) *boom* > > I'll push an updated -feature tree based on scsi-misc + patches straight > from the linux-scsi mailing list so you guys can try it. I'm also going
-features has been updated to be scsi-misc + 14 patches from linux-scsi mailing list. [-rc7] I've also pushed a scsi-misc, rebased to Linus' tree + 14 patches from linux-scsi as fcoe-features-rebase.git, but won't publish it on gitweb. [-rc8] I wiped everything I can think of and just tested -features again (after pushing as just mentioned) and I do _not_ have a problem anymore. I'll have to investigate this more tomorrow, I'm going to chalk it up to user error now since I don't have a root-cause. Thanks for testing for me. _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
