[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cron <buildd@kullervo> update-buildd.net status



On Mon, Feb 11, 2013 at 03:19:14PM +0100, Andreas Schwab wrote:
> "Christian T. Steigies" <cts@debian.org> writes:
> 
> > On kullervo it happens about twice a day, mostly in some buildd scripts (and
> > not during the actual build, I hope). Can you suggest something to look at
> > this in detail?
> 
> As a first step you should log as much as possible of the context when
> the sigill happens.

Here is a bit more:

[141324.520000] pc=0xc00e0cae, fa=0xc00e0cae
[141324.520000] 68060 access error, fslw=9428014
[141324.520000] Unable to handle kernel access at virtual address 86d42628
[141324.520000] Oops: 00000000
[141324.520000] Modules linked in: ipv6 dm_snapshot dm_mod loop rtc_rp5c01 zorro8390 parport_amiga parport evdev dmasound_paula dmasound_core soundcore
[141324.520000] PC: [<000399ce>] __send_signal.part.28+0x7e/0x1f6
[141324.520000] SR: 2708  SP: 06ff5e3c  a2: 04cb8ae0
[141324.520000] d0: 06d42a18    d1: 0000000e    d2: 00000004    d3: 00000000
[141324.520000] d4: 00000000    d5: 8001cc00    a0: 86d42628    a1: 036e1900
[141324.520000] Process buildd-watcher (pid: 30172, task=04cb8ae0)
[141324.520000] Frame format=4 fault addr=86d42628 fslw=00851000
[141324.520000] Stack from 06ff5e78:
[141324.520000]         04cb8ae0 00000004 06ff5ef8 0065dad0 c0172000 06ff5f78 00039b92 00000004
[141324.520000]         06ff5ef8 04cb8ae0 00000000 00000000 00002010 00000004 00000000 04cb8ae0
[141324.520000]         0003a3dc 00000004 06ff5ef8 04cb8ae0 00000000 0000000b 4c3a3a56 80005008
[141324.520000]         06ff5fc4 002a8bec 00005dc8 00000004 06ff5ef8 04cb8ae0 09428014 06ff5fc4
[141324.520000]         00000004 00000000 00030001 c00e0cae 8001cc00 800054bc efd0df50 06ff5fc4
[141324.520000]         002a8bec c0172000 06ff5f34 00002014 06ff5f44 00002014 00000010 5b313431
[141324.520000] Call Trace: [<00039b92>] send_signal+0x4c/0x78
[141324.520000]  [<00002010>] do_one_initcall+0x8/0x19c
[141324.520000]  [<0003a3dc>] force_sig_info+0x8e/0x9a
[141324.520000]  [<002a8bec>] printk+0x0/0x18
[141324.520000]  [<00005dc8>] trap_c+0x7c/0x33c
[141324.520000]  [<00030001>] do_syslog+0x3b1/0x432
[141324.520000]  [<002a8bec>] printk+0x0/0x18
[141324.520000]  [<00002014>] do_one_initcall+0xc/0x19c
[141324.520000]  [<00002014>] do_one_initcall+0xc/0x19c
[141324.520000]  [<00040000>] cwq_dec_nr_in_flight+0x1c/0x8e
[141324.520000]  [<002a8bfe>] printk+0x12/0x18
[141324.520000]  [<0000615c>] buserr_c+0xd4/0x6d0
[141324.520000]  [<000025ca>] buserr+0x1e/0x24
[141324.520000]  [<08000800>] ip6_dst_destroy+0x58/0x6c [ipv6]
[141324.520000]  [<0004c00e>] do_timer+0x3ae/0xbee
[141324.520000] 
[141324.520000] Code: 0118 206c 0004 294b 0004 268c 2748 0004 <208b> 4a8e 6700 00c0 7001 b08e 6700 0090 41eb 000c 4aae 0008 6d00 0110 209e 275e
[141324.520000] Disabling lock debugging due to kernel taint


Christian


Reply to: