On Mon, 2003-07-14 at 19:01, Sythos wrote:
> Nessun altro kamikaze che abbia voglia di scambiare opinioni su questo
> kernel iperevoluto di cui tutti parlano da tanto tempo?
yes, me!
dopo varie peripezie gia' note (esempio: il kernel si installa ma non
crea le device per l'alsa) mi trovo con un sistema perfettamente
funzionante, tranne che:
1) l'orologio rimane indietro.. parecchio, anche se ho l'ntpd in
funzione
2) "modprobe sbp2" (ho il masterizzatore su firewire) da questo
simpatico output:
---------------------------------------dmesg-----------------
ieee1394: sbp2: Logged into SBP-2 device
arch/i386/kernel/semaphore.c:84: spin_is_locked on uninitialized
spinlock cdf8e898.
Unable to handle kernel paging request at virtual address 6b6b6b6b
printing eip:
c02c0eb7
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c02c0eb7>] Not tainted
EFLAGS: 00010097
EIP is at vsnprintf+0x2e7/0x440
eax: 6b6b6b6b ebx: 0000000a ecx: 6b6b6b6b edx: fffffffe
esi: c06237cb edi: 00000000 ebp: cde6fd74 esp: cde6fd3c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 208, threadinfo=cde6e000 task=cde91000)
Stack: c06237bd c0623b9f 00000054 00000000 0000000a ffffffff 00000001
00000002
ffffffff ffffffff c0623b9f c06237a0 00000046 c04e9909 cde6fdc4
c01290ab
c06237a0 00000400 c04e28b2 cde6fddc 00000082 cdf8e860 00000004
cdf8e868
Call Trace:
[<c01290ab>] printk+0x16b/0x3f0
[<d17ca458>] dma_trm_flush+0x128/0x180 [ohci1394]
[<c010a2ff>] __down+0x1ef/0x360
[<c01220d0>] default_wake_function+0x0/0x30
[<d178b0f8>] sbp2util_allocate_write_packet+0x68/0x80 [sbp2]
[<c010a977>] __down_failed+0xb/0x14
[<d178f361>] .text.lock.sbp2+0x5/0x34 [sbp2]
[<d178c710>] sbp2_start_device+0x200/0x3f0 [sbp2]
[<d178c4c5>] sbp2_start_ud+0x105/0x150 [sbp2]
[<d178bf82>] sbp2_probe+0x32/0x40 [sbp2]
[<c0353c33>] bus_match+0x43/0x80
[<c0353d5d>] driver_attach+0x5d/0x70
[<c0354055>] bus_add_driver+0xa5/0xc0
[<c0354528>] driver_register+0x88/0x90
[<d1815837>] hpsb_register_protocol+0x17/0x30 [ieee1394]
[<d178f330>] sbp2_module_init+0xa0/0xcc [sbp2]
[<c014a185>] sys_init_module+0x205/0x3e0
[<c010c28b>] syscall_call+0x7/0xb
Code: 80 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 83 e7 10 89 c3 75
<6>note: modprobe[208] exited with preempt_count 2
bad: scheduling while atomic!
Call Trace:
[<c0122071>] schedule+0x6e1/0x6f0
e100: eth0 NIC Link is Up 100 Mbps Full duplex
[<c0160e1e>] unmap_page_range+0x4e/0x80
[<c016104e>] unmap_vmas+0x1fe/0x360
[<c0166ae9>] exit_mmap+0xc9/0x2c0
[<c0125643>] mmput+0xb3/0x140
[<c012bb13>] do_exit+0x283/0xac0
[<c010d46c>] die+0x21c/0x220
[<c011f8fd>] do_page_fault+0x15d/0x4dc
[<c0329ccb>] clear_selection+0x1b/0x60
[<c0330f2b>] poke_blanked_console+0x6b/0x80
[<c011f7a0>] do_page_fault+0x0/0x4dc
[<c010cc95>] error_code+0x2d/0x38
[<c02c0eb7>] vsnprintf+0x2e7/0x440
[<c01290ab>] printk+0x16b/0x3f0
[<d17ca458>] dma_trm_flush+0x128/0x180 [ohci1394]
[<c010a2ff>] __down+0x1ef/0x360
[<c01220d0>] default_wake_function+0x0/0x30
[<d178b0f8>] sbp2util_allocate_write_packet+0x68/0x80 [sbp2]
[<c010a977>] __down_failed+0xb/0x14
[<d178f361>] .text.lock.sbp2+0x5/0x34 [sbp2]
[<d178c710>] sbp2_start_device+0x200/0x3f0 [sbp2]
[<d178c4c5>] sbp2_start_ud+0x105/0x150 [sbp2]
[<d178bf82>] sbp2_probe+0x32/0x40 [sbp2]
[<c0353c33>] bus_match+0x43/0x80
[<c0353d5d>] driver_attach+0x5d/0x70
[<c0354055>] bus_add_driver+0xa5/0xc0
[<c0354528>] driver_register+0x88/0x90
[<d1815837>] hpsb_register_protocol+0x17/0x30 [ieee1394]
[<d178f330>] sbp2_module_init+0xa0/0xcc [sbp2]
[<c014a185>] sys_init_module+0x205/0x3e0
[<c010c28b>] syscall_call+0x7/0xb
Slab corruption: start=cdf8e860, expend=cdf8e8d7, problemat=cdf8e8a0
Last user: [<d180d21c>](free_hpsb_packet+0x2c/0x40 [ieee1394])
Data: ****************************************************************6A
******************************************************A5
Next: 71 F0 2C .1C D2 80 D1 71 F0 2C .....................
slab error in check_poison_obj(): cache `hpsb_packet': object was
modified after freeing
Call Trace:
[<c015687b>] check_poison_obj+0x17b/0x1d0
[<c01589eb>] kmem_cache_alloc+0x8b/0x1c0
[<d180d0f1>] alloc_hpsb_packet+0x21/0x120 [ieee1394]
[<d180d0f1>] alloc_hpsb_packet+0x21/0x120 [ieee1394]
[<d180fdb4>] hpsb_make_readpacket+0x44/0xe0 [ieee1394]
[<d1810257>] hpsb_read+0x57/0x150 [ieee1394]
[<d181460b>] nodemgr_read_quadlet+0x5b/0xa0 [ieee1394]
[<d1815b2e>] read_businfo_block+0x4e/0x1a0 [ieee1394]
[<d1815cba>] nodemgr_node_probe_one+0x3a/0xf0 [ieee1394]
[<c01222f2>] __wake_up_locked+0x22/0x30
[<d1815ec1>] nodemgr_node_probe+0x111/0x120 [ieee1394]
[<d18161f8>] nodemgr_host_thread+0x148/0x190 [ieee1394]
[<d18160b0>] nodemgr_host_thread+0x0/0x190 [ieee1394]
[<c0109389>] kernel_thread_helper+0x5/0xc
---------------------------------------/dmesg----------------
allegria! :o)
3) ogni "qualche secondo" in dmesg appare questo altro allegro
avvertimento:
----------------------------------------dmesg----------------
atkbd.c: Unknown key (set 2, scancode 0x93, on isa0060/serio0) pressed.
atkbd.c: Unknown key (set 2, scancode 0x98, on isa0060/serio0) pressed.
atkbd.c: Unknown key (set 2, scancode 0x93, on isa0060/serio0) pressed.
atkbd.c: Unknown key (set 2, scancode 0xb2, on isa0060/serio0) pressed.
---------------------------------------/dmesg----------------
e il codice marcato come "scancode" cambia quasi ogni volta..
questi sono i tre problemi che non sono riuscito a fixare.. per il resto
funziona egregiamente..
PS: il mouse con la kernel-preemption risulta un po' troppo veloce..
--
Francesco -checco- Gigli <spaghetti@xxxxxxxxx>
|