* Re: powerpc 476, Little-endian, pte fault
From: Michael Neuling @ 2011-10-31 5:51 UTC (permalink / raw)
To: Santosh Kumar; +Cc: linux-kernel, linuxppc-dev, Tony Breeds
In-Reply-To: <CAJw04pD24W_nGSLheWunCa_o7QqBmRf_TSAD44EkzazigRe_nQ@mail.gmail.com>
Adding linuxppc-dev list to the CC
> KERNEL: linux 2.6.39.4
> POWERPC: 476, little endian.
>
> I am trying to get linux 2.6.39.4 up on PPC 476 i have done done
> Big-endian to little endian Changes in:
Can you explain what you are trying to do in more detail? What does "i
have done Big-endian to little endian Changes" mean?
> 1) bitops header file.
> 2) while reading the device tree.
> 3) the PTE read/computed in head_32.S
> 4) added E bit in the TLB entries.
>
> with all the above changes the kernel_init is done but and inited is
> mounted.
Can you post your patch?
Are you trying to boot the kernel in little endian or just run userspace
in little endian?
> But while spawning init process the kernel continuously hits pte
> faults at address 0x100000fc and never comes out. Please let me know
> where i should be looking into.
Is this the very first userspace instruction?
Mikey
^ permalink raw reply
* Re: powerpc 476, Little-endian, pte fault
From: Michael Neuling @ 2011-10-31 5:51 UTC (permalink / raw)
To: Santosh Kumar; +Cc: linuxppc-dev, linux-kernel
In-Reply-To: <CAJw04pD24W_nGSLheWunCa_o7QqBmRf_TSAD44EkzazigRe_nQ@mail.gmail.com>
Adding linuxppc-dev list to the CC
> KERNEL: linux 2.6.39.4
> POWERPC: 476, little endian.
>
> I am trying to get linux 2.6.39.4 up on PPC 476 i have done done
> Big-endian to little endian Changes in:
Can you explain what you are trying to do in more detail? What does "i
have done Big-endian to little endian Changes" mean?
> 1) bitops header file.
> 2) while reading the device tree.
> 3) the PTE read/computed in head_32.S
> 4) added E bit in the TLB entries.
>
> with all the above changes the kernel_init is done but and inited is
> mounted.
Can you post your patch?
Are you trying to boot the kernel in little endian or just run userspace
in little endian?
> But while spawning init process the kernel continuously hits pte
> faults at address 0x100000fc and never comes out. Please let me know
> where i should be looking into.
Is this the very first userspace instruction?
Mikey
^ permalink raw reply
* Question: kick SDIO irq when resume
From: Jun Nie @ 2011-10-31 5:50 UTC (permalink / raw)
To: Nicolas Pitre, Bing Zhao, frankh, yongd, tianfh, njun; +Cc: linux-mmc
Hi Nico,
We are debugging fake SDIO irq when 8787 SDIO card resume and
found below patch. The issue is that 8787 driver can not handle card
irq if neither 8787 nor host trigger resume event in some cases. Do
you remember what SDIO card need below patch? What's your idea on this
issue? How about add a SDIO function flag to decide the irq thread
kick off in resume?
Thanks!
commit 40216842dca4fa485cb1aa5eb231149a4a57cc85
Author: Nicolas Pitre <nico@fluxnic.net>
Date: Fri Mar 5 13:43:34 2010 -0800
sdio: kick the interrupt thread upon a resume
Jun
^ permalink raw reply
* Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
From: NeilBrown @ 2011-10-31 5:49 UTC (permalink / raw)
To: Brad Campbell; +Cc: linux RAID
In-Reply-To: <4EAE3352.8090409@fnarfbargle.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Mon, 31 Oct 2011 13:34:10 +0800 Brad Campbell <lists2009@fnarfbargle.com>
wrote:
> On 31/10/11 13:04, Brad Campbell wrote:
> > On 31/10/11 10:08, NeilBrown wrote:
> >>
> >> Hi Linus et al,
> >>
> >> I just discovered a fairly serious flaw that I introduced into 3.1 -
> >> details
> >> below.
> >>
> >> Anyone running RAID10 with 3.1 is advised to either apply this patch or
> >> revert an earlier kernel as soon as possible. In the mean time, remove
> >> any
> >> hot spares from an RAID10 array.
> >>
> >
> > G'day Neil,
> >
> > Is that the issue I bumped up against here?
> >
> > http://permalink.gmane.org/gmane.linux.raid/35805
>
> After looking closer I can confirm that making the indicated change
> resolves this problem.
Yes, definitely the same problem.
It's a shame I didn't pay proper attention to that report at the time - I
think that was the day that the uSD in my phone died and I was somewhat
distracted trying to figure out how to rebuild the install from scratch :-(
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply
* [U-Boot] [PATCH v5 09/11] arm926ejs, davinci: add cpuinfo for dm365
From: Prabhakar Lad @ 2011-10-31 5:46 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1320036790-24283-10-git-send-email-hs@denx.de>
Hi Heiko,
I already see a patch for printing cpu info for dm365(rather for all
davinci family) .
Link for the patch<http://www.mail-archive.com/u-boot@lists.denx.de/msg65514.html>,
which is more cleaner.
Regards
--Prabhakar Lad
On Mon, Oct 31, 2011 at 10:23 AM, Heiko Schocher <hs@denx.de> wrote:
> Signed-off-by: Heiko Schocher <hs@denx.de>
> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
> Cc: Sandeep Paulraj <s-paulraj@ti.com>
>
> ---
> Changes for v2:
> - rebase to TOT
>
> arch/arm/cpu/arm926ejs/davinci/cpu.c | 27
> ++++++++++++++++++++++++-
> arch/arm/include/asm/arch-davinci/pll_defs.h | 4 +++
> 2 files changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/cpu/arm926ejs/davinci/cpu.c
> b/arch/arm/cpu/arm926ejs/davinci/cpu.c
> index 02819f6..9ea9785 100644
> --- a/arch/arm/cpu/arm926ejs/davinci/cpu.c
> +++ b/arch/arm/cpu/arm926ejs/davinci/cpu.c
> @@ -146,13 +146,15 @@ static inline unsigned pll_prediv(volatile void
> *pllbase)
> return 8;
> else
> return pll_div(pllbase, PLLC_PREDIV);
> +#elif defined(CONFIG_SOC_DM365)
> + return pll_div(pllbase, PLLC_PREDIV);
> #endif
> return 1;
> }
>
> static inline unsigned pll_postdiv(volatile void *pllbase)
> {
> -#ifdef CONFIG_SOC_DM355
> +#if defined(CONFIG_SOC_DM355) || defined(CONFIG_SOC_DM365)
> return pll_div(pllbase, PLLC_POSTDIV);
> #elif defined(CONFIG_SOC_DM6446)
> if (pllbase == (volatile void *)DAVINCI_PLL_CNTRL0_BASE)
> @@ -171,9 +173,13 @@ static unsigned pll_sysclk_mhz(unsigned pll_addr,
> unsigned div)
> #endif
>
> /* the PLL might be bypassed */
> - if (REG(pllbase + PLLC_PLLCTL) & BIT(0)) {
> + if (readl(pllbase + PLLC_PLLCTL) & BIT(0)) {
> base /= pll_prediv(pllbase);
> +#if defined(CONFIG_SOC_DM365)
> + base *= 2 * (readl(pllbase + PLLC_PLLM) & 0x0ff);
> +#else
> base *= 1 + (REG(pllbase + PLLC_PLLM) & 0x0ff);
> +#endif
> base /= pll_postdiv(pllbase);
> }
> return DIV_ROUND_UP(base, 1000 * pll_div(pllbase, div));
> @@ -184,8 +190,13 @@ int print_cpuinfo(void)
> /* REVISIT fetch and display CPU ID and revision information
> * too ... that will matter as more revisions appear.
> */
> +#if defined(CONFIG_SOC_DM365)
> + printf("Cores: ARM %d MHz",
> + pll_sysclk_mhz(DAVINCI_PLL_CNTRL1_BASE,
> ARM_PLLDIV));
> +#else
> printf("Cores: ARM %d MHz",
> pll_sysclk_mhz(DAVINCI_PLL_CNTRL0_BASE,
> ARM_PLLDIV));
> +#endif
>
> #ifdef DSP_PLLDIV
> printf(", DSP %d MHz",
> @@ -194,8 +205,13 @@ int print_cpuinfo(void)
>
> printf("\nDDR: %d MHz\n",
> /* DDR PHY uses an x2 input clock */
> +#if defined(CONFIG_SOC_DM365)
> + pll_sysclk_mhz(DAVINCI_PLL_CNTRL0_BASE, DDR_PLLDIV)
> + / 2);
> +#else
> pll_sysclk_mhz(DAVINCI_PLL_CNTRL1_BASE, DDR_PLLDIV)
> / 2);
> +#endif
> return 0;
> }
>
> @@ -205,6 +221,13 @@ unsigned int davinci_arm_clk_get()
> return pll_sysclk_mhz(DAVINCI_PLL_CNTRL0_BASE, ARM_PLLDIV) *
> 1000000;
> }
> #endif
> +
> +#if defined(CONFIG_SOC_DM365)
> +unsigned int davinci_clk_get(unsigned int div)
> +{
> + return pll_sysclk_mhz(DAVINCI_PLL_CNTRL0_BASE, div) * 1000000;
> +}
> +#endif
> #endif /* CONFIG_DISPLAY_CPUINFO */
> #endif /* !CONFIG_SOC_DA8XX */
>
> diff --git a/arch/arm/include/asm/arch-davinci/pll_defs.h
> b/arch/arm/include/asm/arch-davinci/pll_defs.h
> index 5d37616..606ed0b 100644
> --- a/arch/arm/include/asm/arch-davinci/pll_defs.h
> +++ b/arch/arm/include/asm/arch-davinci/pll_defs.h
> @@ -76,4 +76,8 @@ struct dv_pll_regs {
> #define dv_pll0_regs ((struct dv_pll_regs *)DAVINCI_PLL_CNTRL0_BASE)
> #define dv_pll1_regs ((struct dv_pll_regs *)DAVINCI_PLL_CNTRL1_BASE)
>
> +#define ARM_PLLDIV (offsetof(struct dv_pll_regs, plldiv2))
> +#define DDR_PLLDIV (offsetof(struct dv_pll_regs, plldiv7))
> +
> +unsigned int davinci_clk_get(unsigned int div);
> #endif /* _DV_PLL_DEFS_H_ */
> --
> 1.7.6.4
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
^ permalink raw reply
* Re: [PATCH 00/36] m68k: ColdFire MMU support
From: Greg Ungerer @ 2011-10-31 5:46 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux-m68k, uclinux-dev
In-Reply-To: <CAMuHMdX_W5_nW=KYmT4UC-gd7d=J0=2_ZcyZVZkH7nnXgy-Kxg@mail.gmail.com>
Hi Geert,
On 30/10/11 23:47, Geert Uytterhoeven wrote:
> On Tue, Oct 25, 2011 at 09:18,<gerg@snapgear.com> wrote:
>> The following patch set adds support for running the V4e ColdFire cores
>> with their MMU enabled. This is very much a request for comments. I expect
>> a lot more cleanup is required here. But this is a start.
>
> I replied a few comments to the individual patches, but in general it looks
> OK, so you can add my Acked-by.
Thats great, thanks, I really appreciate the review.
I will probably send a v2 after you have pushed the IRQ changes.
No doubt a couple of changes can be dropped from this patch set then.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
^ permalink raw reply
* Re: [Qemu-devel] [0/12] Preliminary work for IOMMU emulation support (v2)
From: David Gibson @ 2011-10-31 5:40 UTC (permalink / raw)
To: Michael S. Tsirkin
Cc: aliguori, joerg.roedel, Alexander Graf, qemu-devel, avi,
eduard.munteanu, rth
In-Reply-To: <20111030175252.GA30156@redhat.com>
On Sun, Oct 30, 2011 at 07:52:54PM +0200, Michael S. Tsirkin wrote:
> On Sun, Oct 30, 2011 at 06:20:46PM +0100, Alexander Graf wrote:
> >
> > On 14.10.2011, at 11:20, David Gibson wrote:
> >
> > > A while back, Eduard - Gabriel Munteanu send a series of patches
> > > implementing support for emulating the AMD IOMMU in conjunction with
> > > qemu emulated PCI devices. A revised patch series added support for
> > > the Intel IOMMU, and I also send a revised version of this series
> > > which added support for the hypervisor mediated IOMMU on the pseries
> > > machine.
> > >
> > > Richard Henderson also weighed in on the discussion, and there's still
> > > a cretain amount to be thrashed out in terms of exactly how to set up
> > > an IOMMU / DMA translation subsystem.
> > >
> > > However, really only 2 or 3 patches in any of these series have
> > > contained anything interesting. The rest of the series has been
> > > converting existing PCI emulated devices to use the new DMA interface
> > > which worked through the IOMMU translation, whatever it was. While we
> > > keep working out what we want for the guts of the IOMMU support, these
> > > device conversion patches keep bitrotting against updates to the
> > > various device implementations themselves.
> > >
> > > Really, regardless of whether we're actually implementing IOMMU
> > > translation, it makes sense that qemu code should distinguish between
> > > when it is really operating in CPU physical addresses and when it is
> > > operating in bus or DMA addresses which might have some kind of
> > > translation into physical addresses.
> > >
> > > This series, therefore, begins the conversion of existing PCI device
> > > emulation code to use new (stub) pci dma access functions. These are,
> > > for now, just defined to be untranslated cpu physical memory accesses,
> > > as before, but has three advantages:
> > >
> > > * It becomes obvious where the code is working with dma addresses,
> > > so it's easier to grep for what might be affected by an IOMMU or
> > > other bus address translation.
> > >
> > > * The new stubs take the PCIDevice *, from which any of the various
> > > suggested IOMMU interfaces should be able to locate the correct
> > > IOMMU translation context.
> > >
> > > * The new pci_dma_{read,write}() functions have a return value.
> > > When we do have IOMMU support, translation failures could lead to
> > > these functions failing, so we want a way to report it.
> > >
> > > This series converts all the easy cases. It doesn't yet handle
> > > devices which have both PCI and non-PCI variants, such as AHCI, OHCI
> > > and ne2k. Unlike the earlier version of this series, functions using
> > > scatter gather _are_ covered, though.
> >
> > Michael, ping?
>
> It's unfortunate that v2 of the patchset doesn't
> include a changelog, which makes one reread all
> of the patchset before responding.
Ah, sorry, it slipped my mind. I'll make sure to do a changelog for
the next iteration.
> I still think just making stX_phys/ldX_phys do memcpy is wrong:
> the former guaranteed atomic access, the later doesn't
> give any access order guarantees.
>
> We do need atomic versions IMO.
Yeah, I think you're right. I've changed my next version to call
stX_phys/ldX_phys instead of going to the dma_rw function.
> If you think we need the non-ordered unaligned version
> of stl_XXX as well, the atomic versions could get an
> _atomic suffix, or the non-atomic versions _nonatomic suffix.
>
> I think I showed an example in e1000 which doesn't currently
> use stX_phys/ldX_phys but really should - otherwise
> the valid bit might get flipped before data is written
> (or it could do two cpu_physical_memory_XXX to ensure
> ordering but that's rather inconvenient IMO).
>
> intel-hda does something similar, I don't know whether ordering
> matters there, but this patch sneaks in a semantic change into
> what should have been a harmless rework.
>
> Also, could the stub functions be made inline? That'd make
> the intent clearer IMO.
So, I would have preferred to use inlines from the beginning, but I
ran into problems because I needed some of the poisoned functions that
couldn't be used in files included anywhere in libhw. However, since
then other changes have meant those poisoned functions are no longer
needed even for inlines, but I hadn't realised that until you pointed
it out. Next version has them as inlines.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
^ permalink raw reply
* [PATCH V6] SDHCI: S3C: Use generic clock names for sdhci bus clock options
From: Rajeshwari Shinde @ 2011-10-31 5:44 UTC (permalink / raw)
To: linux-arm-kernel
This patch modifies the driver to stop depending on the clock names
being passed from the platform and switch over to bus clock lookup
using generic clock names.
V6 Changes:
Changed sprintf to snprintf as suggested by Chris Ball.
Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com>
---
drivers/mmc/host/sdhci-s3c.c | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/mmc/host/sdhci-s3c.c b/drivers/mmc/host/sdhci-s3c.c
index 82709b6..488223c 100644
--- a/drivers/mmc/host/sdhci-s3c.c
+++ b/drivers/mmc/host/sdhci-s3c.c
@@ -435,14 +435,11 @@ static int __devinit sdhci_s3c_probe(struct platform_device *pdev)
for (clks = 0, ptr = 0; ptr < MAX_BUS_CLK; ptr++) {
struct clk *clk;
- char *name = pdata->clocks[ptr];
-
- if (name == NULL)
- continue;
+ char name[14];
+ snprintf(name, 14, "mmc_busclk.%d", ptr);
clk = clk_get(dev, name);
if (IS_ERR(clk)) {
- dev_err(dev, "failed to get clock %s\n", name);
continue;
}
--
1.7.4.4
^ permalink raw reply related
* [PATCH V6] SDHCI: S3C: Use generic clock names for sdhci bus clock options
From: Rajeshwari Shinde @ 2011-10-31 5:44 UTC (permalink / raw)
To: linux-mmc, linux-samsung-soc, cjb; +Cc: kgene.kim, linux-arm-kernel
This patch modifies the driver to stop depending on the clock names
being passed from the platform and switch over to bus clock lookup
using generic clock names.
V6 Changes:
Changed sprintf to snprintf as suggested by Chris Ball.
Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com>
---
drivers/mmc/host/sdhci-s3c.c | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/mmc/host/sdhci-s3c.c b/drivers/mmc/host/sdhci-s3c.c
index 82709b6..488223c 100644
--- a/drivers/mmc/host/sdhci-s3c.c
+++ b/drivers/mmc/host/sdhci-s3c.c
@@ -435,14 +435,11 @@ static int __devinit sdhci_s3c_probe(struct platform_device *pdev)
for (clks = 0, ptr = 0; ptr < MAX_BUS_CLK; ptr++) {
struct clk *clk;
- char *name = pdata->clocks[ptr];
-
- if (name == NULL)
- continue;
+ char name[14];
+ snprintf(name, 14, "mmc_busclk.%d", ptr);
clk = clk_get(dev, name);
if (IS_ERR(clk)) {
- dev_err(dev, "failed to get clock %s\n", name);
continue;
}
--
1.7.4.4
^ permalink raw reply related
* Re: [PATCH 24/36] m68k: compile appropriate mm arch files for ColdFire V4e MMU support
From: Greg Ungerer @ 2011-10-31 5:39 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux-m68k, uclinux-dev, Greg Ungerer
In-Reply-To: <CAMuHMdUZqddsHwWoBqnB+nLBRqHOGOVZwqzoZGC0FEByDwA8kw@mail.gmail.com>
Hi Geert,
On 30/10/11 23:46, Geert Uytterhoeven wrote:
> On Tue, Oct 25, 2011 at 09:19,<gerg@snapgear.com> wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> Compile the mcfmmu.c code when the ColdFire V4e MMU is enabled.
>> And don't compile the unnecessary hwtest.c code for it.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>> ---
>> arch/m68k/mm/Makefile | 8 +++++++-
>> 1 files changed, 7 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/m68k/mm/Makefile b/arch/m68k/mm/Makefile
>> index 09cadf1..1732e31 100644
>> --- a/arch/m68k/mm/Makefile
>> +++ b/arch/m68k/mm/Makefile
>> @@ -4,6 +4,12 @@
>>
>> obj-y := init.o
>>
>> -obj-$(CONFIG_MMU) += cache.o fault.o hwtest.o
>> +obj-$(CONFIG_MMU) += cache.o fault.o
>> obj-$(CONFIG_MMU_MOTOROLA) += kmap.o memory.o motorola.o
>> obj-$(CONFIG_MMU_SUN3) += sun3kmap.o sun3mmu.o
>> +
>> +ifdef CONFIG_COLDFIRE
>> +obj-$(CONFIG_MMU) += kmap.o memory.o mcfmmu.o
>
> What about introducing CONFIG_MMU_COLDFIRE and writing
>
> obj-$(CONFIG_MMU_MOTOROLA) += kmap.o memory.o mcfmmu.o
>
> instead?
>
> It could turn out to be useful in other places too, especially when considering
> merging more mm/no sources files.
Yep, that is much nice. I'll change it.
Thanks
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
^ permalink raw reply
* Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
From: Brad Campbell @ 2011-10-31 5:34 UTC (permalink / raw)
To: NeilBrown; +Cc: linux RAID
In-Reply-To: <4EAE2C62.3030506@fnarfbargle.com>
On 31/10/11 13:04, Brad Campbell wrote:
> On 31/10/11 10:08, NeilBrown wrote:
>>
>> Hi Linus et al,
>>
>> I just discovered a fairly serious flaw that I introduced into 3.1 -
>> details
>> below.
>>
>> Anyone running RAID10 with 3.1 is advised to either apply this patch or
>> revert an earlier kernel as soon as possible. In the mean time, remove
>> any
>> hot spares from an RAID10 array.
>>
>
> G'day Neil,
>
> Is that the issue I bumped up against here?
>
> http://permalink.gmane.org/gmane.linux.raid/35805
After looking closer I can confirm that making the indicated change
resolves this problem.
Regards,
Brad
^ permalink raw reply
* Re: Multi-partition block layer behaviour
From: Shaohua Li @ 2011-10-31 5:39 UTC (permalink / raw)
To: Tiju Jacob; +Cc: linux-kernel@vger.kernel.org
In-Reply-To: <CADAg6uy2xOoAaAhVg07oYia+AZAuOGKywPGx8fvT0EF4ThuKCQ@mail.gmail.com>
On Mon, 2011-10-31 at 12:35 +0800, Tiju Jacob wrote:
> On Thu, Oct 27, 2011 at 6:12 AM, Shaohua Li <shaohua.li@intel.com> wrote:
> > On Wed, 2011-10-26 at 18:10 +0800, Tiju Jacob wrote:
> >> >> 1. When an I/O request is made to the filesystem, process 'A' acquires
> >> >> a mutex FS lock and a mutex block driver lock.
> >> >>
> >> >> 2. Process 'B' tries to acquire the mutex FS lock, which is not
> >> >> available. Hence, it goes to sleep. Due to the new plugging mechanism,
> >> >> before going to sleep, shcedule() is invoked which disables preemption
> >> >> and the context becomes atomic. In schedule(), the newly added
> >> >> blk_flush_plug_list() is invoked which unplugs the block driver.
> >> >>
> >> >> 3) During unplug operation the block driver tries to acquire the mutex
> >> >> lock which fails, because the lock was held by process 'A'. Previous
> >> >> invocation of scheudle() in step 2 has already made the context as
> >> >> atomic, hence the error "Schedule while atomic" occured.
> >> > if blk_flush_plug_list() is called in schedule(), it will use
> >> > blk_run_queue_async
> >> > to unplug the queue. This runs in a workqueue. So how could this happen?
> >> >
> >>
> >> The call stack goes as follows:
> >>
> >> From schedule() it calls blk_schedule_flush_plug() and
> >> blk_flush_plug_list() gets invoked.
> >>
> >> In blk_flush_plug_list() queue_unplugged() does not get invoked. Hence
> >> blk_run_queue_async is not called.
> >> Instead __elv_add_request() is invoked with ELEVATOR_INSERT_SORT_MERGE
> >> flag and the flag gets reassigned to ELEVATOR_INSERT_BACK.
> >>
> >> In ELEVATOR_INSERT_BACK, __blk_run_queue() gets invoked and calls request_fn().
>
> > This doesn't make sense. why the flag is changed from
> > ELEVATOR_INSERT_SORT_MERGE to ELEVATOR_INSERT_BACK?
>
> In __elv_add_request() "where" gets reassigned as follows:
>
> } else if (!(rq->cmd_flags & REQ_ELVPRIV) &&
> (where == ELEVATOR_INSERT_SORT ||
> where == ELEVATOR_INSERT_SORT_MERGE))
> where = ELEVATOR_INSERT_BACK;
>
ok, thanks. So this means the elevator is switching in the test. How
about below patch:
diff --git a/block/elevator.c b/block/elevator.c
index a3b64bc..e14824a 100644
--- a/block/elevator.c
+++ b/block/elevator.c
@@ -683,8 +683,13 @@ void __elv_add_request(struct request_queue *q, struct request *rq, int where)
* - Usually, back inserted requests won't be merged
* with anything. There's no point in delaying queue
* processing.
+ * If elevator is switching, doesn't need run the queue.
+ * elevator switching will run it anyway. And this could
+ * cause warning since the code might run in atomic
+ * environment(blk_flush_plug_list() callbed in schedule())
*/
- __blk_run_queue(q);
+ if (!test_bit(QUEUE_FLAG_ELVSWITCH, &q->queue_flags))
+ __blk_run_queue(q);
break;
case ELEVATOR_INSERT_SORT_MERGE:
^ permalink raw reply related
* powerpc 476, Little-endian, pte fault
From: Santosh Kumar @ 2011-10-31 5:30 UTC (permalink / raw)
To: linux-kernel
KERNEL: linux 2.6.39.4
POWERPC: 476, little endian.
I am trying to get linux 2.6.39.4 up on PPC 476 i have done done
Big-endian to little endian Changes in:
1) bitops header file.
2) while reading the device tree.
3) the PTE read/computed in head_32.S
4) added E bit in the TLB entries.
with all the above changes the kernel_init is done but and inited is mounted.
But while spawning init process the kernel continuously hits pte
faults at address 0x100000fc and never comes out. Please let me know
where i should be looking into.
-
Thanks
Santosh Kumar .A
Vision without Action is a daydream... Action without Vision is a nightmare...
^ permalink raw reply
* [Bug 42409] Mesa 7.12-devel /dri/r600 compilation error: no makefile found
From: bugzilla-daemon @ 2011-10-31 5:27 UTC (permalink / raw)
To: dri-devel
In-Reply-To: <bug-42409-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42409
--- Comment #1 from Jos van Wolput <wolput@onsneteindhoven.nl> 2011-10-30 22:27:17 PDT ---
I understand the dri r600 driver has been removed, isn't it?
So this issue is not a bug and can be closed.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply
* [meta-oe][PATCH] opencv: import from oe-classic and upgrade to 2.3.1
From: Connor Abbott @ 2011-10-31 5:20 UTC (permalink / raw)
To: openembedded-devel
OpenCV <= 2.2 won't compile on oe-core due to the lack of v4l1 headers, and therefore wasn't included in this patch. Also, the support for newer cv2-style python bindings is a bit hacked up at the moment due to the way OpenCV detects the Python version and Numpy headers (see 0001-Fix-CMakeLists.txt-numpy-detection.patch). In particular, it requires the native & target python to be the same version and have similar site-packages directories, which is true at least for now in OE.
Signed-off-by: Connor Abbott <cwabbott0@gmail.com>
---
.../recipes-support/opencv/opencv-samples_2.3.bb | 43 +++++++++++
.../0001-Fix-CMakeLists.txt-numpy-detection.patch | 37 ++++++++++
meta-oe/recipes-support/opencv/opencv_2.3.bb | 76 ++++++++++++++++++++
3 files changed, 156 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-support/opencv/opencv-samples_2.3.bb
create mode 100644 meta-oe/recipes-support/opencv/opencv/0001-Fix-CMakeLists.txt-numpy-detection.patch
create mode 100644 meta-oe/recipes-support/opencv/opencv_2.3.bb
diff --git a/meta-oe/recipes-support/opencv/opencv-samples_2.3.bb b/meta-oe/recipes-support/opencv/opencv-samples_2.3.bb
new file mode 100644
index 0000000..5cac4a5
--- /dev/null
+++ b/meta-oe/recipes-support/opencv/opencv-samples_2.3.bb
@@ -0,0 +1,43 @@
+DESCRIPTION = "Opencv : The Open Computer Vision Library"
+HOMEPAGE = "http://opencv.willowgarage.com/wiki/"
+SECTION = "libs"
+PRIORITY = "optional"
+LICENSE = "BSD"
+
+DEPENDS = "opencv"
+
+LIC_FILES_CHKSUM = "file://include/opencv2/opencv.hpp;endline=41;md5=6d690d8488a6fca7a2c192932466bb14 \
+"
+
+SRC_URI = "svn://code.ros.org/svn/opencv/tags/2.3.1;module=opencv;proto=https \
+"
+
+SRCREV = "6923"
+PV = "2.3.1"
+PR = "r0"
+
+S = "${WORKDIR}/opencv"
+
+do_install() {
+ cd samples/c
+ install -d ${D}/${bindir}
+ install -d ${D}/${datadir}/opencv/samples
+
+ cp * ${D}/${datadir}/opencv/samples || true
+
+ for i in *.c; do
+ echo "compiling $i"
+ ${CXX} ${CFLAGS} ${LDFLAGS} -ggdb `pkg-config --cflags opencv` -o `basename $i .c` $i `pkg-config --libs opencv` || true
+ install -m 0755 `basename $i .c` ${D}/${bindir} || true
+ rm ${D}/${datadir}/opencv/samples/`basename $i .c` || true
+ done
+ for i in *.cpp; do
+ echo "compiling $i"
+ ${CXX} ${CFLAGS} ${LDFLAGS} -ggdb `pkg-config --cflags opencv` -o `basename $i .cpp` $i `pkg-config --libs opencv` || true
+ install -m 0755 `basename $i .cpp` ${D}/${bindir} || true
+ rm ${D}/${datadir}/opencv/samples/`basename $i .cpp` || true
+ done
+}
+
+FILES_${PN}-dev += "${datadir}/opencv/samples/*.c* ${datadir}/opencv/samples/*.vcp* ${datadir}/opencv/samples/build*"
+FILES_${PN} += "${bindir} ${datadir}/opencv"
diff --git a/meta-oe/recipes-support/opencv/opencv/0001-Fix-CMakeLists.txt-numpy-detection.patch b/meta-oe/recipes-support/opencv/opencv/0001-Fix-CMakeLists.txt-numpy-detection.patch
new file mode 100644
index 0000000..dba00f8
--- /dev/null
+++ b/meta-oe/recipes-support/opencv/opencv/0001-Fix-CMakeLists.txt-numpy-detection.patch
@@ -0,0 +1,37 @@
+From a7301911a3cdf9196abd93ff894a9e86e0bcdc5e Mon Sep 17 00:00:00 2001
+From: Connor Abbott <cwabbott0@gmail.com>
+Date: Sun, 30 Oct 2011 20:00:03 -0400
+Subject: [PATCH] Fix CMakeLists.txt numpy detection
+
+Right now, the code opencv uses to detect where the numpy include files are doesn't work with cross-compiling because it uses the native python to determine the environment. To make this a little better, allow the user to explictly specify the path using -DPYTHON_NUMPY_INCLUDE_DIRS=path/to/numpy/include/dir .
+Signed-off-by: Connor Abbott <cwabbott0@gmail.com>
+---
+ CMakeLists.txt | 12 ++++++++----
+ 1 files changed, 8 insertions(+), 4 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index ff8f20c..8edbd78 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -715,10 +715,14 @@ IF ("${PYTHON_VERSION_MAJOR_MINOR}" VERSION_GREATER 2.4)
+ ENDIF()
+
+ # Attempt to discover the NumPy include directory. If this succeeds, then build python API with NumPy
+-execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import os; os.environ['DISTUTILS_USE_SDK']='1'; import numpy.distutils; print numpy.distutils.misc_util.get_numpy_include_dirs()[0]"
+- RESULT_VARIABLE PYTHON_NUMPY_PROCESS
+- OUTPUT_VARIABLE PYTHON_NUMPY_INCLUDE_DIRS
+- OUTPUT_STRIP_TRAILING_WHITESPACE)
++if(NOT DEFINED PYTHON_NUMPY_INCLUDE_DIRS)
++ execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import os; os.environ['DISTUTILS_USE_SDK']='1'; import numpy.distutils; print numpy.distutils.misc_util.get_numpy_include_dirs()[0]"
++ RESULT_VARIABLE PYTHON_NUMPY_PROCESS
++ OUTPUT_VARIABLE PYTHON_NUMPY_INCLUDE_DIRS
++ OUTPUT_STRIP_TRAILING_WHITESPACE)
++else()
++ set(PYTHON_NUMPY_PROCESS 0)
++endif()
+
+ if(PYTHON_NUMPY_PROCESS EQUAL 0)
+ set(PYTHON_USE_NUMPY 1)
+--
+1.7.4.1
+
diff --git a/meta-oe/recipes-support/opencv/opencv_2.3.bb b/meta-oe/recipes-support/opencv/opencv_2.3.bb
new file mode 100644
index 0000000..220116d
--- /dev/null
+++ b/meta-oe/recipes-support/opencv/opencv_2.3.bb
@@ -0,0 +1,76 @@
+DESCRIPTION = "Opencv : The Open Computer Vision Library"
+HOMEPAGE = "http://opencv.willowgarage.com/wiki/"
+SECTION = "libs"
+PRIORITY = "optional"
+LICENSE = "BSD"
+
+ARM_INSTRUCTION_SET = "arm"
+
+LIC_FILES_CHKSUM = "file://include/opencv2/opencv.hpp;endline=41;md5=6d690d8488a6fca7a2c192932466bb14 \
+"
+
+DEPENDS = "python-numpy ffmpeg gtk+ libtool swig swig-native python jpeg bzip2 zlib libpng tiff glib-2.0"
+
+SRC_URI = "svn://code.ros.org/svn/opencv/tags/2.3.1;module=opencv;proto=https \
+file://opencv/0001-Fix-CMakeLists.txt-numpy-detection.patch \
+"
+
+SRCREV = "6923"
+
+PV = "2.3.1"
+PR = "r0"
+
+S = "${WORKDIR}/opencv"
+
+EXTRA_OECMAKE = "-DPYTHON_NUMPY_INCLUDE_DIRS=${STAGING_LIBDIR}/${PYTHON_DIR}/site-packages/numpy/core/include \
+-DBUILD_PYTHON_SUPPORT=ON \
+"
+
+inherit distutils-base pkgconfig cmake
+
+export BUILD_SYS
+export HOST_SYS
+export PYTHON_CSPEC="-I${STAGING_INCDIR}/${PYTHON_DIR}"
+export PYTHON=${STAGING_BINDIR_NATIVE}/python
+
+TARGET_CC_ARCH += "-I${S}/include "
+
+PACKAGES += "${PN}-apps python-opencv"
+
+python populate_packages_prepend () {
+ cv_libdir = bb.data.expand('${libdir}', d)
+ cv_libdir_dbg = bb.data.expand('${libdir}/.debug', d)
+ do_split_packages(d, cv_libdir, '^lib(.*)\.so$', 'lib%s-dev', 'OpenCV %s development package', extra_depends='${PN}-dev', allow_links=True)
+ do_split_packages(d, cv_libdir, '^lib(.*)\.la$', 'lib%s-dev', 'OpenCV %s development package', extra_depends='${PN}-dev')
+ do_split_packages(d, cv_libdir, '^lib(.*)\.a$', 'lib%s-dev', 'OpenCV %s development package', extra_depends='${PN}-dev')
+ do_split_packages(d, cv_libdir, '^lib(.*)\.so\.*', 'lib%s', 'OpenCV %s library', extra_depends='', allow_links=True)
+
+ pn = bb.data.getVar('PN', d, 1)
+ metapkg = pn + '-dev'
+ bb.data.setVar('ALLOW_EMPTY_' + metapkg, "1", d)
+ blacklist = [ metapkg ]
+ metapkg_rdepends = [ ]
+ packages = bb.data.getVar('PACKAGES', d, 1).split()
+ for pkg in packages[1:]:
+ if not pkg in blacklist and not pkg in metapkg_rdepends and pkg.endswith('-dev'):
+ metapkg_rdepends.append(pkg)
+ bb.data.setVar('RRECOMMENDS_' + metapkg, ' '.join(metapkg_rdepends), d)
+}
+
+FILES_${PN} = ""
+FILES_${PN}-apps = "${bindir}/* ${datadir}/OpenCV"
+FILES_${PN}-dbg += "${libdir}/.debug"
+FILES_${PN}-dev = "${includedir} ${libdir}/pkgconfig"
+FILES_${PN}-doc = "${datadir}/OpenCV/doc"
+
+ALLOW_EMPTY_${PN} = "1"
+
+INSANE_SKIP_python-opencv = True
+DESCRIPTION_python-opencv = "Python bindings to opencv"
+FILES_python-opencv = "${PYTHON_SITEPACKAGES_DIR}/*"
+RDEPENDS_python-opencv = "python-core python-numpy"
+
+do_install_append() {
+ cp ${S}/include/opencv/*.h ${D}${includedir}/opencv/
+ sed -i '/blobtrack/d' ${D}${includedir}/opencv/cvaux.h
+}
\ No newline at end of file
--
1.7.4.1
^ permalink raw reply related
* Re: [PATCH 2/3] OMAP: SPI: call pm_runtime_disable in error path and remove
From: Shubhrajyoti @ 2011-10-31 5:16 UTC (permalink / raw)
To: Grant Likely; +Cc: spi-devel-general, Hebbar, Gururaja, linux-kernel
In-Reply-To: <20111029120655.GE22592@ponder.secretlab.ca>
On Saturday 29 October 2011 05:36 PM, Grant Likely wrote:
> On Fri, Oct 28, 2011 at 05:14:18PM +0530, Shubhrajyoti D wrote:
>> omap mcspi probe() doesnt call pm_runtime disable functions
>> in case of failure. remove() doesnt call pm_runtime disable. This could
>> lead to warnings as below on subsequent insmod.
>>
>> ~# insmod spi-omap2-mcspi.ko
>> [ 255.383671] omap2_mcspi omap2_mcspi.1: Unbalanced pm_runtime_enable!
>> ...
>>
>> This patch adds the pm_runtime disable() at appropriate stages.
>>
>> Signed-off-by: Hebbar, Gururaja<gururaja.hebbar@ti.com>
>> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
> Nitpick: please use the format "spi/<device>: ...." for the subject
> line of spi patches. It's just a consistency thing that I like.
Henceforth I will take care
> Picked up for v3.3, thanks.
>
> g.
>
>> ---
>> drivers/spi/spi-omap2-mcspi.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
>> index 471b0f3..6875a0b 100644
>> --- a/drivers/spi/spi-omap2-mcspi.c
>> +++ b/drivers/spi/spi-omap2-mcspi.c
>> @@ -1195,6 +1195,7 @@ static int __init omap2_mcspi_probe(struct platform_device *pdev)
>> err4:
>> spi_master_put(master);
>> err3:
>> + pm_runtime_disable(&pdev->dev);
>> kfree(mcspi->dma_channels);
>> err2:
>> release_mem_region(r->start, resource_size(r));
>> @@ -1216,6 +1217,7 @@ static int __exit omap2_mcspi_remove(struct platform_device *pdev)
>> dma_channels = mcspi->dma_channels;
>>
>> omap2_mcspi_disable_clocks(mcspi);
>> + pm_runtime_disable(&pdev->dev);
>> r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> release_mem_region(r->start, resource_size(r));
>>
>> --
>> 1.7.1
>>
>>
>> ------------------------------------------------------------------------------
>> The demand for IT networking professionals continues to grow, and the
>> demand for specialized networking skills is growing even more rapidly.
>> Take a complimentary Learning@Cisco Self-Assessment and learn
>> about Cisco certifications, training, and career opportunities.
>> http://p.sf.net/sfu/cisco-dev2dev
>> _______________________________________________
>> spi-devel-general mailing list
>> spi-devel-general@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/spi-devel-general
^ permalink raw reply
* Re: [PATCH 2/3] OMAP: SPI: call pm_runtime_disable in error path and remove
From: Shubhrajyoti @ 2011-10-31 5:16 UTC (permalink / raw)
To: Grant Likely
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f,
linux-kernel-u79uwXL29TY76Z2rM5mHXA, Hebbar, Gururaja
In-Reply-To: <20111029120655.GE22592-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On Saturday 29 October 2011 05:36 PM, Grant Likely wrote:
> On Fri, Oct 28, 2011 at 05:14:18PM +0530, Shubhrajyoti D wrote:
>> omap mcspi probe() doesnt call pm_runtime disable functions
>> in case of failure. remove() doesnt call pm_runtime disable. This could
>> lead to warnings as below on subsequent insmod.
>>
>> ~# insmod spi-omap2-mcspi.ko
>> [ 255.383671] omap2_mcspi omap2_mcspi.1: Unbalanced pm_runtime_enable!
>> ...
>>
>> This patch adds the pm_runtime disable() at appropriate stages.
>>
>> Signed-off-by: Hebbar, Gururaja<gururaja.hebbar-l0cyMroinI0@public.gmane.org>
>> Signed-off-by: Shubhrajyoti D<shubhrajyoti-l0cyMroinI0@public.gmane.org>
> Nitpick: please use the format "spi/<device>: ...." for the subject
> line of spi patches. It's just a consistency thing that I like.
Henceforth I will take care
> Picked up for v3.3, thanks.
>
> g.
>
>> ---
>> drivers/spi/spi-omap2-mcspi.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
>> index 471b0f3..6875a0b 100644
>> --- a/drivers/spi/spi-omap2-mcspi.c
>> +++ b/drivers/spi/spi-omap2-mcspi.c
>> @@ -1195,6 +1195,7 @@ static int __init omap2_mcspi_probe(struct platform_device *pdev)
>> err4:
>> spi_master_put(master);
>> err3:
>> + pm_runtime_disable(&pdev->dev);
>> kfree(mcspi->dma_channels);
>> err2:
>> release_mem_region(r->start, resource_size(r));
>> @@ -1216,6 +1217,7 @@ static int __exit omap2_mcspi_remove(struct platform_device *pdev)
>> dma_channels = mcspi->dma_channels;
>>
>> omap2_mcspi_disable_clocks(mcspi);
>> + pm_runtime_disable(&pdev->dev);
>> r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> release_mem_region(r->start, resource_size(r));
>>
>> --
>> 1.7.1
>>
>>
>> ------------------------------------------------------------------------------
>> The demand for IT networking professionals continues to grow, and the
>> demand for specialized networking skills is growing even more rapidly.
>> Take a complimentary Learning@Cisco Self-Assessment and learn
>> about Cisco certifications, training, and career opportunities.
>> http://p.sf.net/sfu/cisco-dev2dev
>> _______________________________________________
>> spi-devel-general mailing list
>> spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/spi-devel-general
------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook
in minutes. BlackBerry App World™ now supports Android™ Apps
for the BlackBerry® PlayBook™. Discover just how easy and simple
it is! http://p.sf.net/sfu/android-dev2dev
^ permalink raw reply
* Re: PROBLEM: Kernel panic and system crash during RAID disk failure
From: Darko @ 2011-10-31 5:13 UTC (permalink / raw)
To: Yongqiang Yang; +Cc: NeilBrown, Thomas Gleixner, linux-kernel, linux-ext4
In-Reply-To: <CAGBYx2bN7Gxm1PWJwm3Vf0-yikyo9H_xnCiGNetLVQagMRJbTQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 11816 bytes --]
Yongqiang,
I am unable to catch the dmesg, since the system locks up and I have to
mechanically reset it.
I have attached the same error with kernel version 2.6.37.6. Out of
approximately 10 times that happened yesterday, I was able to catch it
once...the system remained partially responsive that time.
Thanks,
Darko
On Mon, 31 Oct 2011, Yongqiang Yang wrote:
> Date: Mon, 31 Oct 2011 12:57:03 +0800
> From: Yongqiang Yang <xiaoqiangnk@gmail.com>
> To: Darko <darko@hytron.net>
> Cc: NeilBrown <neilb@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
> linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
> Subject: Re: PROBLEM: Kernel panic and system crash during RAID disk failure
>
> On Mon, Oct 31, 2011 at 12:51 PM, Darko <darko@hytron.net> wrote:
>> Hi Yongqiang,
>>
>> I am using kernel version 3.0.8. Looking through the file super.c, the file
>> already has the code mentioned on the web. I also noticed the date of the
>> post (http://lists.openwall.net/linux-ext4/2011/03/29/5) is back from March
>> of 2011. I think the bug I reported here was not fixed by that patch since
>> the kernel version I am using is much newer than March 2011.
> Could you post out the dmesg log printed by 3.0.8 or 3.1?
>
> Yongqiang.
>>
>> I am not sure if I understand what you mean by "commit 0449641130 ext4"?
>>
>> Thanks,
>>
>> Darko
>>
>>
>> On Mon, 31 Oct 2011, Yongqiang Yang wrote:
>>
>>> Date: Mon, 31 Oct 2011 12:25:18 +0800
>>> From: Yongqiang Yang <xiaoqiangnk@gmail.com>
>>> To: Darko <darko@hytron.net>
>>> Cc: NeilBrown <neilb@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
>>> linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
>>> Subject: Re: PROBLEM: Kernel panic and system crash during RAID disk
>>> failure
>>>
>>> Hi Darko,
>>>
>>> The bug has been fixed by commit 0449641130 ext4: Init timer earlier
>>> to avoid a kernel panic in __save_error_info.
>>> http://lists.openwall.net/linux-ext4/2011/03/29/5
>>>
>>>
>>> I suspect you mounted ext2/3 partition using ext4 module.
>>>
>>>
>>> Yongqiang.
>>>
>>> On Mon, Oct 31, 2011 at 11:13 AM, Darko <darko@hytron.net> wrote:
>>>>
>>>> Thank you for your reply!
>>>>
>>>> I wanted to add to this that I was able to replicate the problem with
>>>> ext3
>>>> and ext2 file systems as well. They both hard lock the system, and the
>>>> only
>>>> way to recovery is to push the reset button. I can see the trace error on
>>>> the screen, but I am unable to do anything with it, since it goes by so
>>>> fast
>>>> that the portion which says "kernel BUG" is invisible. I assume they both
>>>> have similar issues with the code in kernel/timer.c
>>>>
>>>> On the other hand, I tried using raiserfs 3.5 tonight, and I got
>>>> input/output error as expected. The system did not crash. Just another
>>>> proof
>>>> that a bug is laying somewhere in the ext2/3/4 file system.
>>>>
>>>> When someone comes up with a patch, I am willing to try it out and feed
>>>> you
>>>> back with the report.
>>>>
>>>> Hope this helps.
>>>>
>>>> Thank You,
>>>>
>>>> Darko Kraus
>>>>
>>>>
>>>> On Sun, 30 Oct 2011, NeilBrown wrote:
>>>>
>>>>> Date: Sun, 30 Oct 2011 19:05:48 +1100
>>>>> From: NeilBrown <neilb@suse.de>
>>>>> To: Darko <darko@hytron.net>
>>>>> Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org,
>>>>> linux-ext4@vger.kernel.org
>>>>> Subject: Re: PROBLEM: Kernel panic and system crash during RAID disk
>>>>> failure
>>>>>
>>>>> On Sun, 30 Oct 2011 03:27:28 -0400 (EDT) Darko <darko@hytron.net> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have been doing some testing with the md RAID driver and I think I
>>>>>> discovered a problem with it.
>>>>>> Everything was performed on a system with a single hard drive using
>>>>>> loop
>>>>>> devices as virtual raid devices.
>>>>>> So here is the setup:
>>>>>> /dev/sdc is my main drive that hold entire Linux OS and has one
>>>>>> partition.
>>>>>> in the /tmp I created 7 files, 100MB each and associated them with loop
>>>>>> devices:
>>>>>>
>>>>>> losetup -a
>>>>>> /dev/loop0: [0821]:294820 (/var/tmp/raid-0)
>>>>>> /dev/loop1: [0821]:294857 (/var/tmp/raid-1)
>>>>>> /dev/loop2: [0821]:300120 (/var/tmp/raid-2)
>>>>>> /dev/loop3: [0821]:301073 (/var/tmp/raid-3)
>>>>>> /dev/loop4: [0821]:301074 (/var/tmp/raid-4)
>>>>>> /dev/loop5: [0821]:301075 (/var/tmp/raid-5)
>>>>>> /dev/loop6: [0821]:301076 (/var/tmp/raid-6)
>>>>>>
>>>>>> The next step was, created an RAID6 array:
>>>>>> mdadm --create /dev/md10 --level=6 -raid-deviced=7 /dev/loop[0-6]
>>>>>>
>>>>>> Here is how it looks so far:
>>>>>>
>>>>>> cat /proc/mdstat
>>>>>> Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
>>>>>> md10 : active raid6 loop6[6] loop5[5] loop4[4] loop3[3] loop2[2]
>>>>>> loop1[1]
>>>>>> loop0[0]
>>>>>> 499200 blocks super 1.2 level 6, 512k chunk, algorithm 2 [7/7]
>>>>>> [UUUUUUU]
>>>>>>
>>>>>>
>>>>>> Then the filesystem...
>>>>>> mkfs.ext4 -b 4096 -i 4096 -m 0 /dev/md10
>>>>>>
>>>>>> Mounting the file system to a folder called 'A' right in the root of my
>>>>>> system:
>>>>>>
>>>>>> mount /dev/md10 /A
>>>>>>
>>>>>> Then I copied a few files on that file system. So far everything is
>>>>>> good.
>>>>>>
>>>>>> Then I purposly failed 2 drives:
>>>>>> mdadm --manage /dev/md10 --fail /dev/loop0
>>>>>> mdadm --manage /dev/md10 --fail /dev/loop1
>>>>>>
>>>>>> The array continues to run fine in degraded mode. I was wondering what
>>>>>> would happen if another drive fails. So while I was doing a write
>>>>>> operating right in that filesystem (/dev/md10) using:
>>>>>> dd if=/dev/zero of=testfile bs=1k count=360000 ...
>>>>>>
>>>>>> ...quickly switched to a different console and entered the command:
>>>>>> mdadm --manage /dev/md10 --fail /dev/loop2
>>>>>>
>>>>>> ...which made 3 failed drives and the array can no longer work...
>>>>>>
>>>>>> Well I would be happy to see just the array not working, but kernel
>>>>>> panic
>>>>>> in both versions 2.6.37.4 and 3.0.8 made me worry that it is serious
>>>>>> bug
>>>>>> and appears to be in older and newer kernels as well.
>>>>>> I repeated this several times, and mostly the machine gets locked up
>>>>>> with
>>>>>> kernel panic. But once I was able to get it not to lock up all the way,
>>>>>> and that is how I have dmesg output.
>>>>>>
>>>>>> The attached files include dmesg from the system startup until the bug
>>>>>> trace, and some additional information regarding my system that might
>>>>>> be
>>>>>> helpful.
>>>>>>
>>>>>> For any additional question, please feel free to contact me!
>>>>>>
>>>>>> I hope this info helps someone find and resolve the problem in the
>>>>>> code.
>>>>>>
>>>>>
>>>>> The important part of your kernel log message is:
>>>>>
>>>>>
>>>>> [ 1227.766202] ------------[ cut here ]------------
>>>>> [ 1227.766259] kernel BUG at kernel/timer.c:681!
>>>>> [ 1227.766311] invalid opcode: 0000 [#1] SMP
>>>>> [ 1227.766365] last sysfs file: /sys/devices/virtual/block/md10/dev
>>>>> [ 1227.766419] Modules linked in:
>>>>> [ 1227.766471]
>>>>> [ 1227.766520] Pid: 1507, comm: mount Not tainted 2.6.37.6-v5.0 #7
>>>>> MICRO-STAR INTERNATIONAL CO., LTD MS-7142/MS-7142
>>>>> [ 1227.766633] EIP: 0060:[<c104f960>] EFLAGS: 00010246 CPU: 0
>>>>> [ 1227.766690] EIP is at mod_timer+0x210/0x250
>>>>> [ 1227.766742] EAX: 00000000 EBX: f5494e1c ECX: 00000000 EDX: 00000000
>>>>> [ 1227.766796] ESI: 00000000 EDI: 05348416 EBP: f54a3c90 ESP: f54a3c74
>>>>> [ 1227.766851] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>>>>> [ 1227.766904] Process mount (pid: 1507, ti=f54a2000 task=f2068880
>>>>> task.ti=f54a2000)
>>>>> [ 1227.767002] Stack:
>>>>> [ 1227.767003] f2068880 f54b159c 00000010 00000000 f1f8e400 f4efc57c
>>>>> 0000128d f54a3ca8
>>>>> [ 1227.767003] c11cb7ba c17d4e52 f4efc400 00000124 00000000 f54a3cb4
>>>>> c11ce4e6 ecee6318
>>>>> [ 1227.767003] f54a3cdc c11cf7cc ecec7578 00000124 00000000 f4efc400
>>>>> f54a3cd4 00000124
>>>>> [ 1227.767003] Call Trace:
>>>>> [ 1227.767003] [<c11cb7ba>] ? __save_error_info.clone.61+0x7a/0xf0
>>>>> [ 1227.767003] [<c11ce4e6>] ? save_error_info+0x16/0x30
>>>>> [ 1227.767003] [<c11cf7cc>] ? ext4_error_inode+0x4c/0xf0
>>>>> [ 1227.767003] [<c11b57e1>] ? __ext4_get_inode_loc+0x201/0x410
>>>>> [ 1227.767003] [<c110b62a>] ? inode_init_always+0x1aa/0x1c0
>>>>> [ 1227.767003] [<c11b72f9>] ? ext4_iget+0x59/0x6f0
>>>>> [ 1227.767003] [<c11d2716>] ? ext4_fill_super+0x1ab6/0x2c70
>>>>> [ 1227.767003] [<c114896f>] ? disk_name+0xbf/0xd0
>>>>> [ 1227.767003] [<c10fa119>] ? mount_bdev+0x179/0x1c0
>>>>> [ 1227.767003] [<c11d0c60>] ? ext4_fill_super+0x0/0x2c70
>>>>> [ 1227.767003] [<c11ca17f>] ? ext4_mount+0x1f/0x30
>>>>> [ 1227.767003] [<c11d0c60>] ? ext4_fill_super+0x0/0x2c70
>>>>> [ 1227.767003] [<c10f9835>] ? vfs_kern_mount+0x75/0x250
>>>>> [ 1227.767003] [<c110df03>] ? get_fs_type+0x33/0xb0
>>>>> [ 1227.767003] [<c11ca160>] ? ext4_mount+0x0/0x30
>>>>> [ 1227.767003] [<c10f9a6e>] ? do_kern_mount+0x3e/0xe0
>>>>> [ 1227.767003] [<c111080f>] ? do_mount+0x35f/0x6b0
>>>>> [ 1227.767003] [<c10d47c9>] ? strndup_user+0x49/0x70
>>>>> [ 1227.767003] [<c1110e0b>] ? sys_mount+0x6b/0xa0
>>>>> [ 1227.767003] [<c17b550c>] ? syscall_call+0x7/0xb
>>>>> [ 1227.767003] Code: fe ff ff 8b 0e 89 4d e4 8b 46 04 83 c6 08 89 f9 89
>>>>> da
>>>>> ff 55 e4 8b 06 85 c0 89 45 e4 75 ea e9 aa fe ff ff 8b 75 ec e9 ee fe ff
>>>>> ff
>>>>> <0f> 0b 8b 55 04 89 d8 e8 34 f9 ff ff e9 2a fe ff ff 8b 35 30 b8
>>>>> [ 1227.767003] EIP: [<c104f960>] mod_timer+0x210/0x250 SS:ESP
>>>>> 0068:f54a3c74
>>>>> [ 1227.770073] ---[ end trace d7b3d7a67954d202 ]---
>>>>>
>>>>>
>>>>> which happens after:
>>>>>
>>>>> [ 1137.167043] Aborting journal on device md10-8.
>>>>> [ 1137.167058] Buffer I/O error on device md10, logical block 139265
>>>>> [ 1137.167060] lost page write due to I/O error on md10
>>>>> [ 1137.167065] JBD2: I/O error detected when updating journal superblock
>>>>> for md10-8.
>>>>> [ 1137.660922] Buffer I/O error on device md10, logical block 1
>>>>> [ 1137.660926] lost page write due to I/O error on md10
>>>>> [ 1137.660932] EXT4-fs error (device md10): ext4_journal_start_sb:260:
>>>>> Detected aborted journal
>>>>> [ 1137.661046] EXT4-fs (md10): Remounting filesystem read-only
>>>>> [ 1137.661103] EXT4-fs (md10): previous I/O error to superblock detected
>>>>> [ 1137.661313] Buffer I/O error on device md10, logical block 1
>>>>> [ 1137.661315] lost page write due to I/O error on md10
>>>>> [ 1219.891363] EXT4-fs (md10): previous I/O error to superblock detected
>>>>> [ 1220.050654] Buffer I/O error on device md10, logical block 1
>>>>> [ 1220.050657] lost page write due to I/O error on md10
>>>>> [ 1220.050663] EXT4-fs error (device md10): ext4_put_super:728: Couldn't
>>>>> clean up the journal
>>>>>
>>>>> and some more "Buffer I/O error"s.
>>>>>
>>>>> So it looks like an ext4 issue.
>>>>>
>>>>> I have Cc:ed the appropriate list.
>>>>>
>>>>> Thanks for the report.
>>>>>
>>>>> NeilBrown
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Darko Kraus
>>>> Enterprise Network Administrator
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>> Please read the FAQ at http://www.tux.org/lkml/
>>>>
>>>
>>>
>>>
>>> --
>>> Best Wishes
>>> Yongqiang Yang
>>>
>>
>>
>> --
>> Darko Kraus
>> Enterprise Network Administrator
>
>
>
> --
> Best Wishes
> Yongqiang Yang
>
--
Darko Kraus
Enterprise Network Administrator
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 28728 bytes --]
^ permalink raw reply
* [U-Boot] [PATCH] davinci, mmc: fix gcc 4.6 build warnings
From: Heiko Schocher @ 2011-10-31 5:15 UTC (permalink / raw)
To: u-boot
Fix:
davinci_mmc.c: In function 'dmmc_wait_fifo_status':
davinci_mmc.c:72:7: warning: variable 'mmcstatus1' set but not used [-Wunused-but-set-variable]
davinci_mmc.c: In function 'dmmc_busy_wait':
davinci_mmc.c:89:7: warning: variable 'mmcstatus1' set but not used [-Wunused-but-set-variable]
Delete the unused variable.
Signed-off-by: Heiko Schocher <hs@denx.de>
Cc: Sandeep Paulraj <s-paulraj@ti.com>
Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
---
drivers/mmc/davinci_mmc.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/davinci_mmc.c b/drivers/mmc/davinci_mmc.c
index 5d918e6..ce96736 100644
--- a/drivers/mmc/davinci_mmc.c
+++ b/drivers/mmc/davinci_mmc.c
@@ -69,8 +69,8 @@ static void dmmc_set_clock(struct mmc *mmc, uint clock)
static int
dmmc_wait_fifo_status(volatile struct davinci_mmc_regs *regs, uint status)
{
- uint mmcstatus1, wdog = WATCHDOG_COUNT;
- mmcstatus1 = get_val(®s->mmcst1);
+ uint wdog = WATCHDOG_COUNT;
+
while (--wdog && ((get_val(®s->mmcst1) & status) != status))
udelay(10);
@@ -86,9 +86,8 @@ dmmc_wait_fifo_status(volatile struct davinci_mmc_regs *regs, uint status)
/* Busy bit wait loop for MMCST1 */
static int dmmc_busy_wait(volatile struct davinci_mmc_regs *regs)
{
- uint mmcstatus1, wdog = WATCHDOG_COUNT;
+ uint wdog = WATCHDOG_COUNT;
- mmcstatus1 = get_val(®s->mmcst1);
while (--wdog && (get_val(®s->mmcst1) & MMCST1_BUSY))
udelay(10);
--
1.7.6.4
^ permalink raw reply related
* [PATCH] libata-pmp: add schedule timeout to support some PMP cards
From: r66093 @ 2011-10-31 3:57 UTC (permalink / raw)
To: linux-ide; +Cc: Jerry Huang
From: Jerry Huang <r66093freescale.com>
With Freescale SATA controller, some PMP cards(e.g JMB393 PMP card)
can't work on some platforms (e.g mpc837x, p1022):
During PMP initialize, when reading the PMP SCR, we will observe the TIMEOUT
error because PMP card SCR is not ready.
Therefore, we need enough time to wait for the PMP card ready for SCR read:
1. read the SCR after 1ms sleep,
2. if failed, looping until read success or timeout (count = 0)
below is the error log:
fsl-sata e0018000.sata: Sata FSL Platform/CSB Driver init
scsi0 : sata_fsl
ata1: SATA max UDMA/133 irq 44
ata1: Signature Update detected @ 504 msecs
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.15: Port Multiplier 1.2, 0x197b:0x0325 r0, 15 ports, feat 0x5/0xf
ata2.00: hard resetting link
ata2.15: qc timeout (cmd 0xe4)
ata2.00: failed to read SCR 0 (Emask=0x4)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2: ATA_SRST issue failed
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: reset failed, giving up
ata2.15: hard resetting link
ata2: Hardreset failed, not off-lined 0
ata2: No Signature Update
ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: hard resetting link
ata2.15: qc timeout (cmd 0xe4)
ata2.00: failed to read SCR 0 (Emask=0x4)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2: ATA_SRST issue failed
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: reset failed, giving up
ata2.15: hard resetting link
ata2: Hardreset failed, not off-lined 0
ata2: No Signature Update
ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: hard resetting link
ata2.15: qc timeout (cmd 0xe4)
ata2.00: failed to read SCR 0 (Emask=0x4)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2: ATA_SRST issue failed
ata2.00: failed to read SCR 0 (Emask=0x40)
ata2.00: reset failed, giving up
ata2.00: failed to recover link after 3 tries, disabling
ata2.15: hard resetting link
ata2: Hardreset failed, not off-lined 0
ata2: No Signature Update
ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.15: qc timeout (cmd 0xe4)
ata2.00: failed to read SCR 0 (Emask=0x4)
ata2.00: failed to write SCR 1 (Emask=0x40)
ata2.00: failed to clear SError.N (errno=-5)
ata2.15: hard resetting link
ata2: Hardreset failed, not off-lined 0
ata2: No Signature Update
ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.01: hard resetting link
ata2.01: failed to resume link (SControl 0)
ata2.01: SATA link down (SStatus 0 SControl 0)
ata2.02: hard resetting link
ata2.02: failed to resume link (SControl 0)
ata2.02: SATA link down (SStatus 0 SControl 0)
......
ata2.14: hard resetting link
ata2.14: failed to resume link (SControl 0)
ata2.14: SATA link down (SStatus 0 SControl 0)
ata2: EH complete
Signed-off-by: Jerry Huang <r66093@freescale.com>
---
drivers/ata/libata-pmp.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/ata/libata-pmp.c b/drivers/ata/libata-pmp.c
index 224faab..18d5f8e 100644
--- a/drivers/ata/libata-pmp.c
+++ b/drivers/ata/libata-pmp.c
@@ -140,11 +140,19 @@ int sata_pmp_qc_defer_cmd_switch(struct ata_queued_cmd *qc)
int sata_pmp_scr_read(struct ata_link *link, int reg, u32 *r_val)
{
unsigned int err_mask;
+ int count = 20; /* try 20 times */
if (reg > SATA_PMP_PSCR_CONTROL)
return -EINVAL;
- err_mask = sata_pmp_read(link, reg, r_val);
+ do {
+ set_current_state(TASK_INTERRUPTIBLE);
+ schedule_timeout(1 * HZ / 1000); /* sleep 1 msecond */
+ set_current_state(TASK_RUNNING);
+
+ err_mask = sata_pmp_read(link, reg, r_val);
+ } while ((count--) && err_mask);
+
if (err_mask) {
ata_link_printk(link, KERN_WARNING, "failed to read SCR %d "
"(Emask=0x%x)\n", reg, err_mask);
--
1.7.4.1
^ permalink raw reply related
* Re: [lm-sensors] Something wrong with support for NCT6776F in
From: Guenter Roeck @ 2011-10-31 5:07 UTC (permalink / raw)
To: lm-sensors
In-Reply-To: <4EA9CECA.4050007@gmx.de>
On Mon, Oct 31, 2011 at 12:57:36AM -0400, Guenter Roeck wrote:
> Hi Soeren,
>
> sorry for the late reply. Busy ...
>
> On Thu, Oct 27, 2011 at 05:36:10PM -0400, Soeren D. Schulze wrote:
> > I have an ASRock H67M-ITX motherboard.
> >
> > The w83626ehf driver detects:
> >
> > [ 3904.608693] w83627ehf: Found NCT6776F chip at 0x290
> >
> > "sensors" shows me:
> >
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Physical id 0: +46.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 0: +46.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 1: +45.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 2: +46.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 3: +46.0°C (high = +80.0°C, crit = +98.0°C)
> >
> > nct6776-isa-0290
> > Adapter: ISA adapter
> > Vcore: +0.96 V (min = +0.00 V, max = +1.74 V)
> > in1: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM
> > AVCC: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
> > +3.3V: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
> > in4: +0.54 V (min = +0.00 V, max = +0.00 V) ALARM
> > in5: +1.69 V (min = +0.00 V, max = +0.00 V) ALARM
> > 3VSB: +3.41 V (min = +0.00 V, max = +0.00 V) ALARM
> > Vbat: +3.31 V (min = +0.00 V, max = +0.00 V) ALARM
> > fan1: 0 RPM (min = 0 RPM) ALARM
> > fan2: 2180 RPM (min = 0 RPM) ALARM
> > SYSTIN: +42.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor
> > = thermistor
> > CPUTIN: +127.5°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor
> > = thermistor
Followup: In my system, the CPU sensor type is reported to be a diode.
Wonder if that is relevant.
Guenter
> > AUXTIN: -24.0°C (high = +80.0°C, hyst = +75.0°C) sensor =
> > thermistor
> > PECI Agent 0: +46.5°C
> > cpu0_vid: +2.050 V
> > intrusion0: ALARM
> > intrusion1: ALARM
> >
> >
> > Here, CPUTIN and AUXTIN (whatever it is) are obviously wrong. CPUTIN
> > *decreases* towards 17°C when the CPU gets hot (non-linearly, though).
> >
> Odd. No idea what is going on, though. The registers are quite straightforward,
> and the same for NCT6775F and NCT6776F. And it works on my system with NCT6775F.
>
> > This was the first problem. The second problem occurs when I try to
> > control fan2 manually. The "pwm2" file in sysfs is 255 for anything
> > above 2000 RPM, but as you can see above, the fan can do more (I've been
> > at 2600 RPM -- maybe it can do even more), but pwm2 stays at 255.
> >
> Looking through the datasheet, I did not find anything obvious. It might
> be possible that the PWM output frequency (register 2 bank 0) somehow affects
> the fan speed as well. What causes the fan speed to go higher in your system ?
>
> Guenter
>
> >
> > I'm using the Debian Linux kernel 3.0.0-3, but the same problem occurs
> > when I pull the latest w83626ehf.c file from git.
> >
> >
> > Hope this was a tiny bit helpful. If I can help you finding the source
> > of this problem, please tell me.
> >
> > Sören
> >
> > _______________________________________________
> > lm-sensors mailing list
> > lm-sensors@lm-sensors.org
> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply
* Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
From: Brad Campbell @ 2011-10-31 5:04 UTC (permalink / raw)
To: NeilBrown; +Cc: linux RAID
In-Reply-To: <20111031130859.121d5620@notabene.brown>
On 31/10/11 10:08, NeilBrown wrote:
>
> Hi Linus et al,
>
> I just discovered a fairly serious flaw that I introduced into 3.1 - details
> below.
>
> Anyone running RAID10 with 3.1 is advised to either apply this patch or
> revert an earlier kernel as soon as possible. In the mean time, remove any
> hot spares from an RAID10 array.
>
G'day Neil,
Is that the issue I bumped up against here?
http://permalink.gmane.org/gmane.linux.raid/35805
^ permalink raw reply
* Re: [PATCH 06/36] m68k: modify user space access functions to support ColdFire CPUs
From: Greg Ungerer @ 2011-10-31 5:03 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux-m68k, uclinux-dev, Greg Ungerer
In-Reply-To: <CAMuHMdVRvncpVWNa+2EUybv3+v+3PzQ4R_7-sqV71pVqQ67qoQ@mail.gmail.com>
Hi Geert,
On 30/10/11 23:02, Geert Uytterhoeven wrote:
> On Tue, Oct 25, 2011 at 09:18,<gerg@snapgear.com> wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> Modify the user space access functions to support the ColdFire V4e cores
>> running with MMU enabled.
>>
>> The ColdFire processors do not support the "moves" instruction used by
>> the traditional 680x0 processors for moving data into and out of another
>> address space. They only support the notion of a single address space,
>> and you use the usual "move" instruction to access that.
>>
>> I am interrested in what others think if this approach. It is a little
>> ugly, but it does mean that the same code is used, not a complete
>> duplicate that is almost the same except for the "moves" instructions.
>> It does also mean in this form that it is an either/or compile. It
>> can't support both ColdFire and 680x0 in the same binary as it is.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
>> +#ifdef CONFIG_COLDFIRE
>> +/*
>> + * The ColdFire processors do not support the moves instruction used by
>> + * the traditional 680x0 processors for moving data into and out of
>> + * another address space. They only support the notion of a single address
>> + * space, and you use the usual move instruction to access that.
>> + *
>> + * All the user space access functions are otherwise the same on ColdFire
>> + * as the other 680x0 processors. So lets keep the code simple and just
>> + * define in what we need to use.
>> + */
>> +#define MOVES "move"
>> +#else
>> +#define MOVES "moves"
>> +#endif /* CONFIG_COLDFIRE */
>
> I did the same thing originally when trying to get uClinux running on
> MMU-less Amigas, so it's fine for me.
>
> If I'm not mistaken, this will also make it easier to merge uaccess.h again in
> the long run, as the version with "move" should work on all MMU-less
> platforms, right?
Yes, very good point. I hadn't even considered then when I was trying
to make this work. Another good reason to go with it :-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
^ permalink raw reply
* [ANNOUNCE] Git 1.7.8.rc0
From: Junio C Hamano @ 2011-10-31 5:00 UTC (permalink / raw)
To: git; +Cc: Linux Kernel
A release candidate Git 1.7.8.rc0 is available for testing.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
4c437ecb17ba7d1b69cecd06eae9543ad35be7a6 git-1.7.8.rc0.tar.gz
5fc490a7ab29bf020a8f46eecfdb421d970b6235 git-htmldocs-1.7.8.rc0.tar.gz
856259f71c10b21620caa27dbc74c3794f0c6854 git-manpages-1.7.8.rc0.tar.gz
Also the following public repositories all have a copy of the v1.7.8.rc0
tag and the master branch that the tag points at:
url = git://repo.or.cz/alt-git.git
url = https://code.google.com/p/git-core/
url = git://git.sourceforge.jp/gitroot/git-core/git.git
url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
url = https://github.com/gitster/git
There are a few topics that I would further merge down before -rc1 but
this should be pretty much it for the upcoming release, as far as "new
features" are concerned. Please test thoroughly to hunt for regressions.
Hopefully we can have something reasonable by late November before many in
the US will stop working and start stuffing themselves.
Git v1.7.8 Release Notes (draft)
================================
Updates since v1.7.7
--------------------
* Some git-svn, git-gui, git-p4 (in contrib) and msysgit updates.
* Updates to bash completion scripts.
* The build procedure has been taught to take advantage of computed
dependency automatically when the complier supports it.
* The date parser now accepts timezone designators that lack minutes
part and also has a colon between "hh:mm".
* The contents of the /etc/mailname file, if exists, is used as the
default value of the hostname part of the committer/author e-mail.
* "git am" learned how to read from patches generated by Hg.
* "git archive" talking with a remote repository can report errors
from the remote side in a more informative way.
* "git branch" learned an explicit --list option to ask for branches
listed, optionally with a glob matching pattern to limit its output.
* "git check-attr" learned "--cached" option to look at .gitattributes
files from the index, not from the working tree.
* Variants of "git cherry-pick" and "git revert" that take multiple
commits learned to "--continue".
* "git daemon" gives more human readble error messages to clients
using ERR packets when appropriate.
* Errors at the network layer is logged by "git daemon".
* "git diff" learned "--minimal" option to spend extra cycles to come
up with a minimal patch output.
* "git diff" learned "--function-context" option to show the whole
function as context that was affected by a change.
* "git difftool" can be told to skip launching the tool for a path by
answering 'n' to its prompt.
* "git fetch" learned to honor transfer.fsckobjects configuration to
validate the objects that were received from the other end, just like
"git receive-pack" (the receiving end of "git push") does.
* "git fetch" makes sure that the set of objects it received from the
other end actually completes the history before updating the refs.
"git receive-pack" (the receiving end of "git push") learned to do the
same.
* "git fetch" learned that fetching/cloning from a regular file on the
filesystem is not necessarily a request to unpack a bundle file; the
file could be ".git" with "gitdir: <path>" in it.
* "git for-each-ref" learned "%(contents:subject)", "%(contents:body)"
and "%(contents:signature)". The last one is useful for signed tags.
* "git grep" used to incorrectly pay attention to .gitignore files
scattered in the directory it was working in even when "--no-index"
option was used. It no longer does this. The "--exclude-standard"
option needs to be given to explicitly activate the ignore
mechanism.
* "git grep" learned "--untracked" option, where given patterns are
searched in untracked (but not ignored) files as well as tracked
files in the working tree, so that matches in new but not yet
added files do not get missed.
* The recursive merge backend no longer looks for meaningless
existing merges in submodules unless in the outermost merge.
* "git log" and friends learned "--children" option.
* "git ls-remote" learned to respond to "-h"(elp) requests.
* "git merge" learned the "--edit" option to allow users to edit the
merge commit log message.
* "git rebase -i" can be told to use special purpose editor suitable
only for its insn sheet via sequence.editor configuration variable.
* "git send-email" learned to respond to "-h"(elp) requests.
* "git send-email" allows the value given to sendemail.aliasfile to begin
with "~/" to refer to the $HOME directory.
* "git send-email" forces use of Authen::SASL::Perl to work around
issues between Authen::SASL::Cyrus and AUTH PLAIN/LOGIN.
* "git stash" learned "--include-untracked" option to stash away
untracked/ignored cruft from the working tree.
* "git submodule clone" does not leak an error message to the UI
level unnecessarily anymore.
* "git submodule update" learned to honor "none" as the value for
submodule.<name>.update to specify that the named submodule should
not be checked out by default.
* When populating a new submodule directory with "git submodule init",
the $GIT_DIR metainformation directory for submodules is created inside
$GIT_DIR/modules/<name>/ directory of the superproject and referenced
via the gitfile mechanism. This is to make it possible to switch
between commits in the superproject that has and does not have the
submodule in the tree without re-cloning.
* "mediawiki" remote helper can interact with (surprise!) MediaWiki
with "git fetch" & "git push".
* "gitweb" leaked unescaped control characters from syntax hiliter
outputs.
* "gitweb" can be told to give custom string at the end of the HTML
HEAD element.
* "gitweb" now has its own manual pages.
Also contains other documentation updates and minor code cleanups.
Fixes since v1.7.7
------------------
Unless otherwise noted, all fixes in the 1.7.7.X maintenance track are
included in this release.
* We used to drop error messages from libcurl on certain kinds of
errors.
(merge be22d92eac8 jn/maint-http-error-message later to maint).
* Error report from smart HTTP transport, when the connection was
broken in the middle of a transfer, showed a useless message on
a corrupt packet.
(merge 6cdf022 sp/smart-http-failure later to maint).
* HTTP transport did not use pushurl correctly, and also did not tell
what host it is trying to authenticate with when asking for
credentials.
(merge deba493 jk/http-auth later to maint).
* "git branch -m/-M" advertised to update RENAME_REF ref in the
commit log message that introduced the feature but not anywhere in
the documentation, and never did update such a ref anyway. This
undocumented misfeature that did not exist has been excised.
(merge b0eab01 jc/maint-remove-renamed-ref later to maint).
* Adding many refs to the local repository in one go (e.g. "git fetch"
that fetches many tags) and looking up a ref by name in a repository
with too many refs were unnecessarily slow.
(merge 17d68a54d jp/get-ref-dir-unsorted later to maint).
* "git fetch --prune" was unsafe when used with refspecs from the
command line.
(merge e8c1e6c cn/fetch-prune later to maint).
* Report from "git commit" on untracked files was confused under
core.ignorecase option.
(merge 2548183b jk/name-hash-dirent later to maint).
* The attribute mechanism did not use case insensitive match when
core.ignorecase was set.
(merge 6eba621 bc/attr-ignore-case later to maint).
* "git bisect" did not notice when it failed to update the working tree
to the next commit to be tested.
(merge 1acf11717 js/bisect-no-checkout later to maint).
* "git config --bool --get-regexp" failed to separate the variable name
and its value "true" when the variable is defined without "= true".
(merge 880e3cc mm/maint-config-explicit-bool-display later to maint).
* "git remote rename $a $b" were not careful to match the remote name
against $a (i.e. source side of the remote nickname).
(merge b52d00aed mz/remote-rename later to maint).
* "git diff --[num]stat" used to use the number of lines of context
different from the default, potentially giving different results from
"git diff | diffstat" and confusing the users.
(merge f01cae918 jc/maint-diffstat-numstat-context later to maint).
* "git merge" did not understand ":/<pattern>" as a way to name a commit.
* "git mergetool" learned to use its arguments as pathspec, not a path to
the file that may not even have any conflict.
(merge 6d9990a jm/mergetool-pathspec later to maint).
* "git pull" and "git rebase" did not work well even when GIT_WORK_TREE is
set correctly with GIT_DIR if the current directory is outside the working
tree.
(merge 035b5bf jk/pull-rebase-with-work-tree later to maint).
" "git push" on the receiving end used to call post-receive and post-update
hooks for attempted removal of non-existing refs.
(merge 160b81ed ph/push-to-delete-nothing later to maint).
* "git send-email" did not honor the configured hostname when restarting
the HELO/EHLO exchange after switching TLS on.
(merge 155b940 md/smtp-tls-hello-again later to maint).
* "gitweb" used to produce a non-working link while showing the contents
of a blob, when JavaScript actions are enabled.
(merge 2b07ff3ff ps/gitweb-js-with-lineno later to maint).
* The logic to filter out forked projects in the project list in
"gitweb" was broken for some time.
(merge 53c632f jm/maint-gitweb-filter-forks-fix later to maint).
----------------------------------------------------------------
Changes since v1.7.7 are as follows:
Bert Wesarg (7):
grep: do not use --index in the short usage output
grep --no-index: don't use git standard exclusions
git-gui: search and linenumber input are mutual exclusive in the blame view
git-gui: only accept numbers in the goto-line input
git-gui: clear the goto line input when hiding
git-gui: incremental goto line in blame view
grep: fix the error message that mentions --exclude
Brad King (3):
rev-list: Demonstrate breakage with --ancestry-path --all
submodule: Demonstrate known breakage during recursive merge
submodule: Search for merges only at end of recursive merge
Brandon Casey (13):
t/t3905: use the name 'actual' for test output, swap arguments to test_cmp
git-stash.sh: fix typo in error message
t/t3905: add missing '&&' linkage
git-stash: remove untracked/ignored directories when stashed
attr.c: avoid inappropriate access to strbuf "buf" member
cleanup: use internal memory allocation wrapper functions everywhere
builtin/mv.c: plug miniscule memory leak
refs.c: ensure struct whose member may be passed to realloc is initialized
refs.c: abort ref search if ref array is empty
refs.c: free duplicate entries in the ref array instead of leaking them
attr.c: respect core.ignorecase when matching attribute patterns
strbuf.c: remove unnecessary strbuf_grow() from strbuf_getwholeline()
t/t3000-ls-files-others.sh: use $SHELL_PATH to run git-new-workdir script
Carlos Martín Nieto (7):
Remove 'working copy' from the documentation and C code
fetch: free all the additional refspecs
t5510: add tests for fetch --prune
remote: separate out the remote_find_tracking logic into query_refspecs
fetch: honor the user-provided refspecs when pruning refs
fetch: treat --tags like refs/tags/*:refs/tags/* when pruning
Documentation: update [section.subsection] to reflect what git does
Chris Packham (1):
git-web--browse: avoid the use of eval
Christian Couder (1):
bisect: fix exiting when checkout failed in bisect_start()
Christoffer Pettersson (1):
git-gui: Corrected a typo in the Swedish translation of 'Continue'
Clemens Buchacher (5):
remove prefix argument from pathspec_prefix
rename pathspec_prefix() to common_prefix() and move to dir.[ch]
send-email: add option -h
use -h for synopsis and --help for manpage consistently
use test number as port number
Cord Seele (3):
Add Git::config_path()
use new Git::config_path() for aliasesfile
send-email: Fix %config_path_settings handling
Dan McGee (2):
tree-walk: drop unused parameter from match_dir_prefix
tree-walk: micro-optimization in tree_entry_interesting
David Aguilar (1):
Makefile: Improve compiler header dependency check
David Fries (2):
git-gui: Enable jumping to a specific line number in blame view.
git-gui: Add keyboard shortcuts for search and goto commands in blame view.
Dmitry Ivankov (3):
Fix typo: existant->existent
fast-import: don't allow to tag empty branch
fast-import: don't allow to note on empty branch
Drew Northup (1):
gitweb: Add gitweb.conf(5) manpage for gitweb configuration files
Erik Faye-Lund (2):
enter_repo: do not modify input
mingw: avoid using strbuf in syslog
Fredrik Gustafsson (2):
rev-parse: add option --resolve-git-dir <path>
Move git-dir for submodules
Fredrik Kuivinen (1):
Makefile: Use computed header dependencies if the compiler supports it
Frédéric Heitzmann (1):
git svn dcommit: new option --interactive.
Giuseppe Bilotta (1):
am: preliminary support for hg patches
Haitao Li (1):
date.c: Support iso8601 timezone formats
Heiko Voigt (4):
git-gui: warn when trying to commit on a detached head
submodule: move update configuration variable further up
add update 'none' flag to disable update of submodule by default
git-gui: deal with unknown files when pressing the "Stage Changed" button
Hui Wang (1):
sha1_file: normalize alt_odb path before comparing and storing
Ilari Liusvaara (1):
Support ERR in remote archive like in fetch/push
Jakub Narebski (6):
gitweb: Strip non-printable characters from syntax highlighter output
gitweb: Add gitweb(1) manpage for gitweb itself
Documentation: Link to gitweb(1) and gitweb.conf(5) in other manpages
Documentation: Add gitweb config variables to git-config(1)
gitweb: Add gitweb manpages to 'gitweb' package in git.spec
Add simple test for Git::config_path() in t/t9700-perl-git.sh
Jay Soffian (6):
Teach '--cached' option to check-attr
log --children
merge-one-file: fix "expr: non-numeric argument"
revert.c: defer writing CHERRY_PICK_HEAD till it is safe to do so
cherry-pick: do not give irrelevant advice when cherry-pick punted
Teach merge the '[-e|--edit]' option
Jeff King (30):
url: decode buffers that are not NUL-terminated
improve httpd auth tests
remote-curl: don't retry auth failures with dumb protocol
http: retry authentication failures for all http requests
t7004: factor out gpg setup
t6300: add more body-parsing tests
for-each-ref: refactor subject and body placeholder parsing
for-each-ref: handle multiline subjects like --pretty
fetch: avoid quadratic loop checking for updated submodules
t3200: clean up checks for file existence
add sha1_array API docs
quote.h: fix bogus comment
refactor argv_array into generic code
quote: provide sq_dequote_to_argv_array
bisect: use argv_array API
checkout: use argv_array API
run_hook: use argv_array API
filter-branch: use require_clean_work_tree
fix phantom untracked files when core.ignorecase is set
t1300: put git invocations inside test function
t1300: test mixed-case variable retrieval
pull,rebase: handle GIT_WORK_TREE better
pack-objects: protect against disappearing packs
downgrade "packfile cannot be accessed" errors to warnings
daemon: give friendlier error messages to clients
http_init: accept separate URL parameter
contrib: add diff highlight script
tests: add missing executable bits
contrib: add git-jump script
completion: match ctags symbol names in grep patterns
Jeremie Nikaes (1):
Add a remote helper to interact with mediawiki (fetch & push)
Jim Meyering (2):
fix "git apply --index ..." not to deref NULL
make the sample pre-commit hook script reject names with newlines, too
Johannes Schindelin (5):
Fix is_gitfile() for files too small or larger than PATH_MAX to be a gitfile
t1020: disable the pwd test on MinGW
t9001: do not fail only due to CR/LF issues
t9300: do not run --cat-blob-fd related tests on MinGW
git grep: be careful to use mutexes only when they are initialized
Johannes Sixt (2):
t1402-check-ref-format: skip tests of refs beginning with slash on Windows
t1300: attempting to remove a non-existent .git/config is not an error
Jonathan Nieder (7):
http: remove extra newline in error message
http: avoid empty error messages for some curl errors
ident: check /etc/mailname if email is unknown
Makefile: do not set setgid bit on directories on GNU/kFreeBSD
ident: do not retrieve default ident when unnecessary
Makefile: fix permissions of mergetools/ checked out with permissive umask
RelNotes/1.7.7.1: setgid bit patch is about fixing "git init" via Makefile setting
Jonathon Mah (1):
mergetool: Use args as pathspec to unmerged files
Julian Phillips (2):
Don't sort ref_list too early
refs: Use binary search to lookup refs faster
Julien Muchembled (1):
gitweb: fix regression when filtering out forks
Junio C Hamano (66):
rev-list: fix finish_object() call
revision.c: add show_object_with_name() helper function
revision.c: update show_object_with_name() without using malloc()
revision: keep track of the end-user input from the command line
revision: do not include sibling history in --ancestry-path output
rebase -i: notice and warn if "exec $cmd" modifies the index or the working tree
traverse_trees(): allow pruning with pathspec
unpack-trees: allow pruning with pathspec
diff-index: pass pathspec down to unpack-trees machinery
list-objects: pass callback data to show_objects()
rev-list --verify-object
fetch: verify we have everything we need before updating our ref
fetch.fsckobjects: verify downloaded objects
transfer.fsckobjects: unify fetch/receive.fsckobjects
test: fetch/receive with fsckobjects
consolidate pathspec_prefix and common_prefix
fetch: verify we have everything we need before updating our ref
check_everything_connected(): refactor to use an iterator
check_everything_connected(): libify
receive-pack: check connectivity before concluding "git push"
builtin/revert.c: make commit_list_append() static
refs.c: make create_cached_refs() static
fsck: do not abort upon finding an empty blob
send-pack: typofix error message
refactor run_receive_hook()
rename "match_refs()" to "match_push_refs()"
Allow git merge ":/<pattern>"
ls-remote: a lone "-h" is asking for help
Teach progress eye-candy to fetch_refs_from_bundle()
diff: teach --stat/--numstat to honor -U$num
t0003: remove extra whitespaces
mergetool: no longer need to save standard input
apply --whitespace=error: correctly report new blank lines at end
parse-options: deprecate OPT_BOOLEAN
archive.c: use OPT_BOOL()
checkout $tree $path: do not clobber local changes in $path not in $tree
url.c: simplify is_url()
diff: resurrect XDF_NEED_MINIMAL with --minimal
grep: teach --untracked and --exclude-standard options
Post 1.7.7 first wave
attr: read core.attributesfile from git_default_core_config
Update draft release notes to 1.7.8
branch -m/-M: remove undocumented RENAMED-REF
refs.c: move dwim_ref()/dwim_log() from sha1_name.c
Update draft release notes to 1.7.8
bundle: allowing to read from an unseekable fd
bundle: add parse_bundle_header() helper function
Update draft release notes to 1.7.8
t7800: avoid arithmetic expansion notation
Prepare for 1.7.7.1
Update draft release notes to 1.7.8
resolve_gitlink_packed_ref(): fix mismerge
Update draft release notes to 1.7.8
Makefile: ask "ls-files" to list source files if available
libperl-git: refactor Git::config_*
Update draft release notes to 1.7.8
resolve_ref(): expose REF_ISBROKEN flag
resolve_ref(): report breakage to the caller without warning
Almost ready for 1.7.7.1
Update draft release notes to 1.7.8
Git 1.7.7.1
builtin/grep: make lock/unlock into static inline functions
builtin/grep: simplify lock_and_read_sha1_file()
Update draft release notes to 1.7.8
Update draft release notes to 1.7.8
Git 1.7.8-rc0
Luke Diamand (1):
git-p4: handle files with shell metacharacters
Lénaïc Huard (1):
gitweb: provide a way to customize html headers
Martin von Zweigbergk (4):
remote: write correct fetch spec when renaming remote 'remote'
remote: "rename o foo" should not rename ref "origin/bar"
remote rename: warn when refspec was not updated
remote: only update remote-tracking branch if updating refspec
Matthew Daley (1):
send-email: Honour SMTP domain when using TLS
Matthieu Moy (8):
rebase -i: clean error message for --continue after failed exec
git-remote-mediawiki: allow push to set MediaWiki metadata
git-remote-mediawiki: trivial fixes
git-remote-mediawiki: set 'basetimestamp' to let the wiki handle conflicts
git-remote-mediawiki: obey advice.pushNonFastForward
git-remote-mediawiki: allow a domain to be set for authentication
config: display key_delim for config --bool --get-regexp
git-remote-mediawiki: don't include HTTP login/password in author
Michael Haggerty (37):
Extract a function clear_cached_refs()
Access reference caches only through new function get_cached_refs()
Change the signature of read_packed_refs()
Allocate cached_refs objects dynamically
Store the submodule name in struct cached_refs
Retain caches of submodule refs
notes_merge_commit(): do not pass temporary buffer to other function
get_sha1_hex(): do not read past a NUL character
t1402: add some more tests
git check-ref-format: add options --allow-onelevel and --refspec-pattern
Change bad_ref_char() to return a boolean value
Change check_ref_format() to take a flags argument
Refactor check_refname_format()
Do not allow ".lock" at the end of any refname component
Make collapse_slashes() allocate memory for its result
Inline function refname_format_print()
Change check_refname_format() to reject unnormalized refnames
resolve_ref(): explicitly fail if a symlink is not readable
resolve_ref(): use prefixcmp()
resolve_ref(): only follow a symlink that contains a valid, normalized refname
resolve_ref(): turn buffer into a proper string as soon as possible
resolve_ref(): extract a function get_packed_ref()
resolve_ref(): do not follow incorrectly-formatted symbolic refs
remote: use xstrdup() instead of strdup()
remote: avoid passing NULL to read_ref()
resolve_ref(): verify that the input refname has the right format
resolve_ref(): emit warnings for improperly-formatted references
resolve_ref(): also treat a too-long SHA1 as invalid
resolve_ref(): expand documentation
add_ref(): verify that the refname is formatted correctly
invalidate_ref_cache(): rename function from invalidate_cached_refs()
invalidate_ref_cache(): take the submodule as parameter
invalidate_ref_cache(): expose this function in the refs API
clear_ref_cache(): rename parameter
clear_ref_cache(): extract two new functions
write_ref_sha1(): only invalidate the loose ref cache
clear_ref_cache(): inline function
Michael J Gruber (10):
t6040: test branch -vv
git-tag: introduce long forms for the options
git-branch: introduce missing long forms for the options
branch: introduce --list option
branch: allow pattern arguments
branch: -v does not automatically imply --list
unpack-trees: print "Aborting" to stderr
git-read-tree.txt: language and typography fixes
git-read-tree.txt: correct sparse-checkout and skip-worktree description
http: use hostname in credential description
Michael Schubert (1):
patch-id.c: use strbuf instead of a fixed buffer
Michael W. Olson (1):
git-svn: Allow certain refs to be ignored
Michał Górny (1):
for-each-ref: add split message parts to %(contents:*).
Nguyễn Thái Ngọc Duy (12):
merge: keep stash[] a local variable
merge: use return value of resolve_ref() to determine if HEAD is invalid
merge: remove global variable head[]
Accept tags in HEAD or MERGE_HEAD
sparse checkout: show error messages when worktree shaping fails
Add explanation why we do not allow to sparse checkout to empty working tree
git-read-tree.txt: update sparse checkout examples
pack-protocol: document "ERR" line
daemon: return "access denied" if a service is not allowed
daemon: log errors if we could not use some sockets
t5403: convert leading spaces to tabs
Reindent closing bracket using tab instead of spaces
Nicolas Morey-Chaisemartin (1):
grep: Fix race condition in delta_base_cache
Pang Yan Han (1):
receive-pack: don't pass non-existent refs to post-{receive,update} hooks
Pat Thoyts (6):
git-gui: updated translator README for current procedures.
Fix tooltip display with multiple monitors on windows.
git-gui: drop the 'n' and 'Shift-n' bindings from the last patch.
mergetools: use the correct tool for Beyond Compare 3 on Windows
mingw: ensure sockets are initialized before calling gethostname
t9901: fix line-ending dependency on windows
Pete Wyckoff (5):
git-p4 tests: refactor and cleanup
git-p4: handle utf16 filetype properly
git-p4: recognize all p4 filetypes
git-p4: stop ignoring apple filetype
git-p4: keyword flattening fixes
Peter Oberndorfer (1):
"rebase -i": support special-purpose editor to edit insn sheet
Peter Stuge (1):
gitweb: Fix links to lines in blobs when javascript-actions are enabled
Phil Hord (3):
Learn to handle gitfiles in enter_repo
Teach transport about the gitfile mechanism
Add test showing git-fetch groks gitfiles
Ramkumar Ramachandra (18):
advice: Introduce error_resolve_conflict
config: Introduce functions to write non-standard file
revert: Simplify and inline add_message_to_msg
revert: Don't check lone argument in get_encoding
revert: Rename no_replay to record_origin
revert: Eliminate global "commit" variable
revert: Introduce struct to keep command-line options
revert: Separate cmdline parsing from functional code
revert: Don't create invalid replay_opts in parse_args
revert: Save data for continuing after conflict resolution
revert: Save command-line options for continuing operation
revert: Make pick_commits functionally act on a commit list
revert: Introduce --reset to remove sequencer state
reset: Make reset remove the sequencer state
revert: Remove sequencer state when no commits are pending
revert: Don't implicitly stomp pending sequencer operation
revert: Introduce --continue to continue the operation
revert: Propagate errors upwards from do_pick_commit
Ramsay Allan Jones (6):
Makefile: Make dependency directory creation less noisy
sparse: Fix an "Using plain integer as NULL pointer" warning
obstack.c: Fix some sparse warnings
t9159-*.sh: skip for mergeinfo test for svn <= 1.4
Fix some "variable might be used uninitialized" warnings
gitweb/Makefile: Remove static/gitweb.js in the clean target
René Scharfe (26):
Revert removal of multi-match discard heuristic in 27af01
parseopt: add OPT_NOOP_NOARG
revert: use OPT_NOOP_NOARG
apply: use OPT_NOOP_NOARG
checkout: check for "Previous HEAD" notice in t2020
revision: factor out add_pending_sha1
checkout: use add_pending_{object,sha1} in orphan check
revision: add leak_pending flag
bisect: use leak_pending flag
bundle: use leak_pending flag
checkout: use leak_pending flag
commit: factor out clear_commit_marks_for_object_array
test-ctype: macrofy
test-ctype: add test for is_pathspec_magic
name-rev: split usage string
pickaxe: plug diff filespec leak with empty needle
pickaxe: plug regex leak
pickaxe: plug regex/kws leak
pickaxe: factor out has_changes
pickaxe: pass diff_options to contains and has_changes
pickaxe: give diff_grep the same signature as has_changes
pickaxe: factor out pickaxe
xdiff: factor out get_func_line()
diff: add option to show whole functions as context
t1304: fall back to $USER if $LOGNAME is not defined
read-cache.c: fix index memory allocation
Richard Hartmann (1):
clone: Quote user supplied path in a single quote pair
SZEDER Gábor (2):
completion: unite --reuse-message and --reedit-message for 'notes'
completion: unite --format and --pretty for 'log' and 'show'
Sebastian Schuberth (2):
git-svn: On MSYS, escape and quote SVN_SSH also if set by the user
inet_ntop.c: Work around GCC 4.6's detection of uninitialized variables
Shawn O. Pearce (1):
remote-curl: Fix warning after HTTP failure
Sitaram Chamarty (1):
git-difftool: allow skipping file by typing 'n' at prompt
Stefan Naewe (2):
Documentation/git-update-index: refer to 'ls-files'
completion: fix issue with process substitution not working on Git for Windows
Tay Ray Chuan (3):
fetch: plug two leaks on error exit in store_updated_refs
submodule: whitespace fix
submodule::module_clone(): silence die() message from module_name()
Teemu Matilainen (3):
completion: unite --reuse-message and --reedit-message handling
completion: commit --fixup and --squash
completion: push --set-upstream
Thomas Rast (3):
Symlink mergetools scriptlets into valgrind wrappers
Documentation: basic configuration of notes.rewriteRef
t6019: avoid refname collision on case-insensitive systems
Zbigniew Jędrzejewski-Szmek (1):
send-email: auth plain/login fix
^ permalink raw reply
* :configure: error: cannot find install-sh, install.sh, or shtool in ./build-scripts
From: sonu vishwakarma @ 2011-10-31 4:59 UTC (permalink / raw)
To: poky
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
Hi,
I'm trying the build for XBMC 10.10 which depends on libsdl-mixer. I'm
attaching the recipe of libsdl-mixer
and the error log. I'm getting the error as below :
| configure: loading site script /home/meta/site/endian-little
| configure: loading site script /home/meta/site/common-glibc
| configure: loading site script /home/meta/site/ix86-common
| configure: loading site script /home/meta/site/common
| configure: loading site script
/home/build/tmp/sysroots/fishriver/usr/share/i586-poky-linux_config_site.d/zlib_config
| configure: loading site script
/home/build/tmp/sysroots/fishriver/usr/share/i586-poky-linux_config_site.d/eglibc_config
| configure: error: cannot find install-sh, install.sh, or shtool in
./build-scripts
| FATAL: oe_runconf failed
| ERROR: Function 'do_configure' failed (see
/home/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/temp/log.do_configure.5111
for further information)
NOTE: package libsdl-mixer-1.2.11-r0: task do_configure: Failed
I'm pulling for the Fishriver machine . My host machine is Ubuntu 10.10 ,64
bit .
Can someone help me out of this problem ?
Thanks & Regards,
Sonu.
[-- Attachment #1.2: Type: text/html, Size: 2763 bytes --]
[-- Attachment #2: libsdl-mixer_1.2.11.bb --]
[-- Type: application/octet-stream, Size: 1290 bytes --]
DESCRIPTION = "Simple DirectMedia Layer mixer library."
SECTION = "libs"
DEPENDS = "virtual/libsdl flac libmikmod libvorbis ${@base_conditional('ENTERPRISE_DISTRO', '1', '', 'libmad', d)}"
LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM = "file://COPYING;md5=27818cd7fd83877a8e3ef82b82798ef4"
SRC_URI = "http://www.libsdl.org/projects/SDL_mixer/release/SDL_mixer-${PV}.tar.gz \
file://fix-flac-madness.diff \
file://configure.patch \
"
SRC_URI[md5sum] = "65ada3d997fe85109191a5fb083f248c"
SRC_URI[sha256sum] = "86145ac39cac6d2c6169c226f937648dca5e89dcd828751763dd174fa9af9cf9"
S = "${WORKDIR}/SDL_mixer-${PV}"
inherit autotools
EXTRA_AUTORECONF += "--include=acinclude"
EXTRA_OECONF = "--disable-music-mp3 --enable-music-ogg --enable-music-ogg-tremor ${@base_conditional('ENTERPRISE_DISTRO', '1', '', '--enable-music-mp3-mad-gpl', d)} LIBS=-L${STAGING_LIBDIR}"
do_configure () {
# Remove old libtool macros.
MACROS="libtool.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4"
for i in ${MACROS}; do
rm -f acinclude/$i
done
cp build-scripts/* . || true
rm -rf build-scripts/
export SYSROOT=$PKG_CONFIG_SYSROOT_DIR
autotools_do_configure
rm config.log
for i in $(find -name "Makefile") ; do
sed -i -e 's:-L/usr/lib:-L${STAGING_LIBDIR}:g' $i
done
}
[-- Attachment #3: log .do_configure.2254 --]
[-- Type: application/octet-stream, Size: 5406 bytes --]
NOTE: package libsdl-mixer-1.2.11-r0: task do_configure: Started
ERROR: '/home/poky/meta/libsdl/libsdl-mixer_1.2.11.bb' failed
ERROR: Function 'do_configure' failed (see /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/temp/log.do_configure.2254 for further information)
ERROR: Logfile of failure stored in: /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/temp/log.do_configure.2254
Log data follows:
| cp: cannot stat `build-scripts/*': No such file or directory
| automake (GNU automake) 1.11.1
| Copyright (C) 2009 Free Software Foundation, Inc.
| License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
| This is free software: you are free to change and redistribute it.
| There is NO WARRANTY, to the extent permitted by law.
|
| Written by Tom Tromey <tromey@redhat.com>
| and Alexandre Duret-Lutz <adl@gnu.org>.
| AUTOV is 1.11
| NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint --include=acinclude -I /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/SDL_mixer-1.2.11/acinclude/ -I/home/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.11 -I /home/poky/build/tmp/sysroots/fishriver/usr/share/aclocal
| autoreconf: Entering directory `.'
| autoreconf: configure.in: not using Gettext
| autoreconf: running: aclocal -I acinclude -I /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/SDL_mixer-1.2.11/acinclude/ -I /home/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.11 -I /home/poky/build/tmp/sysroots/fishriver/usr/share/aclocal -I acinclude -I /home/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/SDL_mixer-1.2.11/acinclude/ -I /home/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.11 -I /home/poky/build/tmp/sysroots/fishriver/usr/share/aclocal --force
| autoreconf: configure.in: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in `.'.
| libtoolize: copying file `./ltmain.sh'
| libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
| libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
| libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
| autoreconf: running: /home/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf --include=acinclude --include=/home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/SDL_mixer-1.2.11/acinclude/ --include=/home/poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.11 --include=/home/poky/build/tmp/sysroots/fishriver/usr/share/aclocal --force --warnings=cross
| autoreconf: configure.in: not using Autoheader
| autoreconf: configure.in: not using Automake
| autoreconf: running: gnu-configize
| Perl lib version (5.12.2) doesn't match executable version (v5.10.1) at /home/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.12.2/Config.pm line 50.
| Compilation failed in require at /home/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.12.2/File/Copy.pm line 14.
| BEGIN failed--compilation aborted at /home/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.12.2/File/Copy.pm line 14.
| Compilation failed in require at /home/poky/build/tmp/sysroots/x86_64-linux/usr/share/autoconf/Autom4te/FileUtils.pm line 166.
| BEGIN failed--compilation aborted at /home/poky/build/tmp/sysroots/x86_64-linux/usr/share/autoconf/Autom4te/FileUtils.pm line 166.
| Compilation failed in require at /home/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autom4te line 41.
| BEGIN failed--compilation aborted at /home/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autom4te line 41.
| autoreconf: Leaving directory `.'
| NOTE: Running /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/SDL_mixer-1.2.11/configure --build=x86_64-linux --host=i586-poky-linux --target=i586-poky-linux --prefix=/usr --exec_prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec --datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib --includedir=/usr/include --oldincludedir=/usr/include --infodir=/usr/share/info --mandir=/usr/share/man --with-libtool-sysroot=/home/poky/build/tmp/sysroots/fishriver --disable-music-mp3 --enable-music-ogg --enable-music-ogg-tremor --enable-music-mp3-mad-gpl LIBS=-L/home/sct/logi/gigabyte/poky_gigabyte_16Sep2011/build/tmp/sysroots/fishriver/usr/lib ...
| configure: loading site script /home/poky/meta/site/endian-little
| configure: loading site script /home/poky/meta/site/common-glibc
| configure: loading site script /home/poky/meta/site/ix86-common
| configure: loading site script /home/poky/meta/site/common
| configure: loading site script /home/poky/build/tmp/sysroots/fishriver/usr/share/i586-poky-linux_config_site.d/zlib_config
| configure: loading site script /home/poky/build/tmp/sysroots/fishriver/usr/share/i586-poky-linux_config_site.d/eglibc_config
| configure: error: cannot find install-sh, install.sh, or shtool in ./build-scripts
| FATAL: oe_runconf failed
| ERROR: Function 'do_configure' failed (see /home/poky/build/tmp/work/atom-poky-linux/libsdl-mixer-1.2.11-r0/temp/log.do_configure.2254 for further information)
NOTE: package libsdl-mixer-1.2.11-r0: task do_configure: Failed
ERROR: Task 1052 (/home/poky/meta/recipes/libsdl/libsdl-mixer_1.2.11.bb, do_configure) failed with exit code '1'
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
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.