Alexey Serov wrote: > Hi All, > > I had a working CAN setup with ECAN527 PC/104 Card, but recently this > configuration stopped working. > > It was running on Ubuntu 9.04 with kernel 2.6.28. I've just upgraded it to > Ubuntu 9.10 with 2.6.31 kernel (and most recent socket-can snapshot from > SVN), but with no results. > > I'm getting some strange traceback in /var/log/messages when trying to send > something to CAN network (e.g., "cansend can0 080#"). > > Here is a cut from dmesg: > > [ 690.702419] can: raw protocol (rev 20090105) > [ 934.096116] ------------[ cut here ]------------ > [ 934.096177] WARNING: at > /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 > dev_watchdog+0x1f6/0x210() > [ 934.096207] NETDEV WATCHDOG: can0 (): transmit queue 0 timed out > [ 934.096225] Modules linked in: can_raw can i82527_iomem vcan snd_via82xx > gameport snd_ac97_codec ac97_bus snd_pcm snd_timer iptable_filter ip_tables > snd_page_alloc snd_mpu401_uart snd_rawmidi x_tables snd_seq_device ppdev > shpchp snd lp via686a soundcore parport_pc via_agp agpgart i2c_viapro > parport 8139too 8139cp mii > [ 934.096434] Pid: 0, comm: swapper Not tainted 2.6.31-15-generic > #50-Ubuntu > [ 934.096457] Call Trace: > [ 934.096515] [<c014518d>] warn_slowpath_common+0x6d/0xa0 > [ 934.096546] [<c04b0dd6>] ? dev_watchdog+0x1f6/0x210 > [ 934.096574] [<c04b0dd6>] ? dev_watchdog+0x1f6/0x210 > [ 934.096608] [<c0145206>] warn_slowpath_fmt+0x26/0x30 > [ 934.096637] [<c04b0dd6>] dev_watchdog+0x1f6/0x210 > [ 934.096676] [<c0161dab>] ? sched_clock_cpu+0xeb/0x1a0 > [ 934.096709] [<c013bcf1>] ? scheduler_tick+0x101/0x240 > [ 934.096743] [<c01501b7>] run_timer_softirq+0x117/0x200 > [ 934.096772] [<c04b0be0>] ? dev_watchdog+0x0/0x210 > [ 934.096818] [<c014b3b0>] __do_softirq+0x90/0x1a0 > [ 934.096860] [<c0127c38>] ? default_spin_lock_flags+0x8/0x10 > [ 934.096898] [<c0570dca>] ? _spin_lock_irqsave+0x2a/0x40 > [ 934.096946] [<c0106b92>] ? enable_8259A_irq+0x42/0x60 > [ 934.096978] [<c014b4fd>] do_softirq+0x3d/0x40 > [ 934.097007] [<c014b63d>] irq_exit+0x5d/0x70 > [ 934.097036] [<c0104f10>] do_IRQ+0x50/0xc0 > [ 934.097069] [<c01039b0>] common_interrupt+0x30/0x40 > [ 934.097100] [<c0126fc5>] ? native_safe_halt+0x5/0x10 > [ 934.097132] [<c010a486>] default_idle+0x46/0xd0 > [ 934.097162] [<c010202c>] cpu_idle+0x8c/0xd0 > [ 934.097211] [<c055ee85>] rest_init+0x55/0x60 > [ 934.097263] [<c078e8cd>] start_kernel+0x2e6/0x2ec > [ 934.097295] [<c078e406>] ? unknown_bootoption+0x0/0x1ab > [ 934.097331] [<c078e07c>] i386_start_kernel+0x7c/0x83 > [ 934.097354] ---[ end trace ffe46399f3049559 ]--- > [ 934.097709] can0: i82527: using msg object 15 for SFF receiption.
This message shows up once when the TX timeout triggers, which happens if the message does not go out. > Here is my config in /etc/modprobe.d/llcf file: > > alias net-pf-29 can > alias can-proto-1 can-raw > alias can-proto-2 can-bcm > alias can-proto-3 can-tp16 > alias can-proto-4 can-tp20 > alias can-proto-5 can-mcnet > alias can-proto-6 can-isotp > alias can-proto-7 can-bap > > alias can0 i82527-iomem > alias can1 i82527-iomem > options i82527-iomem irq=4,6 base=0xD0000,0xD0100 speed=125,125 clk=8000000 > irq_mode=2 force_dmc=1 debug=1 > > Can this be software problem or there is really something bad with my CAN > hardware? I suspect electrical problems with your bus e.g. not connected, bus termination or improper bit-timing. Anyway, if you have a chance, please switch tot the new cc770/i82527 driver, which is fully compatible with the Socket-CAN interface available in mainline. Wolfgang. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
