Re: [Bugme-new] [Bug 8561] New: list_add corruption. prev->next should be next (f7d28794), but was f0df8ed4

Paulo Pereira <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
A Friday 01 June 2007 16:52:16, Andrew Morton escreveu:
> On Fri, 1 Jun 2007 04:17:01 -0700 [email protected] wrote:
>
>
> (Please folow up via emailed reply-to-all, not via the bugzilla web
> interface)
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=8561
> >
> >            Summary: list_add corruption. prev->next should be next
> >                     (f7d28794), but was f0df8ed4
> >                     (prev=f0df8ed4)
> >     Kernel Version: vanilla kernel 2.6.22-rc3 (and I try'ed with
> > 2.6.21-fc7 fedora
> >             Status: NEW
> >           Severity: high
> >              Owner: [email protected]
> >          Submitter: [email protected]
> >
> >
> > Most recent kernel where this bug did *NOT* occur: vanilla kernel
> > 2.6.22-rc3
>
> No, this question is asking what is the most recent kernel versions which
> *did not* have this bug?
>
> > Distribution:2.6.22-rc3
> > Hardware Environment:AMD ATHLON X2 4200+, M2V MOTHERBOARD
> > Software Environment:AMULE
> > Problem Description:
> >
> > I'm using vanilla kernel 2.6.22-rc3 (and I try'ed with 2.6.21-fc7 fedora
> > kernel) with a huawei e220 3g, and when I open amule after sometime
> > kernel panics:
> > _
> > list_add corruption. prev->next should be next (f7d28794), but was
> > f0df8ed4 (prev=f0df8ed4)
> > Kernel Bug at lib/list_debug.c:33
> > SMP
> > Modules linhed in: ppp_deflate zlib_deflate ppp_async crc_ccitt
> > pp_generic slhc sata_mv autofs4 hipd rfconn 12cap bluetooth sunrpc
> > nf_conntrack_netbios_ns
> > ipt_REJECT nf_conntrack_ipv4 xt_satte nf_conntrack nfnetlink
> > iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables
> > x_tables vfat fat fuse dm_mirror dm_multipatch dm_mod video sbs button
> > dock battery ac radeon drm ipv6 lp option usbserial snd_emv10k1_synth
> > snd_emux_synth snd_seq_virmidi snd_seq_midi_emulbt878 tuner snd_emu10k1
> > msp3400 snd_rawmidi bttv snd_hda_intell snd_ac97_codec ac97_bus
> > snd_seq_dummy video_buf snd_seq_oss ir_common compat_isctl32 i2c_algo_bit
> > snd_seq_midi_event sg btcx_risc snd_seq floppy snd_pcm_oss snd_mixer_oss
> > snd_pcm snd_seq_device snd_timer pata_via tveeprom i2c_viapro
> > snd_util_mem i2c_core snd_page_alloc snd_hwdep snd videodev atl1
> > v4l2_common soundcore mii v4l1_compat emu10k1_gp sr_mod gameport k8temp
> > hwmon parport_pc parport cdrom serio_raw usb_storage sata_via ata_generic
> > libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
> > CPU: 0
> > EIP: 0060:[<c04ddda5>] Not tainted VLI
> > EFLAGS: 00010092 (2.6.22_rc3 #1)
> > EIP is at __list_add+0x48/0x5c
> > eax: 00000061___ebx: f0df8ed4___ecx: c06ced10___edx:00000086
> > esi: f0df8ed4___edi: 00000246___ebp: f7d28788___esp: c0750e68
> > ds: 007b________es: 007b________fs: 00d8________gs: 0033________ss: 0068
> > Process Amule (pid: 9719, ti=c0750000 task=d1da38b0 task.ti=c7899000)
> > Satck:
> > _co69461e________f7d28794________f0df8ed4________f0df8ed4________f0df8ec0
> >________ffffffff________c0558f09________ 00000040
> > ________00000021________f9316564________c180a120________00000000________d
> >4884800________00000020________f7ece200________000000fc
> > ________f7a45000________db1c8000________00000001________00000040________f
> >90b8da0________f7a45000________d3740000________c409e470 Call Trace:
> > ________[<c0558f09>] usb_hcd_sumit_urb+0x9a/0x778
> > ________[<f9316564>] ppp_async_push+0x38c/0x398 [ppp_async]
> > ________[<f931657d>] ppp_async_send+0xd/0x36 [ppp_async]
> > ________[<f932d677>] ppp_push+0x67/0x4c1 [ppp_generic]
> > ________[<f9316564>] ppp_async_push+0x38c/0x398 [ppp_async]
> > ________[<c043abdc>] timer_stats_update_stats+0x141/0x14d
> > ________[<f90b73c6>] option_write+0xa1/0xe9 [option]
> > ________[<f90ad586>] serial_write+0x9c/0xab [usbserial]
> > ________[<f931627e>] ppp_async_push+0xa6/0x398 [ppp_async]
> > ________[<f9316a31>] ppp_async_process+0x42/0x56 [ppp_async]
> > ________[<c0427990>] tasklet_action+0x46/0x90
> > ________[<c04278c3>] __do_softirq+0x5d/0xc1
> > ________[<c0406cdb>] do_softirq+0x59/0xa8
> > ________[<c0427772>] irq_exit+0x38/0x6b
> > ________[<c0416c60>] smp_apic_timer_interrupt+0x74/0x80
> > ________[<c04057e8>] apic_timer_interrupt+0x28/0x30
> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> > Code:
> > ________ce______45______69______c0______e8______3d______5c______f4______f
> >f______0f______0b______eb______fe______8b______32______39______ce______74
> > ________1c______89______54______24______0c______89______74______24______0
> >8______89______4c______24______04______c7______04______24______1e______46
> > ________69______c0______e8______1b______5c______f4______ff______<0f>____0
> >b______eb______fe______89______59______04______89______0b______89______43
> > ________04______89______18______83______c4______10______5b______5e______c
> >3______8b EIP: [<c04ddda5>] __list_add+0x48/0x5c__SS:ESP 0068:c0750e68
> > Kernel panic - not syncing: Fatal exception in interrupt
>
> Could be a ppp bug, more likely a USB bug, but that's a well-tested code
> path.
>
> Greg? Anyone?  ANy idea where to start looking?
>
> Paolo, I assume this crash is repeatable?

I don't have a kernel versions which *did not* have this bug, because this is 
my first one.

And yes this crash is repeatable, always that I put Amule or Ktorrent to work, 
30/45 minutes later is a kernel panic...

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.