-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 while apt-get install cvs in a non0domain Unable to handle kernel NULL pointer dereference at virtual address 000000b2 ~ printing eip: c019e50c *pde = ma 00000000 pa 55555000 ~ [<c017eeb6>] scan_bitmap_block+0xea/0x2c0 ~ [<c017f338>] scan_bitmap+0x1f4/0x228 ~ [<c0180397>] reiserfs_allocate_blocknrs+0x237/0x514 ~ [<c018b458>] reiserfs_allocate_blocks_for_region+0x21c/0x1358 ~ [<c0199e38>] search_for_position_by_key+0x8c/0x37c ~ [<c0199f2e>] search_for_position_by_key+0x182/0x37c ~ [<c0150afd>] alloc_buffer_head+0x11/0x44 ~ [<c01861d0>] make_cpu_key+0x30/0x34 ~ [<c0198951>] pathrelse+0x21/0x30 ~ [<c018d996>] reiserfs_file_write+0x42a/0x5ec ~ [<c013ef45>] do_wp_page+0x381/0x414 ~ [<c01201b1>] update_process_times+0x29/0x30 ~ [<c01124bd>] do_page_fault+0x3c5/0x5b0 ~ [<c0112544>] do_page_fault+0x44c/0x5b0 ~ [<c0127598>] rcu_check_quiescent_state+0x58/0x6c ~ [<c0127658>] __rcu_process_callbacks+0xa8/0x10c ~ [<c012030a>] run_timer_softirq+0x13a/0x1d0 ~ [<c012faf7>] handle_IRQ_event+0x2f/0x74 ~ [<c012faf7>] handle_IRQ_event+0x2f/0x74 ~ [<c014c8b3>] vfs_write+0x8b/0xd0 ~ [<c014c99b>] sys_write+0x3b/0x68 ~ [<c0109368>] syscall_call+0x7/0xb Oops: 0000 [#1] PREEMPT Modules linked in: zaptel crc_ccitt CPU: 0 EIP: 0061:[<c019e50c>] Not tainted VLI EFLAGS: 00010206 (2.6.10) EIP is at reiserfs_in_journal+0xc0/0x180 eax: 000000aa ebx: 0003b700 ecx: 000004bd edx: c4811000 esi: 00000001 edi: c0455000 ebp: 00003700 esp: c1da9be0 ds: 007b es: 007b ss: 0069 Process frontend (pid: 5190, threadinfo=c1da8000 task=c1f97a40) Stack: c4811000 00003700 c480f038 c0455000 c1da9c60 c017eeb6 c0455000 00000007 ~ 00003700 00000001 c1da9c10 000036f2 00000000 00000000 00000007 c0455000 ~ c1da9c60 c0444800 c017f338 c1da9eb4 00000007 c1da9c60 00008000 00000001 Call Trace: ~ [<c017eeb6>] scan_bitmap_block+0xea/0x2c0 ~ [<c017f338>] scan_bitmap+0x1f4/0x228 ~ [<c0180397>] reiserfs_allocate_blocknrs+0x237/0x514 ~ [<c018b458>] reiserfs_allocate_blocks_for_region+0x21c/0x1358 ~ [<c0199e38>] search_for_position_by_key+0x8c/0x37c ~ [<c0199f2e>] search_for_position_by_key+0x182/0x37c ~ [<c0150afd>] alloc_buffer_head+0x11/0x44 ~ [<c01861d0>] make_cpu_key+0x30/0x34 ~ [<c0198951>] pathrelse+0x21/0x30 ~ [<c018d996>] reiserfs_file_write+0x42a/0x5ec ~ [<c013ef45>] do_wp_page+0x381/0x414 ~ [<c01201b1>] update_process_times+0x29/0x30 ~ [<c01124bd>] do_page_fault+0x3c5/0x5b0 ~ [<c0112544>] do_page_fault+0x44c/0x5b0 ~ [<c0127598>] rcu_check_quiescent_state+0x58/0x6c ~ [<c0127658>] __rcu_process_callbacks+0xa8/0x10c ~ [<c012030a>] run_timer_softirq+0x13a/0x1d0 ~ [<c012faf7>] handle_IRQ_event+0x2f/0x74 ~ [<c012faf7>] handle_IRQ_event+0x2f/0x74 ~ [<c014c8b3>] vfs_write+0x8b/0xd0 ~ [<c014c99b>] sys_write+0x3b/0x68 ~ [<c0109368>] syscall_call+0x7/0xb Code: d8 c1 f8 0d c1 e2 07 31 c2 89 f9 8d 04 1b 31 c2 c1 e9 07 31 d1 81 e1 ff 1f 00 00 8b 14 24 8b 84 8a 0c 81 00 00 85 c0 74 12 89 f6 <39> 58 08 0f 84 83 00 00 00 8b 40 20 85 c0 75 f0 31 d2 85 d2 b8 ~ dpkg: error processing cvs (--configure): ~ subprocess post-installation script killed by signal (Segmentation fault) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHlkjihYL426P5W4RAtOmAJwJ+XrtMX4m8RwIGsZbFZBgBuoeKgCdFF/M oFwnci+jObh1YtltQWIlCXk=q0O+ -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok At least I''m able to reproduce something all the stuff are in http://www.junghanns.net/asterisk/downloads/bristuff-0.2.0-RC7f.tar.gz this tgz contain a script that download zaptel drivers and compile it against the running kernel this is the problem: domain1:~# lsmod Module Size Used by domain1:~# modprobe zaptel Zapata Telephony Interface Registered on major 196 domain1:~# lsmod Module Size Used by zaptel 222468 0 crc_ccitt 2176 1 zaptel domain1:~# insmod bristuff-0.2.0-RC7f/zaphfc/zaphfc.ko zaphfc: no version for "zt_receive" found: kernel tainted. PCI: Enabling device 0000:00:0b.0 (0002 -> 0003) PCI: Obtained IRQ 19 for device 0000:00:0b.0 zaphfc: CCD/Billion/Asuscom 2BD0 configured at mem 0xc48be000 fifo 0xc3b08000(0x 3b08000) IRQ 19 HZ 1000 zaphfc: Card 0 configured for TE mode general protection fault: 0000 [#1] PREEMPT Modules linked in: zaphfc zaptel crc_ccitt CPU: 0 EIP: 0061:[<c49301ad>] Tainted: GF VLI EFLAGS: 00010202 (2.6.10) EIP is at zt_chan_reg+0x9/0xd8 [zaptel] eax: 00000002 ebx: 00000001 ecx: c48e896a edx: c3af0114 esi: c3af0114 edi: 00000202 ebp: c3af0114 esp: c39b1ec8 ds: 007b es: 007b ss: 0069 Process insmod (pid: 970, threadinfo=c39b0000 task=c10b7080) Stack: 00000001 00000000 c3af0004 c492256c c3af0114 ffffffff c01b9a8f c3af1241 ~ ffffffff 00000003 00000000 0000000a ffffffff 00000000 00000002 ffffffff ~ ffffffff 00000003 c3af1110 c3af1aac 00000000 c01b9d52 c3af1238 3c50edc8 Call Trace: ~ [<c492256c>] zt_register+0xcc/0x218 [zaptel] ~ [<c01b9a8f>] vsnprintf+0x223/0x46c ~ [<c01b9d52>] vsprintf+0x16/0x1c ~ [<c01b9d6a>] sprintf+0x12/0x18 ~ [<c48e81b9>] zthfc_initialize+0x17d/0x1b8 [zaphfc] ~ [<c0118655>] vprintk+0xfd/0x188 ~ [<c48e83d1>] hfc_findCards+0x1dd/0x3a4 [zaphfc] ~ [<c48e85d2>] init_module+0x3a/0x60 [zaphfc] ~ [<c012e1e2>] sys_init_module+0x15e/0x20c ~ [<c0109368>] syscall_call+0x7/0xb Code: 00 6a 00 ba 01 00 00 00 e8 89 50 7e fb 59 eb 95 89 f6 5b c3 89 f6 8b 93 f4 ~ 01 00 00 e9 53 ff ff ff 90 57 56 53 8b 74 24 10 9c 5f <fa> ba 00 e0 ff ff 21 e2 ~ ff 42 14 bb 01 00 00 00 8d 76 00 8b 14 ~ <1>general protection fault: 0000 [#2] PREEMPT Modules linked in: zaphfc zaptel crc_ccitt CPU: 0 EIP: 0061:[<c48e7bda>] Tainted: GF VLI EFLAGS: 00010286 (2.6.10) EIP is at hfc_interrupt+0x1e/0x33c [zaphfc] eax: 00000000 ebx: c3ae6800 ecx: c130ef60 edx: c1323998 esi: 00000286 edi: c1323998 ebp: 00000013 esp: c1323918 ds: 007b es: 007b ss: 0069 Process syslogd (pid: 892, threadinfo=c1322000 task=c12f15a0) Stack: 00000000 c130e380 c130ef60 00000000 c1323998 00000013 c012faf7 00000013 ~ c3ae6800 c1323998 00000000 c1322000 00000013 c0364400 c1322000 c012fc09 ~ c130ef60 c1323998 00000000 00000000 fbffb000 00000000 c010ddad c0105cc7 Call Trace: ~ [<c012faf7>] handle_IRQ_event+0x2f/0x74 ~ [<c012fc09>] __do_IRQ+0xcd/0x128 ~ [<c010ddad>] do_IRQ+0x19/0x24 ~ [<c0105cc7>] evtchn_do_upcall+0x9f/0x100 ~ [<c0109517>] hypervisor_callback+0x37/0x40 ~ [<c0105c26>] force_evtchn_callback+0xa/0xc ~ [<c01fa21c>] xencons_tx_flush_task_routine+0x4c/0x50 ~ [<c010545a>] __ctrl_if_tx_tasklet+0x14a/0x164 ~ [<c011cb97>] tasklet_action+0x4f/0x94 ~ [<c011c91b>] __do_softirq+0x8f/0xa0 ~ [<c011c975>] do_softirq+0x49/0x4c ~ [<c012fac5>] irq_exit+0x35/0x38 ~ [<c010ddb2>] do_IRQ+0x1e/0x24 ~ [<c0105cc7>] evtchn_do_upcall+0x9f/0x100 ~ [<c0109517>] hypervisor_callback+0x37/0x40 ~ [<c019c212>] reiserfs_paste_into_item+0x17e/0x238 ~ [<c018bb11>] reiserfs_allocate_blocks_for_region+0x8d5/0x1358 ~ [<c0199e38>] search_for_position_by_key+0x8c/0x37c ~ [<c01861d0>] make_cpu_key+0x30/0x34 ~ [<c0198951>] pathrelse+0x21/0x30 ~ [<c018d996>] reiserfs_file_write+0x42a/0x5ec ~ [<c0108785>] setup_sigcontext+0x385/0x47c ~ [<c0231c59>] sys_recvfrom+0x9d/0xf4 ~ [<c0231c99>] sys_recvfrom+0xdd/0xf4 ~ [<c02366c3>] datagram_poll+0x1f/0xbc ~ [<c015cba4>] poll_freewait+0x3c/0x44 ~ [<c015ced3>] do_select+0x1a7/0x2b0 ~ [<c01bab16>] copy_from_user+0x2e/0x54 ~ [<c014cc40>] do_readv_writev+0x158/0x218 ~ [<c018d56c>] reiserfs_file_write+0x0/0x5ec ~ [<c0231cc9>] sys_recv+0x19/0x20 ~ [<c014cd84>] vfs_writev+0x3c/0x48 ~ [<c014ce33>] sys_writev+0x3b/0x68 ~ [<c0109368>] syscall_call+0x7/0xb Code: f6 81 c3 00 02 00 00 e9 27 fe ff ff 90 55 57 56 53 83 ec 08 8b 5c 24 20 31 ~ c0 85 db 74 30 8b 73 10 85 f6 0f 84 08 03 00 00 9c 5e <fa> ba 00 e0 ff ff 21 e2 ~ ff 42 14 8b 4b 10 8a 41 70 84 c0 78 1d ~ <0>Kernel panic - not syncing: Fatal exception in interrupt ~ <0>Rebooting in 1 seconds.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHnA8ihYL426P5W4RAshFAJ9c4t03dbql+rhGV19tPZ4tOepA/ACbBNtB fEBQcGxAs6Ev5szT0Vj2Rpc=Arxz -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On 25 Feb 2005, at 00:24, visik7 wrote:> Ok At least I''m able to reproduce something > all the stuff are in > http://www.junghanns.net/asterisk/downloads/bristuff-0.2.0-RC7f.tar.gz > this tgz contain a script that download zaptel drivers > and compile it against the running kernel > this is the problem: >Your compiled driver contains privileged instructions that guests are not allowed to execute. Either these are hardcoded within the driver or it has compiled itself against arch/i386 rather than arch/xen. If you are running on xen-unstable then we can add CLI/STI to the instructions that we emulate and that may get the driver working. But we don''t emulate instructions in 2.0-testing so if you are running the stable series you will have to dig into teh driver a bit and work out how to pull in the Xen definitions of cli() and sti(). -- Keir ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keir Fraser wrote: | Your compiled driver contains privileged instructions that guests | are not allowed to execute. Either these are hardcoded within the | driver or it has compiled itself against arch/i386 rather than | arch/xen. | | If you are running on xen-unstable then we can add CLI/STI to the | instructions that we emulate and that may get the driver working. | But we don''t emulate instructions in 2.0-testing so if you are | running the stable series you will have to dig into teh driver a | bit and work out how to pull in the Xen definitions of cli() and | sti(). | | -- Keir I understand. I''m running xen stable 2.0.4 but I''m planning to upgrade to unstable if it solves my problem, the question is how much unstable is ''unstable'', I mean for a production system. still one thing: the first oops occured while apt-get install cvs on domain1 then no modprobe or access to the zaptel driver, what happened ? I ask you this ''couse I''m totally incompetent about reading an oops or debugging a problem like this thank you ~ Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHtrtihYL426P5W4RAgCqAJ9Ss3TWdgnwpLqEykANftaG4jAp8QCfQczh ZUGSn7iBAoWjweq1/A+z8TY=ELnH -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On 25 Feb 2005, at 07:59, visik7 wrote:> I understand. > I''m running xen stable 2.0.4 but I''m planning to upgrade to unstable > if it solves my problem, the question is > how much unstable is ''unstable'', I mean for a production system. > still one thing: the first oops occured while apt-get install cvs on > domain1 then no modprobe or access to the zaptel driver, > what happened ? > I ask you this ''couse I''m totally incompetent about reading an oops or > debugging a problem like this > thank you >Marco, After writing my previosu email I''ve concluded that, even if we fix cli/sti instructions, there are other arch-dependencies that are much harder for us to handle automatically, or even with static rewriting of the driver binary. Really, since you are building this driver from source, the correct course of action is to find why it compiled against i386 rather than xen architecture. It is probably something really simple: e.g., did you build the driver while in native Linux and only after that reboot into XenLinux? If you know how, taking a look at the compiler command line and Makefiles will probably make it fairly obvious how to make the driver look at arch/xen rather than arch/i386. -- Keir ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keir Fraser wrote: | After writing my previosu email I''ve concluded that, even if we fix | cli/sti instructions, there are other arch-dependencies that are | much harder for us to handle automatically, or even with static | rewriting of the driver binary. | | Really, since you are building this driver from source, the correct | course of action is to find why it compiled against i386 rather | than xen architecture. It is probably something really simple: | e.g., did you build the driver while in native Linuxt and only | after hat reboot into XenLinux? If you know how, taking a look at | the compiler command line and Makefiles will probably make it | fairly obvious how to make the driver look at arch/xen rather than | arch/i386. | | -- Keir | | ok I do the following steps: compile a kernel linux-2.6.10-xen0 and use it both for dom0 and domU than after run a domU I get the source of linux-2.6.10-xen0 tree into /usr/src/linux-2.6.10 (getting also linux-2.6.10-xen-sparse and putting it in the same dir of the source (so no broken links)) after doing this I compiled my driver against this source I check the source tree of the module but there aren''t no explicit reference to i386 thankyou ~ Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCIlvTihYL426P5W4RAkErAJ9+h9J1ZF0N3aSeFq+S1437IvKLHQCfSvAD +al2WPxpY2sr0wqXjMfE8HI=HNSj -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keir Fraser wrote: | | On 25 Feb 2005, at 07:59, visik7 wrote: | Really, since you are building this driver from source, the correct | course of action is to find why it compiled against i386 rather than xen | architecture. It is probably something really simple: e.g., did you | build the driver while in native Linux and only after that reboot into | XenLinux? If you know how, taking a look at the compiler command line | and Makefiles will probably make it fairly obvious how to make the | driver look at arch/xen rather than arch/i386. | | -- Keir Really I can''t figure how to check if I''m building agains arch/xen or arch/i386 can u help me thanks Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCJPWUihYL426P5W4RAsk0AKCeb6y8FF4jspbh82tAhz8WwmWuGACePkV1 EM8KcdbrXrJnBF8QyhmtAq8=ED8j -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On 1 Mar 2005, at 23:07, visik7 wrote:> Really I can''t figure how to check if I''m building agains arch/xen or > arch/i386 > can u help me > thanks > MarcoWe''ve just done some comparsion of modules built against arch/i386 and arch/xen, and decided that there isn''t so much difference between them after all. I''ll add CLI/STI emulation to xen-unstable and let you know when I;ve done that. With that support checked in your driver ought to work. -- Keir ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keir Fraser wrote: | | On 1 Mar 2005, at 23:07, visik7 wrote: | |> Really I can''t figure how to check if I''m building agains arch/xen or |> arch/i386 |> can u help me |> thanks |> Marco | | | We''ve just done some comparsion of modules built against arch/i386 and | arch/xen, and decided that there isn''t so much difference between them | after all. I''ll add CLI/STI emulation to xen-unstable and let you know | when I;ve done that. With that support checked in your driver ought to | work. | | -- Keir | | Well I''ll wait for it anyway, do I need to recompile only the hipervisor from the unstable branch or also the kernels and tools ? Thanks Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCJakQihYL426P5W4RAilRAJ0SkpnKW3g/KtZbApg32EOQBFZ0hQCfSW2K 4kohoWGvBVkwkgr9HOYw59I=5YU2 -----END PGP SIGNATURE----- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel