Anthony Wright
2011-Sep-23 11:22 UTC
[Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro Supermicro X8DTL-iF motherboard with 16GB of RAM. If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I run it under xen dmidecode fails to work. On other systems with different hardware but identical software dmidecode works correctly under xen. On this hardware with xen 3.4.1 & linux 2.6.18, dmidecode works correctly under xen. The error message suggests to me that the bios data is partially available as it gets the number of structures correct, but is corrupted fairly early on. There are no DomUs running on the system. I have attached a good and a bad dmidecode output log. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-23 13:32 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote:> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro > Supermicro X8DTL-iF motherboard with 16GB of RAM. > > If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If ICan you attach the beginning of the kernel bootup log? It should have some entry about 1-1 mappings. Make sure to run Linux with "debug loglevel=8" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-23 14:49 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 23/09/2011 14:32, Konrad Rzeszutek Wilk wrote:> On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote: >> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro >> Supermicro X8DTL-iF motherboard with 16GB of RAM. >> >> If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I > Can you attach the beginning of the kernel bootup log? It should > have some entry about 1-1 mappings. Make sure to run Linux with "debug loglevel=8"Please find attached. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-26 14:13 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Fri, Sep 23, 2011 at 03:49:47PM +0100, Anthony Wright wrote:> On 23/09/2011 14:32, Konrad Rzeszutek Wilk wrote: > > On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote: > >> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro > >> Supermicro X8DTL-iF motherboard with 16GB of RAM. > >> > >> If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I > > Can you attach the beginning of the kernel bootup log? It should > > have some entry about 1-1 mappings. Make sure to run Linux with "debug loglevel=8" > Please find attached.> 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on 9a->100 > 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on bf780->100000 > 2011 Sep 23 14:45:41 kernel: [ 0.000000] Set 264422 page(s) to 1-1 mapping. > 2011 Sep 23 14:45:41 kernel: [ 0.000000] BIOS-provided physical RAM map: > 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000000000 - 0000000000099000 (usable) > 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000099800 - 0000000000100000 (reserved).. snip.. So 99C00 is right at cusp of ''usuable'' and ''reserved''. Meaning that region falls within the 4KB page. And we did not set the 1-1 mapping for 99 (we started at 9A). But now that I think of it - this is Linux E820 which does get modified. Can you also provide the hypervisor E820 output? You can get ''xl dmesg'' for that. That should provide the "virgin" output of the e820 which we use for 1-1 mapping. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-26 14:48 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 26/09/2011 15:13, Konrad Rzeszutek Wilk wrote:> On Fri, Sep 23, 2011 at 03:49:47PM +0100, Anthony Wright wrote: >> On 23/09/2011 14:32, Konrad Rzeszutek Wilk wrote: >>> On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote: >>>> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro >>>> Supermicro X8DTL-iF motherboard with 16GB of RAM. >>>> >>>> If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I >>> Can you attach the beginning of the kernel bootup log? It should >>> have some entry about 1-1 mappings. Make sure to run Linux with "debug loglevel=8" >> Please find attached. >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on 9a->100 >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on bf780->100000 >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Set 264422 page(s) to 1-1 mapping. >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] BIOS-provided physical RAM map: >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000000000 - 0000000000099000 (usable) >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000099800 - 0000000000100000 (reserved) > .. snip.. > > So 99C00 is right at cusp of ''usuable'' and ''reserved''. Meaning that region > falls within the 4KB page. And we did not set the 1-1 mapping for 99 (we > started at 9A). > > But now that I think of it - this is Linux E820 which does get modified. > Can you also provide the hypervisor E820 output? You can get ''xl dmesg'' > for that. That should provide the "virgin" output of the e820 which we > use for 1-1 mapping.I''m not quite sure I understand all that, but I think you would find the xl dmesg output helpful, so I''ve attached it. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-26 19:37 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Mon, Sep 26, 2011 at 03:48:52PM +0100, Anthony Wright wrote:> On 26/09/2011 15:13, Konrad Rzeszutek Wilk wrote: > > On Fri, Sep 23, 2011 at 03:49:47PM +0100, Anthony Wright wrote: > >> On 23/09/2011 14:32, Konrad Rzeszutek Wilk wrote: > >>> On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote: > >>>> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro > >>>> Supermicro X8DTL-iF motherboard with 16GB of RAM. > >>>> > >>>> If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I > >>> Can you attach the beginning of the kernel bootup log? It should > >>> have some entry about 1-1 mappings. Make sure to run Linux with "debug loglevel=8" > >> Please find attached. > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on 9a->100 > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] 1-1 mapping on bf780->100000 > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Set 264422 page(s) to 1-1 mapping. > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] BIOS-provided physical RAM map: > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000000000 - 0000000000099000 (usable) > >> 2011 Sep 23 14:45:41 kernel: [ 0.000000] Xen: 0000000000099800 - 0000000000100000 (reserved) > > .. snip.. > > > > So 99C00 is right at cusp of ''usuable'' and ''reserved''. Meaning that region > > falls within the 4KB page. And we did not set the 1-1 mapping for 99 (we > > started at 9A). > > > > But now that I think of it - this is Linux E820 which does get modified. > > Can you also provide the hypervisor E820 output? You can get ''xl dmesg'' > > for that. That should provide the "virgin" output of the e820 which we > > use for 1-1 mapping. > I''m not quite sure I understand all that, but I think you would find the > xl dmesg output helpful, so I''ve attached it.Thanks.> __ __ _ _ _ _ > \ \/ /___ _ __ | || | / | / | > \ // _ \ ''_ \ | || |_ | | | | > / \ __/ | | | |__ _|| |_| | > /_/\_\___|_| |_| |_|(_)_(_)_| > > (XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21 08:25:36 GMT 2011 > (XEN) Latest ChangeSet: unavailable > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode.That bites ^^^^> (XEN) Truncating RAM from 17825792kB to 16777216kB> (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 0000000000099800 (usable) > (XEN) 0000000000099800 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000bf780000 (usable) > (XEN) 00000000bf78e000 - 00000000bf790000 type 9Ok, so this patch should shed some light and potentially fix your problem. Please try it out and attach the serial log for Linux kernel. Thx. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-28 09:08 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 26/09/2011 20:37, Konrad Rzeszutek Wilk wrote:>> __ __ _ _ _ _ >> \ \/ /___ _ __ | || | / | / | >> \ // _ \ ''_ \ | || |_ | | | | >> / \ __/ | | | |__ _|| |_| | >> /_/\_\___|_| |_| |_|(_)_(_)_| >> >> (XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21 08:25:36 GMT 2011 >> (XEN) Latest ChangeSet: unavailable >> (XEN) Bootloader: GNU GRUB 0.97 >> (XEN) Command line: >> (XEN) Video information: >> (XEN) VGA is text mode 80x25, font 8x16 >> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds >> (XEN) Disc information: >> (XEN) Found 4 MBR signatures >> (XEN) Found 4 EDD information structures >> (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode. > That bites ^^^^ >> (XEN) Truncating RAM from 17825792kB to 16777216kBDoes this mean that 32 bit Xen can only use a maximum of 16GB of RAM? If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor?>> (XEN) Xen-e820 RAM map: >> (XEN) 0000000000000000 - 0000000000099800 (usable) >> (XEN) 0000000000099800 - 00000000000a0000 (reserved) >> (XEN) 00000000000e4000 - 0000000000100000 (reserved) >> (XEN) 0000000000100000 - 00000000bf780000 (usable) >> (XEN) 00000000bf78e000 - 00000000bf790000 type 9 > Ok, so this patch should shed some light and potentially fix your problem. Please > try it out and attach the serial log for Linux kernel. Thx.The patch works perfectly. I''ve attached a copy of the kernel log with ''debug loglevel=8'' _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-28 13:28 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
> >> (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode. > > That bites ^^^^ > >> (XEN) Truncating RAM from 17825792kB to 16777216kB > Does this mean that 32 bit Xen can only use a maximum of 16GB of RAM? > > If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor?Yes. I''ve been doing that without any trouble.> > >> (XEN) Xen-e820 RAM map: > >> (XEN) 0000000000000000 - 0000000000099800 (usable) > >> (XEN) 0000000000099800 - 00000000000a0000 (reserved) > >> (XEN) 00000000000e4000 - 0000000000100000 (reserved) > >> (XEN) 0000000000100000 - 00000000bf780000 (usable) > >> (XEN) 00000000bf78e000 - 00000000bf790000 type 9 > > Ok, so this patch should shed some light and potentially fix your problem. Please > > try it out and attach the serial log for Linux kernel. Thx. > The patch works perfectly. I''ve attached a copy of the kernel log with > ''debug loglevel=8''Yeeey! Great. Thanks for testing it. We are re-doing that whole E820 parsing for the next version of Linux (3.2) so will integrate the "essence" of that patch. Would you be up for testing a different variant of that patch just to make sure? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-28 16:07 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote:>>>> (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode. >>> That bites ^^^^ >>>> (XEN) Truncating RAM from 17825792kB to 16777216kB >> Does this mean that 32 bit Xen can only use a maximum of 16GB of RAM? >> >> If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor? > Yes. I''ve been doing that without any trouble.I tried to get this so work some time ago and failed. Do I need a 64 bit Dom0 kernel with a 64 bit xen hypervisor or can I get away with a 32 bit Dom0 kernel?>> The patch works perfectly. I''ve attached a copy of the kernel log with >> ''debug loglevel=8'' > Yeeey! Great. Thanks for testing it. We are re-doing that whole E820 parsing > for the next version of Linux (3.2) so will integrate the "essence" of that > patch. > > Would you be up for testing a different variant of that patch just to make > sure?Not a problem, ship me the patch when you''re ready. I''m running 3.0.4 at the moment and would prefer to stick with 3.0.x for now, so hope that won''t be a problem. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-28 16:32 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Wed, Sep 28, 2011 at 05:07:07PM +0100, Anthony Wright wrote:> On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote: > >>>> (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode. > >>> That bites ^^^^ > >>>> (XEN) Truncating RAM from 17825792kB to 16777216kB > >> Does this mean that 32 bit Xen can only use a maximum of 16GB of RAM? > >> > >> If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor? > > Yes. I''ve been doing that without any trouble. > I tried to get this so work some time ago and failed. Do I need a 64 bit > Dom0 kernel with a 64 bit xen hypervisor or can I get away with a 32 bit > Dom0 kernel?You can get away with a 32-bit dom0 kernel.> >> The patch works perfectly. I''ve attached a copy of the kernel log with > >> ''debug loglevel=8'' > > Yeeey! Great. Thanks for testing it. We are re-doing that whole E820 parsing > > for the next version of Linux (3.2) so will integrate the "essence" of that > > patch. > > > > Would you be up for testing a different variant of that patch just to make > > sure? > Not a problem, ship me the patch when you''re ready. I''m running 3.0.4 at > the moment and would prefer to stick with 3.0.x for now, so hope that > won''t be a problem.Ok. Thx! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David Vrabel
2011-Sep-28 17:02 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 28/09/11 17:07, Anthony Wright wrote:> On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote: >> >> Would you be up for testing a different variant of that patch just to make >> sure? > > Not a problem, ship me the patch when you''re ready. I''m running 3.0.4 at > the moment and would prefer to stick with 3.0.x for now, so hope that > won''t be a problem.I''ve just posted an updated patch series that should include a fix for your dmidecode problem. http://lists.xensource.com/archives/html/xen-devel/2011-09/msg01621.html If you running 3.0.4 you will also need the first two patches from http://lists.xensource.com/archives/html/xen-devel/2011-09/msg00817.html Please give these a try and let me know if they work. Thanks. David _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Oct-04 12:19 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 28/09/2011 18:02, David Vrabel wrote:> On 28/09/11 17:07, Anthony Wright wrote: >> On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote: >>> Would you be up for testing a different variant of that patch just to make >>> sure? >> Not a problem, ship me the patch when you''re ready. I''m running 3.0.4 at >> the moment and would prefer to stick with 3.0.x for now, so hope that >> won''t be a problem. > I''ve just posted an updated patch series that should include a fix for > your dmidecode problem. > > http://lists.xensource.com/archives/html/xen-devel/2011-09/msg01621.html > > If you running 3.0.4 you will also need the first two patches from > > http://lists.xensource.com/archives/html/xen-devel/2011-09/msg00817.html > > Please give these a try and let me know if they work. > > Thanks. > > DavidI''ve tried to apply these patches by cutting and pasting them from the URL, but there''s seven of them, I''m having to manually edit them due to the browser truncating them, and then most don''t apply even when I relax the fuzzing. Could you email me a single patch that applies to 3.0.4? thanks, Anthony. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Oct-05 15:16 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Tue, Oct 04, 2011 at 01:19:06PM +0100, Anthony Wright wrote:> On 28/09/2011 18:02, David Vrabel wrote: > > On 28/09/11 17:07, Anthony Wright wrote: > >> On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote: > >>> Would you be up for testing a different variant of that patch just to make > >>> sure? > >> Not a problem, ship me the patch when you''re ready. I''m running 3.0.4 at > >> the moment and would prefer to stick with 3.0.x for now, so hope that > >> won''t be a problem. > > I''ve just posted an updated patch series that should include a fix for > > your dmidecode problem. > > > > http://lists.xensource.com/archives/html/xen-devel/2011-09/msg01621.html > > > > If you running 3.0.4 you will also need the first two patches from > > > > http://lists.xensource.com/archives/html/xen-devel/2011-09/msg00817.html > > > > Please give these a try and let me know if they work. > > > > Thanks. > > > > David > I''ve tried to apply these patches by cutting and pasting them from the > URL, but there''s seven of them, I''m having to manually edit them due to > the browser truncating them, and then most don''t apply even when I relax > the fuzzing. > > Could you email me a single patch that applies to 3.0.4?Anthony, If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git tree. Mainly the #linux-next or #testing branch. They both have David''s new e820 code. The way to get it is: git clone oss.oracle.com/git/kwilk/xen.git cd xen git checkout origin/linux-next make -j90 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Oct-06 12:53 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
[This email is either empty or too large to be displayed at this time]
Konrad Rzeszutek Wilk
2011-Oct-06 16:07 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
> > If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git > > tree. Mainly the #linux-next or #testing branch. They both have David''s new > > e820 code. > > > > The way to get it is: > > > > git clone oss.oracle.com/git/kwilk/xen.git > > cd xen > > git checkout origin/linux-next > > make -j90 > Sorry it panicked :-( > I''ve attached two photos of the two flavours of panic & a copy of the > config.No serial console? Did it panic when you booted as baremetal?> It seems to get through the initial kernel boot and hands over to my > init script, but panics early on in that process, probably at the point > that udev is loading modules.Looks completly unrelated to the dmidecode issue. Lets attack one thing at a time. Can you move the ioatdma.ko as .bak so it wont load and try again. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Oct-10 15:25 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On 06/10/2011 17:07, Konrad Rzeszutek Wilk wrote:>>> If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git >>> tree. Mainly the #linux-next or #testing branch. They both have David''s new >>> e820 code. >>> >>> The way to get it is: >>> >>> git clone oss.oracle.com/git/kwilk/xen.git >>> cd xen >>> git checkout origin/linux-next >>> make -j90 >> Sorry it panicked :-( >> I''ve attached two photos of the two flavours of panic & a copy of the >> config. > No serial console? Did it panic when you booted as baremetal?Sorry - no serial console - I hadn''t really intended to become part kernel hacker!! We''re looking for leads to see if we can set it up, but I''m going to have to look through the attic into some old dusty boxes... It runs through fine on bare metal.>> It seems to get through the initial kernel boot and hands over to my >> init script, but panics early on in that process, probably at the point >> that udev is loading modules. > Looks completly unrelated to the dmidecode issue. Lets attack one thing > at a time. > > Can you move the ioatdma.ko as .bak so it wont load and try again.I moved the ioatdma.ko module out of the way, but I''m still getting the panics in my init script as udev registers the devices. It''s the same panic as I attached a photo of in the previous email (the one with xen_force_evtchk_callback & do_coprocessor_segment_overrun in the call stack). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Oct-10 16:15 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Mon, Oct 10, 2011 at 04:25:37PM +0100, Anthony Wright wrote:> On 06/10/2011 17:07, Konrad Rzeszutek Wilk wrote: > >>> If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git > >>> tree. Mainly the #linux-next or #testing branch. They both have David''s new > >>> e820 code. > >>> > >>> The way to get it is: > >>> > >>> git clone oss.oracle.com/git/kwilk/xen.git > >>> cd xen > >>> git checkout origin/linux-next > >>> make -j90 > >> Sorry it panicked :-( > >> I''ve attached two photos of the two flavours of panic & a copy of the > >> config. > > No serial console? Did it panic when you booted as baremetal? > Sorry - no serial console - I hadn''t really intended to become part > kernel hacker!! We''re looking for leads to see if we can set it up, but > I''m going to have to look through the attic into some old dusty boxes...Heheh.> > It runs through fine on bare metal.Ok, this was the #linux-next branch right? If you did: git checkout v3.1-rc8 and built that kernel does it work? (Trying to figure out if the patches in #linux-next are the cause of your failure).> > >> It seems to get through the initial kernel boot and hands over to my > >> init script, but panics early on in that process, probably at the point > >> that udev is loading modules. > > Looks completly unrelated to the dmidecode issue. Lets attack one thing > > at a time. > > > > Can you move the ioatdma.ko as .bak so it wont load and try again. > I moved the ioatdma.ko module out of the way, but I''m still getting the > panics in my init script as udev registers the devices. It''s the same > panic as I attached a photo of in the previous email (the one with > xen_force_evtchk_callback & do_coprocessor_segment_overrun in the call > stack).Oh, I somehow missed the do_coprocessor_segment_overrun. That looks to be something entirely new or perhaps: http://bugs.debian.org/642154 Hm, let me take a look at the photos once more. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Oct-10 16:18 UTC
Re: [Xen-devel] dmidecode doesn''t work under xen 4.1.1 on certain hardware
On Mon, Oct 10, 2011 at 04:25:37PM +0100, Anthony Wright wrote:> On 06/10/2011 17:07, Konrad Rzeszutek Wilk wrote: > >>> If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git > >>> tree. Mainly the #linux-next or #testing branch. They both have David''s new > >>> e820 code. > >>> > >>> The way to get it is: > >>> > >>> git clone oss.oracle.com/git/kwilk/xen.git > >>> cd xen > >>> git checkout origin/linux-next > >>> make -j90 > >> Sorry it panicked :-( > >> I''ve attached two photos of the two flavours of panic & a copy of the > >> config. > > No serial console? Did it panic when you booted as baremetal? > Sorry - no serial console - I hadn''t really intended to become part > kernel hacker!! We''re looking for leads to see if we can set it up, but > I''m going to have to look through the attic into some old dusty boxes...I just realized that you can run netconsole - so no need for serial console. But.. <scratches his head> I am really baffled by this. None of the patches in #linux-next do anything there. Please do try to run v3.1-rc8 (or v3.1-rc9) and see if that fails? If it does then we can try to play a bit of bisection game and figure out what caused this mayhem. Is your motherboard easily bought online? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel