Re: [Bugme-new] [Bug 8249] New: NMI watchdog detected LOCKUP when plugging USB devices with acpi=off

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

 



On 21/03/07 at 08:41 -0800, Andrew Morton wrote:
> On Wed, 21 Mar 2007 07:18:45 -0700 bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=8249
> > 
> >            Summary: NMI watchdog detected LOCKUP when plugging USB devices
> >                     with acpi=off
> >     Kernel Version: 2.6.21-rc4
> >             Status: NEW
> >           Severity: high
> >              Owner: greg@xxxxxxxxx
> >          Submitter: lucas@xxxxxxxxxxxxxxxxxx
> > 
> > 
> > Most recent kernel where this bug did *NOT* occur: none, as far as I know
> > Problem Description:
> > 
> > My kernel is running with acpi=off to workaround another bug. When I turn on my
> > USB printer (a Canon PIXMA MP750), I get this on the serial console:
> > 
> > usb 1-1: new full speed USB device using ohci_hcd and address 2
> > usb 1-1: configuration #1 chosen from 1 choice
> > BUG: NMI Watchdog detected LOCKUP on CPU0, eip 00007db7, registers:
> > Modules linked in: nfs nfsd exportfs lockd nfs_acl sunrpc ppdev lp ipv6
> > dm_snapshot dm_mirror dm_mod apm eeprom i2c_i801 snd_es1938 snd_opl3_lib
> > snd_hwdep snd_mpu401_uart snd_pcm_oss snd_pcm snd_page_alloc snd_mixer_oss
> > snd_seq_dummy snd_seq_oss bt878 snd_seq_midi snd_rawmidi snd_seq_midi_event
> > tuner bttv snd_seq video_buf firmware_class snd_timer snd_seq_device ir_common
> > compat_ioctl32 i2c_algo_bit snd btcx_risc tveeprom videodev v4l2_common
> > v4l1_compat soundcore i2c_amd756 i2c_core nvidia_agp agpgart shpchp pci_hotplug
> > parport_pc parport evdev analog rtc gameport pcspkr ext3 jbd mbcache ide_cd
> > cdrom ide_disk generic amd74xx e100 mii ide_core ohci_hcd usbcore
> > CPU:    0
> > EIP:    00b8:[<00007db7>]    Not tainted VLI
> > EFLAGS: 00000006   (2.6.21-rc4 #3)
> > EIP is at 0x7db7
> > eax: 00000ac2   ebx: 00000001   ecx: 00000000   edx: 0000e42e
> > esi: dfe2bf2e   edi: 0000530a   ebp: 00000000   esp: dfe2be66
> > ds: 0000   es: 0000   fs: 0000  gs: 0000  ss: 0068
> > Process hald (pid: 2198, ti=dfe2a000 task=dff94a70 task.ti=dfe2a000)
> > Stack: c2fb0001 0060ef9e 00010000 530a0000 007b0000 007b0000 f7200000 5de0deb8 
> >        0000eefd 00d80000 c0400000 0033c15e 02820000 00010000 00000000 00000000 
> >        bf2a0000 bf2edfe2 bf2cdfe2 0400dfe2 c5cb0000 bee0ef9e bedcdfe2 bed8dfe2 
> > Call Trace:
> >  =======================
> > Code:  Bad EIP value.
> > 
> > I could also reproduce the same crash using two another USB peripherals (a
> > remote controller and a mouse).
> > 
> > Without acpi=off, it works fine.
> > 
> 
> (Please respond via reply-to-all, not via bugzilla web forms)
> 
> Are you able to get a cleaner kenrel trace than that?  This one seems a bit
> mangled.

No. Initially, I didn't have debugging symbols compiled in, so I rebuilt
the kernel in the hope that I would get something useful. But I got the
same trace.

> Please raise a buzilla entry against acpi for the "another bug", if you
> haven't done so.

It's http://bugzilla.kernel.org/show_bug.cgi?id=7937 (wake on lan
doesn't work when acpi is enabled (works if disabled).

> I assume this indicates a bug in USB (as well) but with this trace it is
> hard to tell.

How could I get a more useful output ?
-- 
| Lucas Nussbaum
| lucas@xxxxxxxxxxxxxxxxxx   http://www.lucas-nussbaum.net/ |
| jabber: lucas@xxxxxxxxxxx             GPG: 1024D/023B3F4F |
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux