On Wed, 09 Apr, at 08:01:02PM, Thomas Bächler wrote:
>
> Hello again Matt,
>
> that patch seems to help. Thank you so much.
>
> (I am going to apply this patch and backport dc53324060, too, so
> everything should be in order then.)
That's great to hear, thanks for testing. I'll get this applied
Am 09.04.2014 10:30, schrieb Thomas Bächler:
> Am 09.04.2014 10:25, schrieb Matt Fleming:
>> On Tue, 08 Apr, at 10:04:48PM, Thomas Bächler wrote:
>>>
>>> Hello again Matt,
>>>
>>> with linux.git master, I cannot reproduce the problem at all (with or
>>> without your patch). In fact, all the 0x0 CRC
Am 09.04.2014 10:25, schrieb Matt Fleming:
> On Tue, 08 Apr, at 10:04:48PM, Thomas Bächler wrote:
>>
>> Hello again Matt,
>>
>> with linux.git master, I cannot reproduce the problem at all (with or
>> without your patch). In fact, all the 0x0 CRCs on symbols are gone, and
>> those were the symbols
On Tue, 08 Apr, at 10:04:48PM, Thomas Bächler wrote:
>
> Hello again Matt,
>
> with linux.git master, I cannot reproduce the problem at all (with or
> without your patch). In fact, all the 0x0 CRCs on symbols are gone, and
> those were the symbols that were broken after all.
>
> FWIW, with your
Am 08.04.2014 20:57, schrieb Thomas Bächler:
Thomas, you mention you're running in a 32-bit vm earlier in this
thread. Any chance you're using ovmf because that would make it much
easier to track this down?
>>>
>>> I'm not familiar with UEFI boot, but it could happen because wha
Am 08.04.2014 14:14, schrieb Matt Fleming:
> On Tue, 08 Apr, at 06:46:49AM, Tetsuo Handa wrote:
>> Fleming, Matt wrote:
>>> On 7 April 2014 21:42, Andi Kleen wrote:
This sounds like the UEFI boot corrupts some memory?
>>>
>>> Hmpf, yeah. I'll take a look in the morning.
>>>
>>> Thomas, y
On Tue, 08 Apr, at 06:46:49AM, Tetsuo Handa wrote:
> Fleming, Matt wrote:
> > On 7 April 2014 21:42, Andi Kleen wrote:
> > >
> > > This sounds like the UEFI boot corrupts some memory?
> >
> > Hmpf, yeah. I'll take a look in the morning.
> >
> > Thomas, you mention you're running in a 32-bit vm e
On Mon, Apr 07, 2014 at 10:10:46PM +0200, Thomas Bächler wrote:
> Am 07.04.2014 19:46, schrieb Thomas Bächler:
> > Am 07.04.2014 19:30, schrieb Andi Kleen:
> Do you have a specific config?
> Specific compiler version?
> >>>
> >>> Using gcc 4.8 from Arch Linux with the configuration at [1]
Fleming, Matt wrote:
> On 7 April 2014 21:42, Andi Kleen wrote:
> >
> > This sounds like the UEFI boot corrupts some memory?
>
> Hmpf, yeah. I'll take a look in the morning.
>
> Thomas, you mention you're running in a 32-bit vm earlier in this
> thread. Any chance you're using ovmf because that
Am 07.04.2014 23:25, schrieb Fleming, Matt:
> On 7 April 2014 21:42, Andi Kleen wrote:
>>
>> This sounds like the UEFI boot corrupts some memory?
>
> Hmpf, yeah. I'll take a look in the morning.
>
> Thomas, you mention you're running in a 32-bit vm earlier in this
> thread. Any chance you're usi
On 7 April 2014 21:42, Andi Kleen wrote:
>
> This sounds like the UEFI boot corrupts some memory?
Hmpf, yeah. I'll take a look in the morning.
Thomas, you mention you're running in a 32-bit vm earlier in this
thread. Any chance you're using ovmf because that would make it much
easier to track th
Am 07.04.2014 19:46, schrieb Thomas Bächler:
> Am 07.04.2014 19:30, schrieb Andi Kleen:
Do you have a specific config?
Specific compiler version?
>>>
>>> Using gcc 4.8 from Arch Linux with the configuration at [1] and Linux 3.14.
>>
>> I tested this configuration (with gcc 4.8 on FC20/19)
Am 07.04.2014 19:30, schrieb Andi Kleen:
>>> Do you have a specific config?
>>> Specific compiler version?
>>
>> Using gcc 4.8 from Arch Linux with the configuration at [1] and Linux 3.14.
>
> I tested this configuration (with gcc 4.8 on FC20/19) and it loads
> ext4 and all the other modules witho
On Sat, Apr 05, 2014 at 04:29:31PM +0200, Thomas Bächler wrote:
> Am 05.04.2014 03:13, schrieb Andi Kleen:
> > On Tue, Apr 01, 2014 at 01:38:10AM +0200, Thomas Bächler wrote:
> >> Am 01.04.2014 01:34, schrieb Andi Kleen:
> This problem persists in v3.14, i.e. I still have to revert
> 8346
Am 05.04.2014 19:23, schrieb Tetsuo Handa:
> Thomas B臘hler wrote:
For convenience, here is a copy-and-paste of the full text:
>>>
>>> I did some experiments know and I can't find any 32bit modules
>>> that do not load with 32bit MODVERSIONS on or off with
>>> a current tree.
>>>
>>> Do you h
Thomas B臘hler wrote:
> >> For convenience, here is a copy-and-paste of the full text:
> >
> > I did some experiments know and I can't find any 32bit modules
> > that do not load with 32bit MODVERSIONS on or off with
> > a current tree.
> >
> > Do you have a specific config?
> > Specific compile
Am 05.04.2014 03:13, schrieb Andi Kleen:
> On Tue, Apr 01, 2014 at 01:38:10AM +0200, Thomas Bächler wrote:
>> Am 01.04.2014 01:34, schrieb Andi Kleen:
This problem persists in v3.14, i.e. I still have to revert
83460ec8dcac14142e7860a01fa59c267ac4657c in order to get a working
kernel
On Tue, Apr 01, 2014 at 01:38:10AM +0200, Thomas Bächler wrote:
> Am 01.04.2014 01:34, schrieb Andi Kleen:
> >> This problem persists in v3.14, i.e. I still have to revert
> >> 83460ec8dcac14142e7860a01fa59c267ac4657c in order to get a working
> >> kernel on i686. I would really appreciate if someo
Am 01.04.2014 01:34, schrieb Andi Kleen:
>> This problem persists in v3.14, i.e. I still have to revert
>> 83460ec8dcac14142e7860a01fa59c267ac4657c in order to get a working
>> kernel on i686. I would really appreciate if someone would actually read
>> my original mail from about 3 months ago and w
On Tue, Apr 01, 2014 at 01:16:09AM +0200, Thomas Bächler wrote:
> Am 26.01.2014 10:01, schrieb Thomas Bächler:
> > Good morning,
> >
> > I am trying to build Linux 3.13 on i686 with CONFIG_MODVERSIONS enabled
> > (for configuration, see [2]). Upon booting it in a VM, I discovered that
> > I was un
Am 26.01.2014 10:01, schrieb Thomas Bächler:
> Good morning,
>
> I am trying to build Linux 3.13 on i686 with CONFIG_MODVERSIONS enabled
> (for configuration, see [2]). Upon booting it in a VM, I discovered that
> I was unable to load several kernel modules, like ext4:
>
> ext4: disagrees about v
Am 26.01.2014 15:22, schrieb Tetsuo Handa:
> Thomas B臘hler wrote:
>> This looks exactly like the problem experienced by Tetsuo Handa in [1].
>> However, for me, his solution, i.e. setting
>> CONFIG_PHYSICAL_ALIGN=0x100
>> instead of
>> CONFIG_PHYSICAL_ALIGN=0x10
>> doesn't help and the sy
Thomas B臘hler wrote:
> This looks exactly like the problem experienced by Tetsuo Handa in [1].
> However, for me, his solution, i.e. setting
> CONFIG_PHYSICAL_ALIGN=0x100
> instead of
> CONFIG_PHYSICAL_ALIGN=0x10
> doesn't help and the symptoms stay the same (and, according to the
> docum
Good morning,
I am trying to build Linux 3.13 on i686 with CONFIG_MODVERSIONS enabled
(for configuration, see [2]). Upon booting it in a VM, I discovered that
I was unable to load several kernel modules, like ext4:
ext4: disagrees about version of symbol d_tmpfile
ext4: Unknown symbol d_tmpfile (
24 matches
Mail list logo