* kernel crash
@ 2008-01-29 10:32 fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
0 siblings, 2 replies; 44+ messages in thread
From: fenglg @ 2008-01-29 10:32 UTC (permalink / raw)
To: netfilter-devel
netfilter-devel
I use linux-2.6.18, and there is a bridge with eth0 and eth1. The eth0 and eth1 connetcswitchs which use vlan trunk(802.1q). When i run system some hours, the kernel is crash, anyone can help me.
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010
printing eip:
c030f15d
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
Modules linked in: ipt_recent_mac ip_nat_ftp ip_conntrack_ftp ip_nat_h323 ip_con
ntrack_h323 ip_nat_irc iptable_nat ip_nat ipt_ipp2p ipsec e1000 e100
CPU: 0
EIP: 008 #1)
EIP is at br_nf_pre_routing_finish+0x1d/0x340
eax: c16e7980 ebx: 00000000 ecx: 00000001 edx: c16e7980
esi: de4cb020 edi: c0456520 ebp: de8d2000 esp: c03fbce4
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, ti=c03fa000 task=c0371180 task.ti=c03fa000)
Stack: 00000002 c02f0f53 db39ae30 db39ae30 00000002 e081854b db39ae30 00000002
00000000 c03fbdd4 df8f3c00 c0459560 de8d2000 00000001 c03fbda0 fff644c4
c03fbdd4 c030f140 e0818703 00000000 c03fbdd4 de8d2000 00000000 c030f140
Call Trace:
[<c02f0f53>] icmp_packet+0xc3/0xd0
[<e081854b>] ip_nat_fn+0x7b/0x1f0 [iptable_nat]
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<e0818703>] ip_nat_in+0x43/0xc0 [iptable_nat]
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<c02a3f78>] nf_iterate+0x78/0x90
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<c02a400e>] nf_hook_slow+0x7e/0x120
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<c030a840>] br_handle_frame_finish+0x0/0x130
[<c030f9e2>] br_nf_pre_routing+0x212/0x400
[<c030f140>] br_nf_pre_routing_finish+0x0/0x340
[<c02a3f78>] nf_iterate+0x78/0x90
[<c030a840>] br_handle_frame_finish+0x0/0x130
[<c030a840>] br_handle_frame_finish+0x0/0x130
[<c02a400e>] nf_hook_slow+0x7e/0x120
[<c030a840>] br_handle_frame_finish+0x0/0x130
[<c030ab80>] br_handle_frame+0x1d0/0x210
[<c030a840>] br_handle_frame_finish+0x0/0x130
[<c02854b1>] netif_receive_skb+0x171/0x2e0
[<c027eb0e>] kfree_skbmem+0x5e/0x90
[<e0844358>] e1000_clean_rx_irq+0x1b8/0x530 [e1000]
[<e0843dac>] e1000_clean+0x6c/0x120 [e1000]
[<c02857c5>] net_rx_action+0x85/0x110
[<c01202ea>] __do_softirq+0xca/0xf0
[<c0120345>] do_softirq+0x35/0x40
[<c0120395>] irq_exit+0x45/0x50
[<c0105936>] do_IRQ+0x36/0x70
[<c0103a76>] common_interrupt+0x1a/0x20
[<c0100db1>] default_idle+0x31/0x60
[<c0100e82>] cpu_idle+0x82/0xa0
[<c03ff9c8>] start_kernel+0x1a8/0x200
[<c03ff330>] unknown_bootoption+0x0/0x1e0
Code: 10 01 e9 7a ff ff ff 8d b4 26 00 00 00 00 55 57 56 53 81 ec c0 00 00 00 8b
94 24 d4 00 00 00 8b 9a 80 00 00 00 8b 6a 14 8b 72 20 <8b> 43 10 a8 01 74 14 0f
b6 42 75 24 f8 0c 03 88 42 75 8b 43 10
EIP: [<c030f15d>] br_nf_pre_routing_finish+0x1d/0x340 SS:ESP 0068:c03fbce4
<0>Kernel panic - not syncing: Fatal exception in interrupt
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2008-01-29 10:32 kernel crash fenglg
@ 2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
1 sibling, 0 replies; 44+ messages in thread
From: Patrick McHardy @ 2008-01-29 13:34 UTC (permalink / raw)
To: fenglg; +Cc: netfilter-devel
fenglg wrote:
> netfilter-devel
>
> I use linux-2.6.18, and there is a bridge with eth0 and eth1. The eth0 and eth1 connetcswitchs which use vlan trunk(802.1q). When i run system some hours, the kernel is crash, anyone can help me.
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010
> printing eip:
> c030f15d
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT SMP
> Modules linked in: ipt_recent_mac ip_nat_ftp ip_conntrack_ftp ip_nat_h323 ip_con
> ntrack_h323 ip_nat_irc iptable_nat ip_nat ipt_ipp2p ipsec e1000 e100
> CPU: 0
> EIP: 008 #1)
> EIP is at br_nf_pre_routing_finish+0x1d/0x340
Could you try 2.6.24?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2008-01-29 10:32 kernel crash fenglg
2008-01-29 13:34 ` Patrick McHardy
@ 2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
1 sibling, 1 reply; 44+ messages in thread
From: Jan Engelhardt @ 2008-01-29 17:55 UTC (permalink / raw)
To: fenglg; +Cc: netfilter-devel, kaber
On Jan 29 2008 18:32, fenglg wrote:
>
>I use linux-2.6.18, and there is a bridge with eth0 and eth1. The eth0 and
>eth1 connetcswitchs which use vlan trunk(802.1q). When i run system some
>hours, the kernel is crash, anyone can help me.
>
>BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010
>EIP is at br_nf_pre_routing_finish+0x1d/0x340
>eax: c16e7980 ebx: 00000000 ecx: 00000001 edx: c16e7980
>esi: de4cb020 edi: c0456520 ebp: de8d2000 esp: c03fbce4
>Code: 10 01 e9 7a ff ff ff 8d b4 26 00 00 00 00 55 57 56 53 81 ec c0 00 00 00 8b
> 94 24 d4 00 00 00 8b 9a 80 00 00 00 8b 6a 14 8b 72 20 <8b> 43 10 a8 01 74 14 0f
> b6 42 75 24 f8 0c 03 88 42 75 8b 43 10
Thanks for the report.
All signs point to skb->nf_bridge being NULL.
static int br_nf_pre_routing_finish(struct sk_buff *skb)
{
struct net_device *dev = skb->dev;
struct iphdr *iph = ip_hdr(skb);
struct nf_bridge_info *nf_bridge = skb->nf_bridge;
int err;
boom-> if (nf_bridge->mask & BRNF_PKT_TYPE) {
Hm... now what? :)
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2008-01-29 17:55 ` Jan Engelhardt
@ 2008-01-29 17:59 ` Patrick McHardy
0 siblings, 0 replies; 44+ messages in thread
From: Patrick McHardy @ 2008-01-29 17:59 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: fenglg, netfilter-devel
Jan Engelhardt wrote:
> On Jan 29 2008 18:32, fenglg wrote:
>> I use linux-2.6.18, and there is a bridge with eth0 and eth1. The eth0 and
>> eth1 connetcswitchs which use vlan trunk(802.1q). When i run system some
>> hours, the kernel is crash, anyone can help me.
>>
>> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010
>> EIP is at br_nf_pre_routing_finish+0x1d/0x340
>> eax: c16e7980 ebx: 00000000 ecx: 00000001 edx: c16e7980
>> esi: de4cb020 edi: c0456520 ebp: de8d2000 esp: c03fbce4
>> Code: 10 01 e9 7a ff ff ff 8d b4 26 00 00 00 00 55 57 56 53 81 ec c0 00 00 00 8b
>> 94 24 d4 00 00 00 8b 9a 80 00 00 00 8b 6a 14 8b 72 20 <8b> 43 10 a8 01 74 14 0f
>> b6 42 75 24 f8 0c 03 88 42 75 8b 43 10
>
> Thanks for the report.
>
> All signs point to skb->nf_bridge being NULL.
>
> static int br_nf_pre_routing_finish(struct sk_buff *skb)
> {
> struct net_device *dev = skb->dev;
> struct iphdr *iph = ip_hdr(skb);
> struct nf_bridge_info *nf_bridge = skb->nf_bridge;
> int err;
>
> boom-> if (nf_bridge->mask & BRNF_PKT_TYPE) {
>
>
> Hm... now what? :)
2.6.18 and 2.6.24 differ significantly in how the bridging stuff
is handled, so the preferred way would be to try to reproduce this
with 2.6.24. Debugging a 18 month old kernel doesn't seem too
useful unless we know the problem is still present.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Kernel Crash
@ 2014-01-16 10:24 Nieścierowicz Adam
0 siblings, 0 replies; 44+ messages in thread
From: Nieścierowicz Adam @ 2014-01-16 10:24 UTC (permalink / raw)
To: netdev
Hi,
I do not know if I am writing in a good place.
With the launch of the new kernel 3.13.0-rc8 on on our router errors
appear.
http://wklej.org/id/1238075/ [1]
Is this a kernel bug or wrong configuration?
--
Thanks,
Adam Nieścierowicz
Links:
------
[1] http://wklej.org/id/1238075/
^ permalink raw reply [flat|nested] 44+ messages in thread
* Kernel crash
@ 2012-05-30 17:35 Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
0 siblings, 1 reply; 44+ messages in thread
From: Guido Winkelmann @ 2012-05-30 17:35 UTC (permalink / raw)
To: ceph-devel
Hi,
I just saw a kernel crash on one of my machines. It had the cephfs from the
ceph cluster mounted using the in-kernel client:
[522247.751071] [<ffffffff814d3383>] ? release_sock+0xe3/0x110
[522247.751182] [<ffffffff815ea438>] __bad_area_nosemaphore+0x1d1/0x1f0
[522247.751290] [<ffffffff815ea46a>] bad_area_nosemaphore+0x13/0x15
[522247.751397] [<ffffffff815f7b76>] do_page_fault+0x416/0x4f0
[522247.751503] [<ffffffff814ce5dd>] ? sock_recvmsg+0x11d/0x140
[522247.751611] [<ffffffff812c0ea6>] ? cpumask_next_and+0x36/0x50
[522247.751718] [<ffffffff815f4475>] page_fault+0x25/0x30
[522247.751828] [<ffffffffa03ccba4>] ? ceph_x_destroy_authorizer+0x14/0x40
[libceph]
[522247.751995] [<ffffffffa040f9be>] get_authorizer+0x6e/0x140 [ceph]
[522247.752104] [<ffffffff814ce646>] ? kernel_recvmsg+0x46/0x60
[522247.752213] [<ffffffffa03b969a>] prepare_write_connect+0x17a/0x270
[libceph]
[522247.752378] [<ffffffffa03bba75>] con_work+0x755/0x2c40 [libceph]
[522247.752486] [<ffffffff810876a3>] ? update_rq_clock+0x43/0x1b0
[522247.752598] [<ffffffffa03bb320>] ? ceph_msg_new+0x2d0/0x2d0 [libceph]
[522247.752707] [<ffffffff810747ae>] process_one_work+0x11e/0x470
[522247.752815] [<ffffffff810755bf>] worker_thread+0x15f/0x360
[522247.752925] [<ffffffff81075460>] ? manage_workers+0x230/0x230
[522247.753032] [<ffffffff81079da3>] kthread+0x93/0xa0
[522247.753137] [<ffffffff815fd2a4>] kernel_thread_helper+0x4/0x10
[522247.753245] [<ffffffff81079d10>] ?
kthread_freezable_should_stop+0x70/0x70
[522247.753355] [<ffffffff815fd2a0>] ? gs_change+0x13/0x13
[522247.753459] ---[ end trace b9ba686594d99f89 ]---
These lines are all that I could still read on the screen. (Good thing there's
Opens Source OCR programs out there...) I do not know how to extract more
information about that crash (scrolling up does not work), but I'm leaving the
machine like that over night in case someone can tell me.
Kernel version was 3.3.6-3.fc16.x86_64, Ceph cluster is version 0.47.2. The
crash happened after I issued an rbd command. Another thing that might be
related is that I stopped and restarted the entire cluster twice since
mounting the cephfs. The first time, I disabled cephx, the second time I
enabled it again.
Regards,
Guido
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2012-05-30 17:35 Kernel crash Guido Winkelmann
@ 2012-06-08 16:35 ` Tommi Virtanen
0 siblings, 0 replies; 44+ messages in thread
From: Tommi Virtanen @ 2012-06-08 16:35 UTC (permalink / raw)
To: Guido Winkelmann; +Cc: ceph-devel
On Wed, May 30, 2012 at 10:35 AM, Guido Winkelmann
<guido-ceph@thisisnotatest.de> wrote:
> I just saw a kernel crash on one of my machines. It had the cephfs from the
> ceph cluster mounted using the in-kernel client:
...
> [522247.751290] [<ffffffff815ea46a>] bad_area_nosemaphore+0x13/0x15
> [522247.751397] [<ffffffff815f7b76>] do_page_fault+0x416/0x4f0
> [522247.751503] [<ffffffff814ce5dd>] ? sock_recvmsg+0x11d/0x140
> [522247.751611] [<ffffffff812c0ea6>] ? cpumask_next_and+0x36/0x50
> [522247.751718] [<ffffffff815f4475>] page_fault+0x25/0x30
> [522247.751828] [<ffffffffa03ccba4>] ? ceph_x_destroy_authorizer+0x14/0x40
> [libceph]
> [522247.751995] [<ffffffffa040f9be>] get_authorizer+0x6e/0x140 [ceph]
> [522247.752104] [<ffffffff814ce646>] ? kernel_recvmsg+0x46/0x60
Hi. I can't find any other reports of kernel crashes related to
ceph_x_destroy_authorizer either.
If this keeps happening, please file a bug report at
http://tracker.newdream.net/ with details on the circumstance in which
it triggers, and we'll get back to it once we re-focus on the Ceph
Distributed File System. Right now, we are focusing our efforts in the
RADOS, RBD and radosgw functionality, in an effort to stabilize and
optimize the core object store of the product even more.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2011-10-06 21:59 Pau Espin Pedrol
0 siblings, 0 replies; 44+ messages in thread
From: Pau Espin Pedrol @ 2011-10-06 21:59 UTC (permalink / raw)
To: linux-kernel
Hi,
Since more a less kernel 3.0 my intel i5 has kernel panics (computer
stops working at all and keyboard leds start to blink).
I can't recall exactly, but I think it was more a less the same time
since I started using nvidia drivers with twinview (2 screens), which
could may be the cause?
I'm using archlinux, so I've been told the kernel is a vanilla kernel.
I can somehow "reproduce" the crash here. I mean, every day when I
boot my PC, I know a kernel crash will happen in the next 1-15 min
aprox. Then I reboot my PC and I don't have any kernel panic till next
day.
It sometimes happens at bootime, sometimes when I'm just logged in
into X server and doing work or when I halt the computer.
I was able to get some photos of the kernel backtrace when the crash
appears while booting/halting.
Here you have the link to a tar.gz file which contains several photos
with backtraces:
http://pespin.espeweb.net/tmp/kernel-panic/kernel-panic-bt.tar.gz
You can find more information of the PC in several text files I
uploaded tho the same dir: http://pespin.espeweb.net/tmp/kernel-panic/
Let's hope they are of help to you.
If you need me to try something or give me more information just tell me!
PS: Please add me to the CC when answering this mail as I am not
subscribed to the ml ;)
--
Pau Espin Pedrol
mail/jabber: pespin.shar@gmail.com
http://blog.espeweb.net
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
0 siblings, 1 reply; 44+ messages in thread
From: M @ 2011-09-22 18:45 UTC (permalink / raw)
To: linux-mm
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
Hi,
I am running Fedora 15 644bit on AMD 64bit arch. After update 3 days ago, kernel started to crash when I submit a heavy computation job. It happened today also with similar type of job.
I submitted a bug report to https://bugzilla.redhat.com/ d=740613 . They referred me to contact linux memory management group. I have also uploaded my log file in the bug report. I will be very happy to provide more information if required to resolve this issue.
Thanks.
[-- Attachment #2: Type: text/html, Size: 605 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2011-09-22 18:45 M
@ 2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
0 siblings, 1 reply; 44+ messages in thread
From: Dave Jones @ 2011-09-22 21:24 UTC (permalink / raw)
To: M; +Cc: linux-mm
On Thu, Sep 22, 2011 at 11:45:25AM -0700, M wrote:
> Hi,
>
> I am running Fedora 15 644bit on AMD 64bit arch. After update 3 days ago, kernel started to crash when I submit a heavy computation job. It happened today also with similar type of job.
>
> I submitted a bug report to https://bugzilla.redhat.com/ d=740613 . They referred me to contact linux memory management group. I have also uploaded my log file in the bug report. I will be very happy to provide more information if required to resolve this issue.
>
> Thanks.
(fixed url is https://bugzilla.redhat.com/show_bug.cgi?id=740613)
Manoj's report here has a system with 32GB of RAM and 40GB of swap
oomkill'ing processes when there seems to be ram still available.
I note the gfp mask of the failing allocations has GFP_HIGHMEM,
and this apparently doesn't happen when he runs 32-bit.
Could that be a clue ?
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2011-09-22 21:24 ` Dave Jones
@ 2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
0 siblings, 1 reply; 44+ messages in thread
From: David Rientjes @ 2011-09-22 21:38 UTC (permalink / raw)
To: Dave Jones; +Cc: M, linux-mm
[-- Attachment #1: Type: TEXT/PLAIN, Size: 4758 bytes --]
On Thu, 22 Sep 2011, Dave Jones wrote:
> On Thu, Sep 22, 2011 at 11:45:25AM -0700, M wrote:
> > Hi,
> >
> > I am running Fedora 15 644bit on AMD 64bit arch. After update 3 days ago, kernel started to crash when I submit a heavy computation job. It happened today also with similar type of job.
> >
> > I submitted a bug report to https://bugzilla.redhat.com/ d=740613 . They referred me to contact linux memory management group. I have also uploaded my log file in the bug report. I will be very happy to provide more information if required to resolve this issue.
> >
> > Thanks.
>
> (fixed url is https://bugzilla.redhat.com/show_bug.cgi?id=740613)
>
> Manoj's report here has a system with 32GB of RAM and 40GB of swap
> oomkill'ing processes when there seems to be ram still available.
>
Looking at the output of the first oom from
https://bugzilla.redhat.com/attachment.cgi?id=524451
Sep 20 19:39:19 host2 kernel: [1932999.874704] Node 0 DMA free:15892kB min:40kB low:48kB high:60kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15684kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep 20 19:39:19 host2 kernel: [1932999.874727] lowmem_reserve[]: 0 1970 16110 16110
Sep 20 19:39:19 host2 kernel: [1932999.874739] Node 0 DMA32 free:61832kB min:5500kB low:6872kB high:8248kB active_anon:1494456kB inactive_anon:498264kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2018144kB mlocked:0kB dirty:0kB writeback:0kB mapped:20kB shmem:0kB slab_reclaimable:864kB slab_unreclaimable:44kB kernel_stack:0kB pagetables:6632kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep 20 19:39:19 host2 kernel: [1932999.874765] lowmem_reserve[]: 0 0 14140 14140
Sep 20 19:39:19 host2 kernel: [1932999.874772] Node 0 Normal free:39440kB min:39464kB low:49328kB high:59196kB active_anon:12962768kB inactive_anon:1178596kB active_file:236kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:14479360kB mlocked:0kB dirty:0kB writeback:1560kB mapped:164kB shmem:0kB slab_reclaimable:10356kB slab_unreclaimable:12296kB kernel_stack:1504kB pagetables:75224kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:354 all_unreclaimable? yes
Sep 20 19:39:19 host2 kernel: [1932999.874810] lowmem_reserve[]: 0 0 0 0
Sep 20 19:39:19 host2 kernel: [1932999.874817] Node 1 Normal free:44920kB min:45100kB low:56372kB high:67648kB active_anon:14981988kB inactive_anon:1248872kB active_file:812kB inactive_file:792kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:16547840kB mlocked:0kB dirty:0kB writeback:14676kB mapped:392kB shmem:0kB slab_reclaimable:8484kB slab_unreclaimable:11252kB kernel_stack:840kB pagetables:71480kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:2057 all_unreclaimable? yes
Sep 20 19:39:19 host2 kernel: [1932999.874856] lowmem_reserve[]: 0 0 0 0
We can see that both normal zones are under their minimum watermark, so
they are completely oom. We can't allocate in ZONE_DMA32 because of
lowmem_reserve for this gfp mask (61832K - (14140 * 4K) < 5500K) and
ZONE_DMA for the same reason. So there's no RAM available.
Sep 20 19:39:19 host2 kernel: [1932999.874970] 331623 total pagecache pages
Sep 20 19:39:19 host2 kernel: [1932999.874974] 331021 pages in swap cache
Sep 20 19:39:19 host2 kernel: [1932999.874978] Swap cache stats: add 10280280, delete 9949259, find 5232/9633
Sep 20 19:39:19 host2 kernel: [1932999.874982] Free swap = 0kB
And there's no swap available.
> I note the gfp mask of the failing allocations has GFP_HIGHMEM,
> and this apparently doesn't happen when he runs 32-bit.
>
> Could that be a clue ?
>
The problem is this:
Sep 20 19:39:19 host2 kernel: [1933000.196980] [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name
...
Sep 20 19:39:19 host2 kernel: [1933000.197559] [13918] 507 13918 17992270 7758558 4 -17 -1000 root.exe
root.exe is has about 29.5GB of the 32GB available memory in RAM, and it's
set to have a /proc/13918/oom_score_adj of -1000 meaning it's not eligible
for oom killing. So the kernel panics rather than kill the task.
There's not much the kernel can be expected to do in such a configuration,
you've simply exhausted all RAM and swap. You can set
/proc/pid/oom_score_adj to not be -1000 so that it is at least eligible to
be killed in these circumstances rather than panic the machine, but the VM
will continue to oom under this configuration.
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2011-09-22 21:38 ` David Rientjes
@ 2011-09-22 21:53 ` Dave Jones
0 siblings, 0 replies; 44+ messages in thread
From: Dave Jones @ 2011-09-22 21:53 UTC (permalink / raw)
To: David Rientjes; +Cc: M, linux-mm
On Thu, Sep 22, 2011 at 02:38:47PM -0700, David Rientjes wrote:
> The problem is this:
>
> Sep 20 19:39:19 host2 kernel: [1933000.196980] [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name
> ...
> Sep 20 19:39:19 host2 kernel: [1933000.197559] [13918] 507 13918 17992270 7758558 4 -17 -1000 root.exe
>
> root.exe is has about 29.5GB of the 32GB available memory in RAM, and it's
> set to have a /proc/13918/oom_score_adj of -1000 meaning it's not eligible
> for oom killing. So the kernel panics rather than kill the task.
>
> There's not much the kernel can be expected to do in such a configuration,
> you've simply exhausted all RAM and swap. You can set
> /proc/pid/oom_score_adj to not be -1000 so that it is at least eligible to
> be killed in these circumstances rather than panic the machine, but the VM
> will continue to oom under this configuration.
It's surprising that the same workload in 32-bit works.
Manoj, is root.exe recompiled for 64-bit ? I'm wondering if it's just that
the expansion of a lot of unsigned longs are causing increased memory use vs
the original 32bit use-case.
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2007-12-30 18:25 Jerry Geis
0 siblings, 0 replies; 44+ messages in thread
From: Jerry Geis @ 2007-12-30 18:25 UTC (permalink / raw)
To: linux-kernel
I am running kernel 2.6.23.9
last night I had a crash.
This was all that was in the /var/log/messages.
I run centos 5.1 with the above kernel.
This was late at night noone was using the machine.
The machine is an AMD 6400+ X2, NVIDIA (with nvidia drivers). Software
RAID with 2 seagate 500GIG drives as raid-1.
Any know issues with this?
Dec 29 20:28:04 devcentos5x64 kernel: Unable to handle kernel paging
request at 00000000ffff8160 RIP:
Dec 29 20:28:04 devcentos5x64 kernel: [<ffffffff88035502>]
:jbd:journal_commit_transaction+0x328/0x100a
Dec 29 20:28:04 devcentos5x64 kernel: PGD 101af3067 PUD 0
Dec 29 20:28:04 devcentos5x64 kernel: Oops: 0002 [1] SMP
Jerry
^ permalink raw reply [flat|nested] 44+ messages in thread
* Kernel Crash
@ 2006-02-11 5:37 Jayaprakash Shanmugam
0 siblings, 0 replies; 44+ messages in thread
From: Jayaprakash Shanmugam @ 2006-02-11 5:37 UTC (permalink / raw)
To: linuxppc-embedded
Hello Everyone,
I am using MPC 8270 based board with 2.6. It crashes at times.=20
Mostly it is related to timers. I have attached several crash reports
here. Anybody can give me some pointers on what could be wrong ? I
really appreciate your help. Thanks.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C00288C0 LR: C00289FC SP: CF493C80 REGS: cf493bd0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C0018F24 LR: C001A174 SP: CF415E90 REGS: cf415de0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00C15C74, DSISR: 22000000
TASK =3D c05d7b30[549] 'CCMsgHndlrExe' THREAD: cf414000
Last syscall: 104
GPR00: 00000078 CF415E90 C05D7B30 C05D7B30 C02858AC 2800046C 00000000 C0285=
8B0
GPR08: 00C15C74 00000001 C05D7B50 0000008C B4868000 1003811C 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
668
GPR24: C0290000 C0280000 C02820A8 C0280000 00000000 C0285400 C05D7B30 CF415=
E90
NIP [c0018f24] enqueue_task+0x34/0x7c
LR [c001a174] scheduler_tick+0x300/0x360
Call trace:
[c0019c18] account_user_time+0x78/0xe8
[c002924c] update_process_times+0x98/0x150
[c0005504] timer_interrupt+0x88/0x22c
[c000448c] ret_from_except+0x0/0x14
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C013CAF8 LR: C013CCC4 SP: C06FDCA0 REGS: c06fdbf0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00C12048, DSISR: 20000000
TASK =3D c05d7b30[495] 'CCMsgHndlrExe' THREAD: c06fc000
Last syscall: 54
GPR00: 00000001 C06FDCA0 C05D7B30 CF64F0F0 CFAF0000 0004DC93 C0280000 C028A=
C8C
GPR08: 00200200 00C12000 00C12048 CF64F0F0 2010C022 1003811C 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
668
GPR24: C0290000 00000001 00000000 CF64F000 CFAF0000 CF64F0F0 00001032 CF64F=
000
NIP [c013caf8] roothub_a+0xc/0x6c
LR [c013ccc4] ohci_hub_status_data+0xa4/0x1a8
Call trace:
[c0130978] rh_report_status+0x12c/0x164
[c0029460] run_timer_softirq+0x120/0x228
[c0024068] __do_softirq+0xd0/0xd8
[c00240c8] do_softirq+0x58/0x5c
[c002419c] irq_exit+0x54/0x58
[c0005668] timer_interrupt+0x1ec/0x22c
[c000448c] ret_from_except+0x0/0x14
[d106f5a8] FD_ioctl+0x2160/0x35a8 [FDAC1]
[c007375c] do_ioctl+0x84/0xac
[c00739e8] vfs_ioctl+0x88/0x2c8
[c0073c6c] sys_ioctl+0x44/0x78
[c0003de0] ret_from_syscall+0x0/0x44
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
Oops: kernel access of bad are
a, sig: 11 [#1]
PREEMPT
NIP: C0018F24 LR: C001A174 SP: CF415E90 REGS: cf415de0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00C15C74, DSISR: 22000000
TASK =3D c05d7b30[549] 'CCMsgHndlrExe' THREAD: cf414000
Last syscall: 104
GPR00: 00000078 CF415E90 C05D7B30 C05D7B30 C02858AC 2800046C 00000000 C0285=
8B0
GPR08: 00C15C74 00000001 C05D7B50 0000008C B4868000 1003811C 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
668
GPR24: C0290000 C0280000 C02820A8 C0280000 00000000 C0285400 C05D7B30 CF415=
E90
NIP [c0018f24] enqueue_task+0x34/0x7c
LR [c001a174] scheduler_tick+0x300/0x360
Call trace:
[c0019c18] account_user_time+0x78/0xe8
[c002924c] update_process_times+0x98/0x150
[c0005504] timer_interrupt+0x88/0x22c
[c000448c] ret_from_except+0x0/0x14
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C0018F24 LR: C001A150 SP: CF415D70 REGS: cf415cc0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00C1580C, DSISR: 22000000
TASK =3D c0525b30[495] 'CCMsgHndlrExe' THREAD: cf414000
Last syscall: 54
GPR00: 00000000 CF415D70 C0525B30 C0525B30 C0285434 00000001 100300EA C0285=
438
GPR08: 00C1580C 00000001 C0525B50 00000076 DB718800 1003807C 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
5C8
GPR24: C0290000 C0280000 C02820A8 C0280000 00000000 C0285400 C0525B30 CF415=
D70
NIP [c0018f24] enqueue_task+0x34/0x7c
LR [c001a150] scheduler_tick+0x2dc/0x360
Call trace:
[c0019cf0] account_system_time+0x68/0x144
[c002924c] update_process_times+0x98/0x150
[c0005504] timer_interrupt+0x88/0x22c
[c000448c] ret_from_except+0x0/0x14
[c00739e0] vfs_ioctl+0x80/0x2c8
[c0073c6c] sys_ioctl+0x44/0x78
[c0003de0] ret_from_syscall+0x0/0x44
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C0018F24 LR: C001A150 SP: CF415D70 REGS: cf415cc0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00C1580C, DSISR: 22000000
TASK =3D c0525b30[495] 'CCMsgHndlrExe' THREAD: cf414000
Last syscall: 54
GPR00: 00000000 CF415D70 C0525B30 C0525B30 C0285434 00000001 100300EA C0285=
438
GPR08: 00C1580C 00000001 C0525B50 00000076 DB718800 1003807C 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
5C8
GPR24: C0290000 C0280000 C02820A8 C0280000 00000000 C0285400 C0525B30 CF415=
D70
NIP [c0018f24] enqueue_task+0x34/0x7c
LR [c001a150] scheduler_tick+0x2dc/0x360
Call trace:
[c0019cf0] account_system_time+0x68/0x144
[c002924c] update_process_times+0x98/0x150
[c0005504] timer_interrupt+0x88/0x22c
[c000448c] ret_from_except+0x0/0x14
[c00739e0] vfs_ioctl+0x80/0x2c8
[c0073c6c] sys_ioctl+0x44/0x78
[c0003de0] ret_from_syscall+0x0/0x44
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Uninitialised timer!
This is just a warning. Your computer is OK
function=3D0xc013084c, data=3D0xcfa7e1a0
Call trace:
[c0006d48] dump_stack+0x18/0x28
[c0028824] check_timer_failed+0x7c/0x80
[c0028bc8] mod_timer+0x40/0x8c
[c01309ac] rh_report_status+0x160/0x164
[c0029460] run_timer_softirq+0x120/0x228
[c0024068] __do_softirq+0xd0/0xd8
[c00240c8] do_softirq+0x58/0x5c
[c002419c] irq_exit+0x54/0x58
[c0005668] timer_interrupt+0x1ec/0x22c
[c000448c] ret_from_except+0x0/0x14
[d106d50c] FD_ioctl+0xc4/0x35a8 [FDAC1]
[c007375c] do_ioctl+0x84/0xac
[c00739e8] vfs_ioctl+0x88/0x2c8
[c0073c6c] sys_ioctl+0x44/0x78
[c0003de0] ret_from_syscall+0x0/0x44
Uninitialised timer!
This is just a warning. Your computer is OK
function=3D0xc013084c, data=3D0xcfa7e1a0
Call trace:
[c0006d48] dump_stack+0x18/0x28
[c0028824] check_timer_failed+0x7c/0x80
[c0028bc8] mod_timer+0x40/0x8c
[c01309ac] rh_report_status+0x160/0x164
[c0029460] run_timer_softirq+0x120/0x228
[c0024068] __do_softirq+0xd0/0xd8
[c00240c8] do_softirq+0x58/0x5c
[c002419c] irq_exit+0x54/0x58
[c0005668] timer_interrupt+0x1ec/0x22c
[c000448c] ret_from_except+0x0/0x14
Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C00293DC LR: C0029384 SP: CF449D50 REGS: cf449ca0 TRAP: 0300 Not ta=
inted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 0A8324AC, DSISR: 22000000
TASK =3D c05d7b30[549] 'CCMsgHndlrExe' THREAD: cf448000
Last syscall: 54
GPR00: 000AF4C4 CF449D50 C05D7B30 00000001 64F56640 000AF4C3 C0280000 C028A=
E0C
GPR08: C028AE14 CF449D60 CFB224AC 0A8324AC D5990000 10038490 0FFF8000 00000=
000
GPR16: 00000001 7FFFFB30 10016EB9 00000001 00000000 1001751C 10001694 1000E=
734
GPR24: C0290000 C0290000 C0200000 C028A7F4 CF449D60 C028C044 C028A608 00000=
0C3
NIP [c00293dc] run_timer_softirq+0x9c/0x228
LR [c0029384] run_timer_softirq+0x44/0x228
Call trace:
[c0024068] __do_softirq+0xd0/0xd8
[c00240c8] do_softirq+0x58/0x5c
[c002419c] irq_exit+0x54/0x58
[c0005668] timer_interrupt+0x1ec/0x22c
[c000448c] ret_from_except+0x0/0x14
[c00739b8] vfs_ioctl+0x58/0x2c8
[c0073c6c] sys_ioctl+0x44/0x78
[c0003de0] ret_from_syscall+0x0/0x44
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..
Thanks & Regards,
Jayaprakash.
^ permalink raw reply [flat|nested] 44+ messages in thread
* RE: Kernel crash
@ 2005-01-19 12:54 Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
0 siblings, 1 reply; 44+ messages in thread
From: Ian Pratt @ 2005-01-19 12:54 UTC (permalink / raw)
To: Tobias Hunger, xen-devel
> > Try putting xencons=ttyS on the kernel command line or
> perhaps better,
> > remove vga console support.
>
> How?
>
> The options CONFIG_VT, CONFIG_VT_CONSOLE, CONFIG_HW_CONSOLE and
> CONFIG_VGACONSOLE are not listed in menuconfig. Commenting
> them out in
> the .config file will not work either: make readds them
> before building. The
> only way to stop those flags from appearing is to "depend
> !ARCH_XEN" in the
> Kconfig files where they are defined (I guess/hope there are
> less intrusive
> ways, but so far I never had to tweak the kernel build system).
Edit .config and set "# CONFIG_VT_CONSOLE is not set" etc.
> Turning the options off results in no output after the
> initial text from xen,
> informing me about kernel used, etc. xencons=off behaves the
> same way. I have
> no way to interact with the VM but the console, so I am not
> sure whether this
> works or not.
You'll also need console=ttyS0 on the kernel command line (please check
the syntax).
> The -xenU kernels work and give output, but is
> lacking the
> necessary HW support I need.
Please remind me of what you're trying to set up.
Ian
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 12:54 Kernel crash Ian Pratt
@ 2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
` (2 more replies)
0 siblings, 3 replies; 44+ messages in thread
From: Tobias Hunger @ 2005-01-19 14:04 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
On Wednesday 19 January 2005 13:54, Ian Pratt wrote:
> Edit .config and set "# CONFIG_VT_CONSOLE is not set" etc.
I did. The flags reappear during make ARCH=xen and the consoles get added to
my kernel in spite of those settings. That is why I edited the Kconfig files.
Ugly but works...
> You'll also need console=ttyS0 on the kernel command line (please check
> the syntax).
My results so far:
extra="": crash
extra="console=xen": no output (hoping that this turns of the other consoles)
extra="console=tty2": crash
extra="console=ttyS0": no output
extra="xencons=ttyS console=ttyS0": crash
extra="xencons=off": no output
extra="xencons=off console=ttyS0": no output
extra="xencons=off console=tty1": no output
No config_vm, config_vgaconsole, etc. (nothing set in .config that contains
"CONS"): crash
No config_vm, ... with modified Kconfig files: no output
> Please remind me of what you're trying to set up.
Currently I am trying to set up xen for my router at home. That is the only
box I do not absolutely need to work at all times that is powerful enough to
handle xen.
I am trying to use dom0 for the management of domains only, trying not to have
packets traveling through that domain. dom1 is supposed to handle the
internal NIC and do the bridging/routing (still undecided on what to use
here) for other VMs that normally happens in dom0. I then want to set up the
router with access to the external/WLAN NICs in dom2 (connecting to dom2) and
a intranet server in dom3 (also talking to dom2 for the intranet
connectivity). I think this is a nice playground to try the more advanced
features of xen and getting to know the system better.
So far I got dom0 with a custom xen0-based kernel (all the network drivers
removed) and dom3 with the default xenU kernel up. Both work fine. I am now
trying to setup dom1 and move the networking there. dom2 handling the
external NICs should be similar to setup to dom1 with a bit of iptable magic
added.
So how does the console work? How does the console output end up on a port in
dom0?
--
Gruss,
Tobias
------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@aquazul.com So I installed Linux.
------------------------------------------------------------
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: Kernel crash
2005-01-19 14:04 ` Tobias Hunger
@ 2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 17:46 ` Philip R Auld
2 siblings, 0 replies; 44+ messages in thread
From: Keir Fraser @ 2005-01-19 15:12 UTC (permalink / raw)
To: Tobias Hunger; +Cc: Ian Pratt, xen-devel
> My results so far:
> extra="": crash
> extra="console=xen": no output (hoping that this turns of the other consoles)
> extra="console=tty2": crash
> extra="console=ttyS0": no output
> extra="xencons=ttyS console=ttyS0": crash
> extra="xencons=off": no output
> extra="xencons=off console=ttyS0": no output
> extra="xencons=off console=tty1": no output
> No config_vm, config_vgaconsole, etc. (nothing set in .config that contains
> "CONS"): crash
> No config_vm, ... with modified Kconfig files: no output
I've fixed the testing and unstable repositories so that the kernel
will no longer crash. However, since the problem is that the console
cannot be set up because some other driver has got the 'tty0' or
'ttyS0' name already, you still won't get any consol eoutput after
init starts.
'xencons=ttyS console=ttyS0' ought to work. If not then you still have
serial drivers configured into your kernel.
-- Keir
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
@ 2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2 siblings, 1 reply; 44+ messages in thread
From: Derrik Pates @ 2005-01-19 16:54 UTC (permalink / raw)
To: Tobias Hunger; +Cc: Ian Pratt, xen-devel
Tobias Hunger wrote:
> I did. The flags reappear during make ARCH=xen and the consoles get added to
> my kernel in spite of those settings. That is why I edited the Kconfig files.
> Ugly but works...
Are you doing 'make ARCH=xen (menu|x|g)config' ? If you don't, the
config will probably not be correct for your target architecture.
> My results so far:
> extra="": crash
> extra="console=xen": no output (hoping that this turns of the other consoles)
> extra="console=tty2": crash
> extra="console=ttyS0": no output
> extra="xencons=ttyS console=ttyS0": crash
> extra="xencons=off": no output
> extra="xencons=off console=ttyS0": no output
> extra="xencons=off console=tty1": no output
> No config_vm, config_vgaconsole, etc. (nothing set in .config that contains
> "CONS"): crash
> No config_vm, ... with modified Kconfig files: no output
This is on an unprivileged domain? Unprivileged domains don't have a VGA
console, and they don't have access to serial ports; the console is
implemented through an inter-domain communication channel, like the
virtual network and block devices are.
--
Derrik Pates
demon@devrandom.net
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 16:54 ` Derrik Pates
@ 2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
0 siblings, 1 reply; 44+ messages in thread
From: Tobias Hunger @ 2005-01-19 21:05 UTC (permalink / raw)
To: Derrik Pates; +Cc: Ian Pratt, xen-devel
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
On Wednesday 19 January 2005 17:54, Derrik Pates wrote:
> Are you doing 'make ARCH=xen (menu|x|g)config' ? If you don't, the
> config will probably not be correct for your target architecture.
Yes, I do.
The problem is that the console breaks as soon as you set
CONFIG_XEN_PHYSDEV_ACCESS is set to y. With that setting CONFIG_VT_CONSOLE,
CONFIG_HW_CONSOLE, CONFIG_VGA_CONSOLE, etc. are set to 'y' and there is no
way to turn them off again.
You may edit .config and do a 'make ARCH=xen oldconfig', but afterwards those
flags are turned back to 'y'.
I changed the Kconfig files that define those flags to force them to the
off-state. Afterwards there is some output:
xm create -c zzzz
Using config file "/etc/xen/zzzz".
Started domain zzzz, console on port 9602
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.10-xen1 (root@yoda) (gcc version 3.3.5 (Debian 1:3.3.5-6))
#2 Wed Jan 19 21:28:29 CET 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000002000000 (usable)
32MB LOWMEM available.
DMI not present.
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro
That's it, nothing more:-(
> This is on an unprivileged domain? Unprivileged domains don't have a VGA
> console, and they don't have access to serial ports; the console is
> implemented through an inter-domain communication channel, like the
> virtual network and block devices are.
It is a domain with physical device access but with not a privileged guest.
--
Gruss,
Tobias
------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@aquazul.com So I installed Linux.
------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 21:05 ` Tobias Hunger
@ 2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
0 siblings, 1 reply; 44+ messages in thread
From: Keir Fraser @ 2005-01-20 8:56 UTC (permalink / raw)
To: Tobias Hunger; +Cc: Derrik Pates, Ian Pratt, xen-devel
> On Wednesday 19 January 2005 17:54, Derrik Pates wrote:
> > Are you doing 'make ARCH=xen (menu|x|g)config' ? If you don't, the
> > config will probably not be correct for your target architecture.
>
> Yes, I do.
>
> The problem is that the console breaks as soon as you set
> CONFIG_XEN_PHYSDEV_ACCESS is set to y. With that setting CONFIG_VT_CONSOLE,
> CONFIG_HW_CONSOLE, CONFIG_VGA_CONSOLE, etc. are set to 'y' and there is no
> way to turn them off again.
Yes, that looks to be a "feature" of the drivers/char/Kconfig file,
which we only parse for configurations that are to work with
hardware-access privileges.
So that probably ties up tty0, but you should still be able to
register xencons as ttyS0 unless you have accidentally included serial
drivers in your kernel config:
"xencons=ttyS console=ttyS0"
-- Keir
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-20 8:56 ` Keir Fraser
@ 2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
0 siblings, 1 reply; 44+ messages in thread
From: Tobias Hunger @ 2005-01-20 10:00 UTC (permalink / raw)
To: Keir Fraser; +Cc: Derrik Pates, Ian Pratt, xen-devel
[-- Attachment #1: Type: text/plain, Size: 2703 bytes --]
On Thursday 20 January 2005 09:56, Keir Fraser wrote:
> Yes, that looks to be a "feature" of the drivers/char/Kconfig file,
> which we only parse for configurations that are to work with
> hardware-access privileges.
Yes, I found that, too.
> So that probably ties up tty0, but you should still be able to
> register xencons as ttyS0 unless you have accidentally included serial
> drivers in your kernel config:
> "xencons=ttyS console=ttyS0"
I tried that several times: no output whatsoever! I can not see anything wrt.
serial ports in my config, so there shouldn't be drivers for those.
Here is a list of differences between my kernel configuration and the one from
the default xenU kernel. Maybe I am doing something wrong... I am using a
heavily patched Kconfig setup by now, so do not expect to be able to get a
similar config by running *config:-) I use a dash to mark options that are
not listed in one configuration.
xenU: Mine:
CONFIG_XEN y y
CONFIG_ARCH_XEN y y
CONFIG_NO_IDLE_HZ y y
CONFIG_XEN_PRIVILEGED_GUEST not set not set
CONFIG_XEN_PHYSDEV_ACCESS not set y
CONFIG_XEN_BLKDEV_BACKEND not set not set
CONFIG_XEN_NETDEV_BACKEND not set y
CONFIG_XEN_BLKDEV_FRONTEND y y
CONFIG_XEN_NETDEV_FRONTEND y not set
CONFIG_XEN_NETDEV_[...]_TRANS[...] not set -
CONFIG_XEN_BLKDEV_TAP not set not set
CONFIG_XEN_WRITABLE_PAGETABLES y y
CONFIG_XEN_SCRUB_PAGES y y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB y y
CONFIG_X86 y y
CONFIG_X86_64 not set not set
I have "hotplug" and "kobject uevents" as well as "loadable modules" disabled,
the X86 Processor Configuration is mostly identical (I use Athlon, xenU
assumes a P IV).
Bus options:
CONFIG_PCI - y
CONFIG_PCI_DIRECT - y
Kernel debugging/Blockdevices/SCSI: I have kernel debugging, loop and initrd
disabled and SD missing as well.
Networking is mostly identical with my kernel including some drivers and
bridging in addition to what xenU has.
My kernel has fewer filesystems (only the one it needs to read its root FS)
and crypto functionality disabled.
Everything else is identical (with my config having comments for all the
sections skipped in the xenU kernel configuration).
Did I remove too much? Adding XEN_NETDEV_FRONTEND does not change anything by
the way. I can provide you with my .config file if someone is interested.
--
Gruss,
Tobias
------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@aquazul.com So I installed Linux.
------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: Kernel crash
2005-01-20 10:00 ` Tobias Hunger
@ 2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
0 siblings, 1 reply; 44+ messages in thread
From: Keir Fraser @ 2005-01-20 11:30 UTC (permalink / raw)
To: Tobias Hunger; +Cc: Keir Fraser, Derrik Pates, Ian Pratt, xen-devel
> On Thursday 20 January 2005 09:56, Keir Fraser wrote:
> > Yes, that looks to be a "feature" of the drivers/char/Kconfig file,
> > which we only parse for configurations that are to work with
> > hardware-access privileges.
>
> Yes, I found that, too.
>
> > So that probably ties up tty0, but you should still be able to
> > register xencons as ttyS0 unless you have accidentally included serial
> > drivers in your kernel config:
> > "xencons=ttyS console=ttyS0"
>
> I tried that several times: no output whatsoever! I can not see anything wrt.
> serial ports in my config, so there shouldn't be drivers for those.
>
I see no problem if I add those two parameters to my own xenU
boot-parameter list. Why not start with a vanilla/default xenU config
(perhaps with just the PHYSDEV_ACCESS option added), get that working,
and then start adding in options bit by bit?
-- Keir
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
@ 2005-01-19 17:46 ` Philip R Auld
2 siblings, 0 replies; 44+ messages in thread
From: Philip R Auld @ 2005-01-19 17:46 UTC (permalink / raw)
To: Tobias Hunger; +Cc: Ian Pratt, xen-devel
Rumor has it that on Wed, Jan 19, 2005 at 03:04:48PM +0100 Tobias Hunger said:
> On Wednesday 19 January 2005 13:54, Ian Pratt wrote:
> > Edit .config and set "# CONFIG_VT_CONSOLE is not set" etc.
>
> I did. The flags reappear during make ARCH=xen and the consoles get added to
> my kernel in spite of those settings. That is why I edited the Kconfig files.
> Ugly but works...
After you edit .config by hand you need to run "make oldconfig" to get
the changes to take effect.
Cheers,
Phil
--
Philip R. Auld, Ph.D. Egenera, Inc.
Software Architect 165 Forest St.
(508) 858-2628 Marlboro, MA 01752
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
^ permalink raw reply [flat|nested] 44+ messages in thread
* RE: Kernel crash
@ 2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
0 siblings, 1 reply; 44+ messages in thread
From: Ian Pratt @ 2005-01-19 1:31 UTC (permalink / raw)
To: Tobias Hunger, xen-devel
> Couldn't register Xen virtual console driver as tty
You're running a kernel with privileged extensions in a privileged
domain, and I suspect you have the vga console or virtual terminal (VT)
compiled in, and they're grabbing tty1 before xencons gets a chance.
The later failure mode of using an unitiliased console is very ugly and
needs fixing.
Try putting xencons=ttyS on the kernel command line or perhaps better,
remove vga console support.
Ian
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2005-01-19 1:31 Ian Pratt
@ 2005-01-19 10:52 ` Tobias Hunger
0 siblings, 0 replies; 44+ messages in thread
From: Tobias Hunger @ 2005-01-19 10:52 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On Wednesday 19 January 2005 02:31, Ian Pratt wrote:
> You're running a kernel with privileged extensions in a privileged
> domain, and I suspect you have the vga console or virtual terminal (VT)
> compiled in, and they're grabbing tty1 before xencons gets a chance.
Ah!
> The later failure mode of using an unitiliased console is very ugly and
> needs fixing.
That would be nice. I'll try my hand on it, but do not expect too much:-)
> Try putting xencons=ttyS on the kernel command line or perhaps better,
> remove vga console support.
How?
The options CONFIG_VT, CONFIG_VT_CONSOLE, CONFIG_HW_CONSOLE and
CONFIG_VGACONSOLE are not listed in menuconfig. Commenting them out in
the .config file will not work either: make readds them before building. The
only way to stop those flags from appearing is to "depend !ARCH_XEN" in the
Kconfig files where they are defined (I guess/hope there are less intrusive
ways, but so far I never had to tweak the kernel build system).
Turning the options off results in no output after the initial text from xen,
informing me about kernel used, etc. xencons=off behaves the same way. I have
no way to interact with the VM but the console, so I am not sure whether this
works or not. The -xenU kernels work and give output, but is lacking the
necessary HW support I need.
PS: Being able to catch kernel panics in screen is so cool! I really like Xen,
even though so far I have not managed to set it up completly:-)
--
Gruss,
Tobias
------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@aquazul.com So I installed Linux.
------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Kernel crash
@ 2005-01-18 21:50 Tobias Hunger
0 siblings, 0 replies; 44+ messages in thread
From: Tobias Hunger @ 2005-01-18 21:50 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 5200 bytes --]
Hello!
I am trying to build a custom kernel for myself that is supposed to run a
network driver domain. To do so I configured it with the attached settings.
Starting the kernel in a VM I get the following output using xen unstable from
this morning:
Using config file "/etc/xen/yyyy".
Started domain yyyy, console on port 9603
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.10-xen1 (root@xxxx) (gcc version 3.3.5 (Debian 1:3.3.5-6))
#2 Tue Jan 18 20:58:48 CET 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000002000000 (usable)
32MB LOWMEM available.
DMI not present.
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro
Initializing CPU#0
PID hash table entries: 256 (order: 8, 4096 bytes)
Xen reported: 1668.744 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30232k/32768k available (1455k kernel code, 2488k reserved, 355k data,
16k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: AMD Athlon(tm) XP 2000+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
i8042.c: Can't read CTR while initializing i8042.
io scheduler noop registered
io scheduler anticipatory registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Couldn't register Xen virtual console driver as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
mice: PS/2 mouse device common for all mice
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 8,
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 116k freed
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c01c9cf6
*pde = ma 00000000 pa 55555000
[<c01f8abf>] __xencons_tx_flush+0x1ef/0x270
[<c011a323>] console_device+0x33/0x50
[<c01cacc5>] tty_open+0x95/0x2b0
[<c01cac30>] tty_open+0x0/0x2b0
[<c015c506>] chrdev_open+0xa6/0x170
[<c01527b9>] dentry_open+0xf9/0x170
[<c01526b2>] filp_open+0x62/0x70
[<c0152869>] get_unused_fd+0x39/0xe0
[<c01529d9>] sys_open+0x49/0x90
[<c0105070>] init+0x0/0x110
[<c01050f0>] init+0x80/0x110
[<c0107775>] kernel_thread_helper+0x5/0x10
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0061:[<c01c9cf6>] Not tainted VLI
EFLAGS: 00010246 (2.6.10-xen1)
EIP is at init_dev+0x36/0x5c0
eax: 00000000 ebx: c0322200 ecx: ffffffed edx: 00000000
esi: c0322200 edi: 00000001 ebp: 00500001 esp: c0099eb8
ds: 007b es: 007b ss: 0069
Process swapper (pid: 1, threadinfo=c0098000 task=c000b9e0)
Stack: c035decc c02fb1d2 c0099f06 c01f8abf c0099ed8 00000000 00000006 00000003
c029bfe0 c0322200 c0099f18 00500001 c011a323 c029bfe0 c0322200 c036f9c0
00000001 00500001 c01cacc5 c0322200 00000000 c0099f14 00029f3c c02f7700
Call Trace:
[<c01f8abf>] __xencons_tx_flush+0x1ef/0x270
[<c011a323>] console_device+0x33/0x50
[<c01cacc5>] tty_open+0x95/0x2b0
[<c01cac30>] tty_open+0x0/0x2b0
[<c015c506>] chrdev_open+0xa6/0x170
[<c01527b9>] dentry_open+0xf9/0x170
[<c01526b2>] filp_open+0x62/0x70
[<c0152869>] get_unused_fd+0x39/0xe0
[<c01529d9>] sys_open+0x49/0x90
[<c0105070>] init+0x0/0x110
[<c01050f0>] init+0x80/0x110
[<c0107775>] kernel_thread_helper+0x5/0x10
Code: c7 44 24 14 00 00 00 00 ff 0d ac 6d 29 c0 0f 88 ef 2f 00 00 f6 86 9c 00
00 00 10 0f 85 5b 05 00 00 8b 86 ac 00 00 00 8b 54 24 50 <8b> 1c 90 85 db 74
75 8b 83 b8 00 00 00 a8 80 75 61 81 7e 74 04
<0>Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..
************ REMOTE CONSOLE EXITED *****************
Any ideas?
--
Gruss,
Tobias
------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@aquazul.com So I installed Linux.
------------------------------------------------------------
[-- Attachment #1.2: config-2.6.10-xen1.bz2 --]
[-- Type: application/x-bzip2, Size: 3122 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread* Kernel crash
@ 2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
0 siblings, 1 reply; 44+ messages in thread
From: Giuliano Pochini @ 2004-09-05 18:51 UTC (permalink / raw)
To: Alsa-devel
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
10 days passed since the last time I wrote about this problem... but the
problems is still here. Perhaps I didn't explain clearly enough. The program
I attached was buggy, but I meant it makes the kernel crash, not the program
itself. It's attached again to this message. No need to be root. IMHO it's a
quite serious issue the should be fixed ASAP.
It successfully crashes my system after a few attempts:
Linux Jay 2.6.8.1 #2 SMP Wed Aug 18 15:14:51 CEST 2004 ppc unknown
booted with maxcpus=1 and without preempt.
alsa-driver-1.0.6a and CVS-2004-09-05
alsa-lib-1.0.4
gcc 3.4.1
with both the powermac (Snapper) driver and my Echoaudio driver.
I also tested it on a PC with an intel8x1 chip, but I don't know the version
of alsa. Probably 1.0.2. It's the one include with linux 2.6.7-13-mandrake
edition. On this system the kernel doesn't crash nor it oopses, but often
the sound doesn't stop after my proggy segfaults.
--
Giuliano.
[-- Attachment #2: playrec.c --]
[-- Type: text/plain, Size: 7442 bytes --]
#include <math.h>
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <fcntl.h>
#include <unistd.h>
#include <string.h>
#include <errno.h>
#include <sys/poll.h>
#define ALSA_PCM_NEW_HW_PARAMS_API
#define ALSA_PCM_NEW_SW_PARAMS_API
#include <alsa/asoundlib.h>
int samplerate = 44100, periods = 2, periodframes = 4096;
typedef struct {
int16_t frame[2];
} sample_t;
#define NCH 2
#define TEST(err) do { if (err<0) { printf("Error: %s at line %d\n", snd_strerror(err), __LINE__); return 0; } } while(0)
snd_pcm_t *init_channel(const char *pcm_name, snd_pcm_stream_t stream) {
int n, err;
snd_pcm_hw_params_t *hwparams;
snd_pcm_sw_params_t *swparams;
snd_pcm_t *pcm_handle;
snd_pcm_hw_params_alloca(&hwparams);
snd_pcm_sw_params_alloca(&swparams);
err = snd_pcm_open(&pcm_handle, pcm_name, stream, SND_PCM_NONBLOCK);
TEST(err);
/* Init hwparams with full configuration space */
err = snd_pcm_hw_params_any(pcm_handle, hwparams);
TEST(err);
// printf("snd_pcm_hw_params_can_sync_start: %d\n", snd_pcm_hw_params_can_sync_start(hwparams));
// return(0);
err = snd_pcm_hw_params_set_access(pcm_handle, hwparams, SND_PCM_ACCESS_RW_INTERLEAVED);
TEST(err);
/* Set sample format */
err = snd_pcm_hw_params_set_format(pcm_handle, hwparams, SND_PCM_FORMAT_S16_BE);
TEST(err);
/* Set sample rate. If the exact rate is not supported */
/* by the hardware, use nearest possible rate. */
n = samplerate;
snd_pcm_hw_params_set_rate_near(pcm_handle, hwparams, &samplerate, 0);
if (n != samplerate) {
fprintf(stderr, "The rate %d Hz is not supported by your hardware.\nUsing %d Hz instead.\n", n, samplerate);
}
/* Set number of channels */
err = snd_pcm_hw_params_set_channels(pcm_handle, hwparams, 2);
TEST(err);
/* Set number of periods. Periods used to be called fragments. */
err = snd_pcm_hw_params_set_periods(pcm_handle, hwparams, periods, 0);
TEST(err);
err = snd_pcm_hw_params_set_buffer_size(pcm_handle, hwparams, periodframes * periods);
TEST(err);
err = snd_pcm_hw_params(pcm_handle, hwparams);
TEST(err);
if (stream == SND_PCM_STREAM_PLAYBACK) {
err = snd_pcm_sw_params_current(pcm_handle, swparams);
TEST(err);
err = snd_pcm_sw_params_set_start_threshold(pcm_handle, swparams, 0x7fffffff);
TEST(err);
}
// snd_pcm_hw_params_free(hwparams);
return (pcm_handle);
}
void Riempibuf(sample_t * buf, float frq, int n) {
int s;
static double fase = 0;
//printf("fase i=%f ", fase);
for (s = 0; s < n; s++) {
buf[s].frame[0] = buf[s].frame[1] = ceil(31000.0 * sin(fase * 2 * M_PI));
// buf[s].frame[0] = buf[s].frame[1] = ceil(15000.0 * sin(fase * 2 * M_PI) + 15000.0 * sin(fase*2 * 2 * M_PI));
//buf[s].frame[0] = buf[s].frame[1] = ceil(-32765 + 65530 * fmod(fase, 1));
//buf[s].frame[0] = buf[s].frame[1] = fmod(fase, 1)>=0.5 ? 15000.0 : -15000.0;
fase += frq / samplerate;
}
//printf("f=%f\n", fase);
while (fase > 10) fase -= 10;
}
/*
void Riempibuf(sample_t * buf, float frq, int n) {
int s;
static double fase1 = 0, fase2 = 0;
//printf("fase i=%f ", fase);
for (s = 0; s < n; s++) {
buf[s].frame[0] = buf[s].frame[1] = ceil(15000.0 * sin(fase1 * 2 * M_PI) + 15000.0 * sin(fase2 * 2 * M_PI));
fase1 += 10000.0 / samplerate;
fase2 += 11000.0 / samplerate;
}
}
*/
int writebuf(snd_pcm_t * handle, sample_t * buf, size_t frames) {
int r, tot;
tot = 0;
while (frames > 0) {
r = snd_pcm_writei(handle, buf + tot, frames);
if (r == -EAGAIN) {
// return(0);
continue;
} else if (r > 0) {
frames -= r;
tot += r;
} else {
printf("wr err\n");
return (r);
}
}
// printf("Scritti %d\n", tot);
return (0);
}
int main(int argc, char **argv) {
sample_t *buffer_in, *buffer_out;
double frq;
int i, c, r, bufsize, scritti, ricevuti, f;
int min[NCH], max[NCH];
snd_pcm_t *pcm_handle_in, *pcm_handle_out;
pcm_handle_out = init_channel("plughw:0,0,0", SND_PCM_STREAM_PLAYBACK);
if (!pcm_handle_out)
return (-1);
pcm_handle_in = init_channel("plughw:0,0,0", SND_PCM_STREAM_CAPTURE);
if (!pcm_handle_in)
return (-1);
if ((r = snd_pcm_prepare(pcm_handle_out)) < 0) {
printf("Prepare error: %s\n", snd_strerror(r));
exit(0);
}
if ((r = snd_pcm_prepare(pcm_handle_in)) < 0) {
printf("Prepare error: %s\n", snd_strerror(r));
exit(0);
}
if ((r = snd_pcm_link(pcm_handle_out, pcm_handle_in)) < 0) {
printf("Streams link error: %s\n", snd_strerror(r));
exit(0);
}
/*
if (writebuf(pcm_handle_out, buffer_out, BUFR) < 0) {
fprintf(stderr, "write error\n");
exit(0);
}
*/
/*
if ((r = snd_pcm_start(pcm_handle_in)) < 0) {
printf("Go error: %s\n", snd_strerror(r));
exit(0);
}
*/
bufsize=samplerate;
buffer_in=malloc(bufsize * sizeof(sample_t));
buffer_out=malloc(bufsize * sizeof(sample_t));
f = open("Merd.raw", O_TRUNC | O_WRONLY | O_CREAT, 0664);
// for (frq = (float)samplerate / 8192.0; frq <= (float)samplerate / 2; frq *= 1.189207115) { //frq*=1.414213562) {
for (frq = 1000; frq <= 10000; frq += 100) {
// for (frq = 5.0; frq <= (float)samplerate / 2; frq *= sqrt(sqrt(2.0))) {
//int yyy=3;
// Prepara 1 sec. di roba da suonare
Riempibuf(buffer_out, frq, bufsize);
scritti=ricevuti=0;
while (ricevuti<bufsize) {
poll(0, 0, 5);
if (0)
snd_pcm_wait(pcm_handle_in, 1000);
if (scritti == bufsize) {
//snd_pcm_drain(pcm_handle_out);
printf("spedito\n");
//write(f, buffer_out + scritti, rimanenti * sizeof(sample_t));
} else {
r = snd_pcm_writei(pcm_handle_out, buffer_out+scritti, bufsize-scritti);
if (r < 0 && r != -EAGAIN) {
fprintf(stderr, "write error: %s\n", snd_strerror(r));
exit(r);
} else if (r > 0) {
//printf("scr %d %d\n",r,scritti);
//write(f, buffer_out + scritti, r * sizeof(sample_t));
scritti += r;
}
}
do {
r = snd_pcm_readi(pcm_handle_in, buffer_in+ricevuti, bufsize-ricevuti);
if (r > 0) {
write(f, buffer_in, r * sizeof(sample_t));
ricevuti+=r;
printf("rice %d (%d)\n", r, ricevuti);
} else if (r < 0 && r != -EAGAIN) {
printf("rice err: %s\n", snd_strerror(r));
exit(r);
}
} while (r > 0);
}
/* BOOM ! */
snd_pcm_drain(pcm_handle_out);
snd_pcm_drop(pcm_handle_in);
/*
if ((r = snd_pcm_prepare(pcm_handle_out)) < 0) {
printf("Prepare error: %s\n", snd_strerror(r));
exit(0);
}
if ((r = snd_pcm_prepare(pcm_handle_in)) < 0) {
printf("Prepare error: %s\n", snd_strerror(r));
exit(0);
}
*/
min[c] = max[c] = 0;
printf("%f %f %f\n", frq, 20 * log10((double)(max[0] - min[0]) / 60000), 20 * log10((double)(max[1] - min[1]) / 60000));
// printf("Frq=%7.1f dB: Sin=%6.3f Des=%6.3f\n", frq, 20 * log10((double)(max[0] - min[0]) / 60000), 20 * log10((double)(max[1] - min[1]) / 60000));
// printf("Frq=%7.1f min=%6d max=%6d dB: Sin=%6.3f Des=%6.3f\n", frq, min, max, 20 * log10((double)(max[0] - min[0]) / 60000), 20 * log10((double)(max[1] - min[1]) / 60000));
}
close(f);
/* snd_pcm_drop(pcm_handle_out);
snd_pcm_drop(pcm_handle_in);*/
snd_pcm_close(pcm_handle_out);
snd_pcm_close(pcm_handle_in);
return (0);
}
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: Kernel crash
2004-09-05 18:51 Giuliano Pochini
@ 2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
0 siblings, 1 reply; 44+ messages in thread
From: Takashi Iwai @ 2004-09-06 15:16 UTC (permalink / raw)
To: Giuliano Pochini; +Cc: Alsa-devel
At Sun, 5 Sep 2004 20:51:22 +0200,
Giuliano Pochini wrote:
>
> 10 days passed since the last time I wrote about this problem... but the
> problems is still here. Perhaps I didn't explain clearly enough. The program
> I attached was buggy, but I meant it makes the kernel crash, not the program
> itself. It's attached again to this message. No need to be root. IMHO it's a
> quite serious issue the should be fixed ASAP.
>
> It successfully crashes my system after a few attempts:
>
> Linux Jay 2.6.8.1 #2 SMP Wed Aug 18 15:14:51 CEST 2004 ppc unknown
> booted with maxcpus=1 and without preempt.
> alsa-driver-1.0.6a and CVS-2004-09-05
> alsa-lib-1.0.4
> gcc 3.4.1
>
> with both the powermac (Snapper) driver and my Echoaudio driver.
It doesn't crash on my system with SB live with the latest CVS version
but segfaults at line 263 because c is bogus.
The crash looks likely driver-specific, then.
Did you try a UP kernel?
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: Kernel crash
2004-09-06 15:16 ` Takashi Iwai
@ 2004-09-07 7:55 ` Giuliano Pochini
0 siblings, 0 replies; 44+ messages in thread
From: Giuliano Pochini @ 2004-09-07 7:55 UTC (permalink / raw)
To: Takashi Iwai; +Cc: Alsa-devel
On 06-Sep-2004 Takashi Iwai wrote:
>> It successfully crashes my system after a few attempts:
>>
>> Linux Jay 2.6.8.1 #2 SMP Wed Aug 18 15:14:51 CEST 2004 ppc unknown
>> booted with maxcpus=1 and without preempt.
>> alsa-driver-1.0.6a and CVS-2004-09-05
>> alsa-lib-1.0.4
>> gcc 3.4.1
>>
>> with both the powermac (Snapper) driver and my Echoaudio driver.
>
> It doesn't crash on my system with SB live with the latest CVS
> version but segfaults at line 263 because c is bogus.
> The crash looks likely driver-specific, then.
No, I don't think so. I already found (one of?) the cause, but
I forgot to mention it again, sorry. It happens because ALSA
calls the .free() pcm callback without calling .trigger(STOP)
and .close() first. Jaroslav posted a patch which didn't work,
then the discussion stopped. The problem occurs only when the
substreams are linked and the userpace app is badly broken
like mine.
> Did you try a UP kernel?
Just tried. Same thing with Echo driver, but the Pmac
driver doen't seem to crash anymore. And about the
PC I don't know if that kernel is MP of UP.
--
Giuliano.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2003-05-29 20:41 Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
0 siblings, 2 replies; 44+ messages in thread
From: Gordon Messmer @ 2003-05-29 20:41 UTC (permalink / raw)
To: netfilter-devel
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
We recently have had trouble with kernel crashes on a Linux 2.4.20 box
used as a NAT gateway. The machine is running Slackware 8.1 with a
vanilla 2.4.20 kernel. The kernel configuration is attached. The
message-log attachment contains the full dmesg output, as captured by a
remote syslog server, as well as the last messages received before the
box hung:
May 28 16:18:08 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
`&ct->tuplehash[IP_CT_DIR_REPLY]'(f687fbc4) not in &ip_conntrack_hash
[hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
`&ct->tuplehash[IP_CT_DIR_REPLY]'(f687cd24) not in &ip_conntrack_hash
[hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
`&ct->tuplehash[IP_CT_DIR_REPLY]'(f687ce64) not in &ip_conntrack_hash
[hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
What further information would be useful in tracking down this problem?
[-- Attachment #2: message-log.txt.gz --]
[-- Type: application/x-gzip, Size: 5563 bytes --]
[-- Attachment #3: kernel-config.gz --]
[-- Type: application/x-gzip, Size: 3915 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2003-05-29 20:41 kernel crash Gordon Messmer
@ 2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
1 sibling, 0 replies; 44+ messages in thread
From: John M Flinchbaugh @ 2003-05-29 21:20 UTC (permalink / raw)
To: Gordon Messmer; +Cc: netfilter-devel
[-- Attachment #1: Type: text/plain, Size: 2995 bytes --]
On Thu, May 29, 2003 at 01:41:11PM -0700, Gordon Messmer wrote:
> May 28 16:18:08 tog-wakko4 kernel: LIST_DELETE:
ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687fbc4) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
> May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE:
ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687cd24) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
> May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE:
ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687ce64) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
what iptables statements are you running at startup?
i had a similar problem, i think, last summer due to _overlapping_ nat
rules causing a race condition. i'm not sure anyone ever knew what to
do about it, but i did find that tweaking some rules kept the bug from
being triggered.
http://marc.theaimsgroup.com/?l=netfilter-devel&m=102750186506947&w=2
i used to use:
iptables -t nat -A POSTROUTING -j SNAT --to 64.192.31.41
iptables -t nat -A POSTROUTING -j SNAT --to 192.168.1.1
iptables -t nat -A POSTROUTING -j SNAT --to 127.0.0.1
and now i use something very similar to (now i have 3 ifs):
iptables -t nat -A POSTROUTING -j SNAT -o eth0 --to 64.192.31.41
iptables -t nat -A POSTROUTING -o eth1 -s 192.168.1.0/24 \
-j SNAT --to 192.168.1.1
iptables -t nat -A POSTROUTING -o eth2 -s 192.168.2.0/24 \
-j SNAT --to 192.168.2.1
i've formulated the opinion that the first set of rules would match a
packet on multiple rules and mangle the packet more than once, while
the new rule set only matches packets going certain directions, so a
packet only matches one rule.
i think these multiple matches caused a race condition and hung the
machine. does this make any sense to anyone?
the idea of these rules is to mangle the destination of a packet that
came in on an interface and got forwarded back out the same interface.
this allows a port forward to work from any network, even if it's the
same network. here's my example:
iptables -t nat -A PREROUTING -p tcp \
--destination 64.192.31.41 --destination-port 2080 \
-j DNAT --to 192.168.1.2:80
with the SNATs above, this connection works:
192.168.1.2 -> 64.192.31.41:2080 -> 192.168.1.2:80
and return:
192.168.1.2 <- 64.192.31.41 <- 192.168.1.2:80
if i only did the SNAT on the external ip, then the forward would only
work when the connection came from the outside.
a connection from the intranet would:
192.168.1.2 -> 64.192.31.41:2080 -> 192.168.1.2:80
and return:
192.168.1.2 <- 192.168.1.2:80
the return path wouldn't match up and thus the packets were just lost.
--
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
@ 2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:18 ` Eicke Friedrich
1 sibling, 2 replies; 44+ messages in thread
From: Martin Josefsson @ 2003-05-29 22:36 UTC (permalink / raw)
To: Gordon Messmer; +Cc: Netfilter-devel
On Thu, 2003-05-29 at 22:41, Gordon Messmer wrote:
> We recently have had trouble with kernel crashes on a Linux 2.4.20 box
> used as a NAT gateway. The machine is running Slackware 8.1 with a
> vanilla 2.4.20 kernel. The kernel configuration is attached. The
> message-log attachment contains the full dmesg output, as captured by a
> remote syslog server, as well as the last messages received before the
> box hung:
>
> May 28 16:18:08 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687fbc4) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
> May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687cd24) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
> May 28 16:18:52 tog-wakko4 kernel: LIST_DELETE: ip_conntrack_core.c:303
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f687ce64) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
>
> What further information would be useful in tracking down this problem?
Beware that conntrack in kernel 2.4.20 has a serious bug caused by core
kernel changes. Can you please try 2.4.21-rc or apply at least
submitted/10_confirm_fix.patch from patch-o-matic and run the same thing
again and see if it still happens?
It appears that as if the reply-tuple is modified after the conntrack
has been added to the hashtable (shouldn't happen). The only place this
modification could happen is in ip_conntrack_alter_reply() which is
called from ip_nat_setup_info() which in turn is called from various
places to set up NAT mappings. But I can't find a place where it's
called for a connection that's already in the hashtable...
And the IP_NF_ASSERT() in ip_conntrack_alter_reply() would have
triggered unless the conntrack had already been deleted from the
lists...
Which modules are you using?
--
/Martin
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2003-05-29 22:36 ` Martin Josefsson
@ 2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
1 sibling, 1 reply; 44+ messages in thread
From: Gordon Messmer @ 2003-05-30 4:23 UTC (permalink / raw)
Cc: Netfilter-devel
Martin Josefsson wrote:
>
> Beware that conntrack in kernel 2.4.20 has a serious bug caused by core
> kernel changes. Can you please try 2.4.21-rc or apply at least
> submitted/10_confirm_fix.patch from patch-o-matic and run the same thing
> again and see if it still happens?
I've suggested the patch to the person responsible for the machine (I'm
just helping him track this down).
> It appears that as if the reply-tuple is modified after the conntrack
> has been added to the hashtable (shouldn't happen). The only place this
> modification could happen is in ip_conntrack_alter_reply() which is
> called from ip_nat_setup_info() which in turn is called from various
> places to set up NAT mappings. But I can't find a place where it's
> called for a connection that's already in the hashtable...
> And the IP_NF_ASSERT() in ip_conntrack_alter_reply() would have
> triggered unless the conntrack had already been deleted from the
> lists...
Possibly memory corruption, then?
>
> Which modules are you using?
>
According to Mark:
lsmod
Module Size Used by Not tainted
ipt_MARK 856 1 (autoclean)
ipt_LOG 3320 1 (autoclean)
ipt_limit 1048 1 (autoclean)
ipt_REJECT 2840 13 (autoclean)
ipt_mark 536 1 (autoclean)
iptable_mangle 2228 1 (autoclean)
ip_nat_ftp 3696 0 (unused)
ip_conntrack_ftp 4240 1 [ip_nat_ftp]
ipt_state 632 0 (unused)
ipt_multiport 728 0 (unused)
ipt_esp 632 0 (unused)
ipt_MASQUERADE 1944 1
iptable_filter 1736 1
iptable_nat 21176 2 [ip_nat_ftp ipt_MASQUERADE]
ip_conntrack 28064 3 [ip_nat_ftp ip_conntrack_ftp ipt_state
ipt_MASQUERADE iptable_nat]
ip_tables 13400 14 [ipt_MARK ipt_LOG ipt_limit ipt_REJECT
ipt_mark iptable_mangle ipt_state
ipt_multiport ipt_esp ipt_MASQUERADE
iptable_filter iptable_nat]
ip_gre 7584 0 (unused)
sk98lin 113136 1
e1000 47980 1
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2003-05-30 4:23 ` Gordon Messmer
@ 2003-05-30 10:53 ` Martin Josefsson
0 siblings, 0 replies; 44+ messages in thread
From: Martin Josefsson @ 2003-05-30 10:53 UTC (permalink / raw)
To: Gordon Messmer; +Cc: Netfilter-devel
On Fri, 2003-05-30 at 06:23, Gordon Messmer wrote:
> Martin Josefsson wrote:
> >
> > Beware that conntrack in kernel 2.4.20 has a serious bug caused by core
> > kernel changes. Can you please try 2.4.21-rc or apply at least
> > submitted/10_confirm_fix.patch from patch-o-matic and run the same thing
> > again and see if it still happens?
>
> I've suggested the patch to the person responsible for the machine (I'm
> just helping him track this down).
Ok.
> Possibly memory corruption, then?
Can very well be a real bug, There have been reports of the same thing
happening to UP machines running 2.4.21-rc kernels (which include the
patch mentioned above, but I still think your friend should apply it)
I'll see if I can cook up some form of debugging-patch for this, it
might help us track it down. Some way of reproducing it wouldn't hurt.
Does he still have the same problem if he removes ip_conntrack_ftp and
ip_nat_ftp ?
> >
> > Which modules are you using?
> >
>
> According to Mark:
>
> lsmod
> Module Size Used by Not tainted
> ipt_MARK 856 1 (autoclean)
> ipt_LOG 3320 1 (autoclean)
> ipt_limit 1048 1 (autoclean)
> ipt_REJECT 2840 13 (autoclean)
> ipt_mark 536 1 (autoclean)
> iptable_mangle 2228 1 (autoclean)
> ip_nat_ftp 3696 0 (unused)
> ip_conntrack_ftp 4240 1 [ip_nat_ftp]
> ipt_state 632 0 (unused)
> ipt_multiport 728 0 (unused)
> ipt_esp 632 0 (unused)
> ipt_MASQUERADE 1944 1
> iptable_filter 1736 1
> iptable_nat 21176 2 [ip_nat_ftp ipt_MASQUERADE]
> ip_conntrack 28064 3 [ip_nat_ftp ip_conntrack_ftp ipt_state
> ipt_MASQUERADE iptable_nat]
> ip_tables 13400 14 [ipt_MARK ipt_LOG ipt_limit ipt_REJECT
> ipt_mark iptable_mangle ipt_state
> ipt_multiport ipt_esp ipt_MASQUERADE
> iptable_filter iptable_nat]
> ip_gre 7584 0 (unused)
> sk98lin 113136 1
> e1000 47980 1
--
/Martin
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
@ 2003-05-30 10:18 ` Eicke Friedrich
1 sibling, 0 replies; 44+ messages in thread
From: Eicke Friedrich @ 2003-05-30 10:18 UTC (permalink / raw)
To: netfilter-devel
Hi all,
Martin Josefsson wrote:
> Beware that conntrack in kernel 2.4.20 has a serious bug caused by core
> kernel changes. Can you please try 2.4.21-rc or apply at least
> submitted/10_confirm_fix.patch from patch-o-matic and run the same thing
> again and see if it still happens?
As I'm using kernel 2.4.20 and conntrack as well, I'm very interessted
in this problem. I've just patched the kernel with 10_confirm_fix but
have no chance to test it under load.
Testing my software in a real-scenario on tuesday, I would be glad to
hear if this patch fixes the problem or if I'm forced to update the
kernel.
Best regards,
Eicke.
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
0 siblings, 1 reply; 44+ messages in thread
From: Pavel Gulchouck @ 2002-06-26 11:02 UTC (permalink / raw)
To: linux-kernel
Hello.
RedHat 7.3, kernel 2.4.18-4, ext3, swap to partition, no SMP.
Any suggestions?
Should I change aufs to ufs in squid, or it's not related to this crash?
Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
Jun 20 04:33:30 gate kernel: invalid operand: 0000
Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32 sch_tbf sch_cbq autofs smbfs ne2k-p
Jun 20 04:33:30 gate kernel: CPU: 0
Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:31 gate kernel: EIP is at iput [kernel] 0x2f (2.4.18-4)
Jun 20 04:33:31 gate kernel: eax: 0000001c ebx: c5d12810 ecx: 00000001 edx: 0020c5f3
Jun 20 04:33:31 gate kernel: esi: c74fd400 edi: 00000000 ebp: 0000004b esp: c11c1f50
Jun 20 04:33:31 gate kernel: ds: 0018 es: 0018 ss: 0018
Jun 20 04:33:31 gate kernel: Process kswapd (pid: 4, stackpage=c11c1000)
Jun 20 04:33:31 gate kernel: Stack: c022bbab 0000042a c009dd78 c009dd60 c5d12810 c0146c66 c5d12810 c11c0000
Jun 20 04:33:31 gate kernel: c012e148 00000000 00000000 ffffffff c02cad78 00000000 000000e8 0000003a
Jun 20 04:33:31 gate kernel: 000001d0 000000e8 00000000 66666667 c0146f84 0000025c c012eb96 00000006
Jun 20 04:33:31 gate kernel: Call Trace: [prune_dcache+262/372] prune_dcache [kernel] 0x106
Jun 20 04:33:31 gate kernel: Call Trace: [<c0146c66>] prune_dcache [kernel] 0x106
Jun 20 04:33:31 gate kernel: [page_launder_zone+1344/1648] page_launder_zone [kernel] 0x540
Jun 20 04:33:31 gate kernel: [<c012e148>] page_launder_zone [kernel] 0x540
Jun 20 04:33:31 gate kernel: [shrink_dcache_memory+32/48] shrink_dcache_memory [kernel] 0x20
Jun 20 04:33:31 gate kernel: [<c0146f84>] shrink_dcache_memory [kernel] 0x20
Jun 20 04:33:31 gate kernel: [do_try_to_free_pages+26/376] do_try_to_free_pages [kernel] 0x1a
Jun 20 04:33:31 gate kernel: [<c012eb96>] do_try_to_free_pages [kernel] 0x1a
Jun 20 04:33:31 gate kernel: [kswapd+248/680] kswapd [kernel] 0xf8
Jun 20 04:33:31 gate kernel: [<c012ee64>] kswapd [kernel] 0xf8
Jun 20 04:33:31 gate kernel: [_stext+0/28] stext [kernel] 0x0
Jun 20 04:33:31 gate kernel: [<c0105000>] stext [kernel] 0x0
Jun 20 04:33:31 gate kernel: [kernel_thread+38/48] kernel_thread [kernel] 0x26
Jun 20 04:33:31 gate kernel: [<c0106e7a>] kernel_thread [kernel] 0x26
Jun 20 04:33:31 gate kernel: [kswapd+0/680] kswapd [kernel] 0x0
Jun 20 04:33:31 gate kernel: [<c012ed6c>] kswapd [kernel] 0x0
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:32 gate kernel: Code: 0f 0b 59 58 85 f6 74 09 8b 46 20 85 c0 74 02 89 c7 85 ff 74
--
Lucky carrier,
Pavel.
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2002-06-26 11:02 Pavel Gulchouck
@ 2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
0 siblings, 1 reply; 44+ messages in thread
From: James Stevenson @ 2002-06-26 19:03 UTC (permalink / raw)
To: gul, linux-kernel
>
> Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
> Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
> Jun 20 04:33:30 gate kernel: invalid operand: 0000
> Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32
sch_tbf sch_cbq autofs smbfs ne2k-p
> Jun 20 04:33:30 gate kernel: CPU: 0
> Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
> Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
> Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
what makes your kernel tainted ?
do you have some binary only drivers ?
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
2002-06-26 19:03 ` James Stevenson
@ 2002-06-27 8:00 ` Pavel Gulchouck
0 siblings, 0 replies; 44+ messages in thread
From: Pavel Gulchouck @ 2002-06-27 8:00 UTC (permalink / raw)
To: James Stevenson; +Cc: linux-kernel
Hi!
On Wed, Jun 26, 2002 at 08:03:20PM +0100, James Stevenson writes:
> > Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
> > Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
> > Jun 20 04:33:30 gate kernel: invalid operand: 0000
> > Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32 sch_tbf sch_cbq autofs smbfs ne2k-p
> > Jun 20 04:33:30 gate kernel: CPU: 0
> > Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
> > Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
> > Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
>
> what makes your kernel tainted ?
It's a question for me.
> do you have some binary only drivers ?
No.
--
Lucky carrier,
Pavel.
^ permalink raw reply [flat|nested] 44+ messages in thread
* RE: kernel crash
@ 2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
0 siblings, 1 reply; 44+ messages in thread
From: Cyrille Ngalle @ 2001-04-12 15:16 UTC (permalink / raw)
To: nak, linux-kernel, linux-arm
Hi all !!
This is just to reinforce the message below.
This crash is ver easy to reproduce.
Use bootldr (with the last patch from Nico) [it also happens with
Redboot]
+
Lunix 2.4.0 + patch rmk2 + diff rmk2-np2
+ a ramdisk.
Once logged in Linux, type these commands :
SHELL> mknod /dev/dsp c 14 3
SHELL> echo foo > /dev/dsp
and there you are => kernel crash
I had a deeper look and this seems to be the scheduler that is not
handling some page stuff properly (I am not a specialist but this is
what I observed).
This has been reported several times in various mailing lists. I haven't
found yet
any patch fixing this.
Is there someone around the place looking at this problem as many people
seem to be waiting
for this fix ???
Thanks again folks,
Cyrille
-----Original Message-----
From: nak@apfbioelectronics.com [mailto:nak@apfbioelectronics.com]
Sent: Sunday, April 01, 2001 12:15 PM
To: linux-kernel@vger.kernel.org; linux-arm@lists.arm.linux.org.uk
Subject: kernel crash
This is a general plea for help .. We were told Linux was the most
stable OS
for embedded work so we put it to use in running our ARM based
pacemaker.
It did well on the preliminary tests using simulated output we managed 3
weeks with no problems and almost perfect rhythm generation.
On the fourth week we began animal testing our product and it did fine
for 5
days 3 hours and 10 minutes.
On Thursday March 22 at 0419 hrs a software crash caused a malfunction
in
the pacemaker resulting in a large discharge of current, defibrilating
the
heart and forcing it into an angonal rhythm from which we were unable to
cardiovert.
On top of that, the catastrophic failure means we will be unable to
begin
human testing of our product until early 2003.
One of our techs managed to retrieve something he called an "oops"? from
the
monitor and I've enclosed it below. If anyone can help us with this
please
get back to me. We need to fix this as soon as possible so we can make
final
product release as early as possible.
sincerely,
Dr. Nakasumo
Cardiac Products Dept.
APF Bioelectronics
Unable to handle kernel paging request at virtual address ea0032fb
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c0021124>] lr : [<c0021450>]
sp : c8785c98 ip : a0000013 fp : c8785cd0
r10: 01000000 r9 : 00000003 r8 : c8785cf8
r7 : 00000003 r6 : 00003240 r5 : e7933000 r4 : ea0032fb
r3 : 00000001 r2 : 01000000 r1 : c016209c r0 : ea0032fb
Flags: nzcv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
Stack:
c8785c80: c0021450 c0021124 00000013 ffffffff
00000000 00000
000
c8785ca0: 00000000 00000004 ffffffff ea0032fb c8785cf8 c0121cf4
00000003 a0000
013
c8785cc0: 00000000 c8785cf4 c8785cd4 c0021450 c0020e44 ffffffff
c8785d2c c9000
000
c8785ce0: c8785e28 00000005 c8785d4c c8785cf8 c001ab20 c0021390
00003240 00000
000
c8785d00: ea0032fb ea0000bb ffffffff c8784000 c9000000 c8785e28
00000005 00000
000
c8785d20: 00000000 c8785d4c c0374821 c8785d40 c0020d00 c0020afc
a0000013 fffff
fff
c8785d40: c8785e00 c8785d50 c0020d00 c0020ad0 00000000 00000000
00000000 00000
000
c8785d60: 00000000 00000000 00000000 c8784000 00000000 00000001
c8785da4 c8785
d88
c8785d80: c0036390 c0036260 40000013 fa000000 c8785e0c fa000014
c8785dbc c8785
da8
c8785da0: c00367e4 c0036368 40000013 fa000000 c8785ddc c8785dc0
c001aa08 c0036
7c0
c8785dc0: 00000000 0000001a 00000000 c01893b0 c8785e08 c8785de0
ffffffff c9000
000
c8785de0: c8785e28 c0121d0c 00000005 20000013 00800080 c8785e24
c8785e04 c0021
450
c8785e00: c0020b2c ffffffff c8785e5c 00000000 00000000 ffffffff
c8785e94 c8785
e28
c8785e20: c001ab20 c0021390 c9000000 e8040020 0003ffe0 00000000
00000000 00000
000
c8785e40: 00000000 00000000 ffffffff ffffffff 00800080 c8785e94
ffffffff c8785
e70
c8785e60: c00bf190 c011a7c0 20000013 ffffffff 00040000 00040000
c9000000 00040
000
c8785e80: 00000000 c8036504 c8785eb0 c8785e98 c00bf190 c011a78c
c0189c60 c8036
4c0
c8785ea0: c015ddf0 c8785f28 c8785eb4 c00bc964 c00bf168 c8784000
c8036504 c8784
000
c8785ec0: 0000090d 00000000 00040000 00000000 00040000 00000000
c80364c0 00040
000
c8785ee0: 00000000 c8784000 00000000 00000000 00000000 c8784000
00000000 00000
000
c8785f00: 00040000 00000000 00000000 00000000 00040000 c9000000
c8785f78 c8785
f5c
c8785f20: c8785f2c c00b9ed4 c00bc0e4 c8785f78 c9000000 c01cf428
c01cf420 00001
000
c8785f40: 00000000 00040000 00000000 00000000 c8785fa4 c8785f60
c00bf588 c00b9
e1c
c8785f60: c8785f78 c9000000 00040000 c01db160 c0350000 00001000
00000000 c01cf
428
c8785f80: c02d0660 00000008 c018e158 c015de90 6901b116 c015de78
c8785fc4 c8785
fa8
c8785fa0: c00bfcd4 c00bf414 00000000 c8784000 c8785fc8 c018e158
c8785ffc c8785
fc8
c8785fc0: c00bfee4 c00bfba8 00000000 c8784000 c015de94 c015de94
00000000 c0187
160
c8785fe0: c0187120 c0188ba4 c018c494 c0014c34 00000000 c8786000
c001c620 c00bf
d8c
Backtrace:
Function entered at [<c0020e38>] from [<c0021450>] do_alignment
Function entered at [<c0021384>] from [<c001ab20>] do_data_abort
r8 = 00000005 r7 = C8785E28 r6 = C9000000 r5 = C8785D2C
r4 = FFFFFFFF
Function entered at [<c0020ac4>] from [<c0020d00>] __do_vmalloc_fault
Function entered at [<c0020b20>] from [<c0021450>] __do_page_fault
Function entered at [<c0021384>] from [<c001ab20>] do_DataAbort
r8 = FFFFFFFF r7 = 00000000 r6 = 00000000 r5 = C8785E5C
r4 = FFFFFFFF
Function entered at [<c011a780>] from [<c00bf190>] memcpy
r9 = C8036504 r8 = 00000000 r7 = 00040000 r6 = C9000000
r5 = 00040000 r4 = 00040000
Function entered at [<c00bf15c>] from [<c00bc964>] sa1100_copy_from
r6 = C015DDF0 r5 = C80364C0 r4 = C0189C60
Function entered at [<c00bc0d8>] from [<c00b9ed4>] cfi_intelext_read
Function entered at [<c00b9e10>] from [<c00bf588>] part_read
Function entered at [<c00bf408>] from [<c00bfcd4>] do_cached_write
Function entered at [<c00bfb9c>] from [<c00bfee4>]
handle_mtdblock_request
r7 = C018E158 r6 = C8785FC8 r5 = C8784000 r4 = 00000000
Function entered at [<c00bfd80>] from [<c001c620>] mtdblock_thread
Aiee, killing interrupt handler
Scheduling in interrupt
kernel BUG at sched.c:698!
Unable to handle kernel NULL pointer dereference at virtual address
00000000
pgd = c0004000
*pgd = c01a0001, *pmd = c01a0001, *pte = c000308b, *ppte = c000300a
Internal error: Oops: 0
CPU: 0
pc : [<c001fdc8>] lr : [<c002e0ac>]
sp : c8785b08 ip : c8785ac4 fp : c8785b18
r10: 00000000 r9 : c0189c60 r8 : 00000000
r7 : 0000000b r6 : c8784000 r5 : c8784000 r4 : 00000000
r3 : 00000000 r2 : c0154ea8 r1 : 00000000 r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2001-04-12 15:16 Cyrille Ngalle
@ 2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
0 siblings, 1 reply; 44+ messages in thread
From: Russell King @ 2001-04-12 15:31 UTC (permalink / raw)
To: Cyrille Ngalle; +Cc: nak, linux-kernel, linux-arm
On Thu, Apr 12, 2001 at 05:16:33PM +0200, Cyrille Ngalle wrote:
> This is just to reinforce the message below.
And why is it of interest to LKML? I can think if no one here who'd
be interested in it.
> This crash is ver easy to reproduce.
>
> Use bootldr (with the last patch from Nico) [it also happens with
> Redboot]
It is not a function of the bootloader, this is irrelevent.
Also, I believe that the original posters message was an April Fool's
joke (was posted on the 1st April to the linux-arm lists).
However, the problem it describes is not, and I do have a fix in my
tree, but the delta between my last patch and my current tree is one
line, which hardly seems worth putting out a new ARM patch.
--- linux.rel/arch/arm/mm/fault-armv.c Fri Apr 6 19:09:05 2001
+++ linux/arch/arm/mm/fault-armv.c Thu Apr 12 16:30:25 2001
@@ -490,7 +490,7 @@
bad_or_fault:
if (type == TYPE_ERROR)
goto bad;
-
+ regs->ARM_pc -= 4;
/*
* We got a fault - fix it up, or die.
*/
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 44+ messages in thread* Re: kernel crash
2001-04-12 15:31 ` Russell King
@ 2001-04-13 13:16 ` nak
0 siblings, 0 replies; 44+ messages in thread
From: nak @ 2001-04-13 13:16 UTC (permalink / raw)
To: Russell King; +Cc: Cyrille Ngalle, linux-kernel, linux-arm
Ok, I see this has started to interfere with the bug tracking process so
I'll kill it now (I seriously thought it was already dead).
Yep it was an april fools joke.
for the record:
2 offers for help;
1 post asking me if I mounted a scratch monkey( heh);
1 email begging me to abandon the project for the sake of humanity (and
linux' reputation)
And this adds 1 attempt to use it as corroborating evidence. Who knows, it
might have even been this guy's post I ripped the oops from.
On Thu, 12 Apr 2001, Russell King wrote:
> On Thu, Apr 12, 2001 at 05:16:33PM +0200, Cyrille Ngalle wrote:
> > This is just to reinforce the message below.
>
> And why is it of interest to LKML? I can think if no one here who'd
> be interested in it.
>
> > This crash is ver easy to reproduce.
> >
> > Use bootldr (with the last patch from Nico) [it also happens with
> > Redboot]
>
> It is not a function of the bootloader, this is irrelevent.
>
> Also, I believe that the original posters message was an April Fool's
> joke (was posted on the 1st April to the linux-arm lists).
>
> However, the problem it describes is not, and I do have a fix in my
> tree, but the delta between my last patch and my current tree is one
> line, which hardly seems worth putting out a new ARM patch.
>
> --- linux.rel/arch/arm/mm/fault-armv.c Fri Apr 6 19:09:05 2001
> +++ linux/arch/arm/mm/fault-armv.c Thu Apr 12 16:30:25 2001
> @@ -490,7 +490,7 @@
> bad_or_fault:
> if (type == TYPE_ERROR)
> goto bad;
> -
> + regs->ARM_pc -= 4;
> /*
> * We got a fault - fix it up, or die.
> */
>
>
> --
> Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
> http://www.arm.linux.org.uk/personal/aboutme.html
>
^ permalink raw reply [flat|nested] 44+ messages in thread
* Re: kernel crash
@ 2001-04-02 16:40 Wayne.Brown
0 siblings, 0 replies; 44+ messages in thread
From: Wayne.Brown @ 2001-04-02 16:40 UTC (permalink / raw)
To: nak; +Cc: linux-kernel, linux-arm
I hope you were using a scratch monkey...
^ permalink raw reply [flat|nested] 44+ messages in thread
* kernel crash
@ 2001-04-01 10:15 nak
0 siblings, 0 replies; 44+ messages in thread
From: nak @ 2001-04-01 10:15 UTC (permalink / raw)
To: linux-kernel, linux-arm
This is a general plea for help .. We were told Linux was the most stable OS
for embedded work so we put it to use in running our ARM based pacemaker.
It did well on the preliminary tests using simulated output we managed 3
weeks with no problems and almost perfect rhythm generation.
On the fourth week we began animal testing our product and it did fine for 5
days 3 hours and 10 minutes.
On Thursday March 22 at 0419 hrs a software crash caused a malfunction in
the pacemaker resulting in a large discharge of current, defibrilating the
heart and forcing it into an angonal rhythm from which we were unable to
cardiovert.
On top of that, the catastrophic failure means we will be unable to begin
human testing of our product until early 2003.
One of our techs managed to retrieve something he called an "oops"? from the
monitor and I've enclosed it below. If anyone can help us with this please
get back to me. We need to fix this as soon as possible so we can make final
product release as early as possible.
sincerely,
Dr. Nakasumo
Cardiac Products Dept.
APF Bioelectronics
Unable to handle kernel paging request at virtual address ea0032fb
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c0021124>] lr : [<c0021450>]
sp : c8785c98 ip : a0000013 fp : c8785cd0
r10: 01000000 r9 : 00000003 r8 : c8785cf8
r7 : 00000003 r6 : 00003240 r5 : e7933000 r4 : ea0032fb
r3 : 00000001 r2 : 01000000 r1 : c016209c r0 : ea0032fb
Flags: nzcv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
Stack:
c8785c80: c0021450 c0021124 00000013 ffffffff 00000000 00000
000
c8785ca0: 00000000 00000004 ffffffff ea0032fb c8785cf8 c0121cf4 00000003 a0000
013
c8785cc0: 00000000 c8785cf4 c8785cd4 c0021450 c0020e44 ffffffff c8785d2c c9000
000
c8785ce0: c8785e28 00000005 c8785d4c c8785cf8 c001ab20 c0021390 00003240 00000
000
c8785d00: ea0032fb ea0000bb ffffffff c8784000 c9000000 c8785e28 00000005 00000
000
c8785d20: 00000000 c8785d4c c0374821 c8785d40 c0020d00 c0020afc a0000013 fffff
fff
c8785d40: c8785e00 c8785d50 c0020d00 c0020ad0 00000000 00000000 00000000 00000
000
c8785d60: 00000000 00000000 00000000 c8784000 00000000 00000001 c8785da4 c8785
d88
c8785d80: c0036390 c0036260 40000013 fa000000 c8785e0c fa000014 c8785dbc c8785
da8
c8785da0: c00367e4 c0036368 40000013 fa000000 c8785ddc c8785dc0 c001aa08 c0036
7c0
c8785dc0: 00000000 0000001a 00000000 c01893b0 c8785e08 c8785de0 ffffffff c9000
000
c8785de0: c8785e28 c0121d0c 00000005 20000013 00800080 c8785e24 c8785e04 c0021
450
c8785e00: c0020b2c ffffffff c8785e5c 00000000 00000000 ffffffff c8785e94 c8785
e28
c8785e20: c001ab20 c0021390 c9000000 e8040020 0003ffe0 00000000 00000000 00000
000
c8785e40: 00000000 00000000 ffffffff ffffffff 00800080 c8785e94 ffffffff c8785
e70
c8785e60: c00bf190 c011a7c0 20000013 ffffffff 00040000 00040000 c9000000 00040
000
c8785e80: 00000000 c8036504 c8785eb0 c8785e98 c00bf190 c011a78c c0189c60 c8036
4c0
c8785ea0: c015ddf0 c8785f28 c8785eb4 c00bc964 c00bf168 c8784000 c8036504 c8784
000
c8785ec0: 0000090d 00000000 00040000 00000000 00040000 00000000 c80364c0 00040
000
c8785ee0: 00000000 c8784000 00000000 00000000 00000000 c8784000 00000000 00000
000
c8785f00: 00040000 00000000 00000000 00000000 00040000 c9000000 c8785f78 c8785
f5c
c8785f20: c8785f2c c00b9ed4 c00bc0e4 c8785f78 c9000000 c01cf428 c01cf420 00001
000
c8785f40: 00000000 00040000 00000000 00000000 c8785fa4 c8785f60 c00bf588 c00b9
e1c
c8785f60: c8785f78 c9000000 00040000 c01db160 c0350000 00001000 00000000 c01cf
428
c8785f80: c02d0660 00000008 c018e158 c015de90 6901b116 c015de78 c8785fc4 c8785
fa8
c8785fa0: c00bfcd4 c00bf414 00000000 c8784000 c8785fc8 c018e158 c8785ffc c8785
fc8
c8785fc0: c00bfee4 c00bfba8 00000000 c8784000 c015de94 c015de94 00000000 c0187
160
c8785fe0: c0187120 c0188ba4 c018c494 c0014c34 00000000 c8786000 c001c620 c00bf
d8c
Backtrace:
Function entered at [<c0020e38>] from [<c0021450>] do_alignment
Function entered at [<c0021384>] from [<c001ab20>] do_data_abort
r8 = 00000005 r7 = C8785E28 r6 = C9000000 r5 = C8785D2C
r4 = FFFFFFFF
Function entered at [<c0020ac4>] from [<c0020d00>] __do_vmalloc_fault
Function entered at [<c0020b20>] from [<c0021450>] __do_page_fault
Function entered at [<c0021384>] from [<c001ab20>] do_DataAbort
r8 = FFFFFFFF r7 = 00000000 r6 = 00000000 r5 = C8785E5C
r4 = FFFFFFFF
Function entered at [<c011a780>] from [<c00bf190>] memcpy
r9 = C8036504 r8 = 00000000 r7 = 00040000 r6 = C9000000
r5 = 00040000 r4 = 00040000
Function entered at [<c00bf15c>] from [<c00bc964>] sa1100_copy_from
r6 = C015DDF0 r5 = C80364C0 r4 = C0189C60
Function entered at [<c00bc0d8>] from [<c00b9ed4>] cfi_intelext_read
Function entered at [<c00b9e10>] from [<c00bf588>] part_read
Function entered at [<c00bf408>] from [<c00bfcd4>] do_cached_write
Function entered at [<c00bfb9c>] from [<c00bfee4>] handle_mtdblock_request
r7 = C018E158 r6 = C8785FC8 r5 = C8784000 r4 = 00000000
Function entered at [<c00bfd80>] from [<c001c620>] mtdblock_thread
Aiee, killing interrupt handler
Scheduling in interrupt
kernel BUG at sched.c:698!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
*pgd = c01a0001, *pmd = c01a0001, *pte = c000308b, *ppte = c000300a
Internal error: Oops: 0
CPU: 0
pc : [<c001fdc8>] lr : [<c002e0ac>]
sp : c8785b08 ip : c8785ac4 fp : c8785b18
r10: 00000000 r9 : c0189c60 r8 : 00000000
r7 : 0000000b r6 : c8784000 r5 : c8784000 r4 : 00000000
r3 : 00000000 r2 : c0154ea8 r1 : 00000000 r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
^ permalink raw reply [flat|nested] 44+ messages in thread
end of thread, other threads:[~2014-01-16 10:25 UTC | newest]
Thread overview: 44+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-29 10:32 kernel crash fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2012-05-30 17:35 Kernel crash Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
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.