10.10 RC: serial8250: too much work for irq (Motorola SM56 modem, RS480, SB400)

Bug #653388 reported by floid
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Previous attempt to file resulted in a Launchpad timeout and lost screed, so here's the "talk-like-the-Micro-Machines-guy" version:
10.10 RC i386 Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux

dmesg clogs with:
[ 326.566996] serial8250: too much work for irq17
[ 326.580318] serial8250: too much work for irq17
[ 326.593635] serial8250: too much work for irq17
[ 326.606966] serial8250: too much work for irq17
[ 326.620285] serial8250: too much work for irq17
[ 326.633606] serial8250: too much work for irq17
oddly only until:
[ 335.695389] serial8250: too much work for irq17
on the boot I was reporting from; see comment #2 re: noticing this at all because it was ongoing under a different session and drowning out dmesg.

Hardware: Compaq SR1611NX desktop

Never observed as a continuous problem under 9.10 using 2.6.31-22-generic #65-Ubuntu SMP Thu Sep 16 15:48:58 UTC 2010 i686 GNU/Linux ; noise from https://bugs.launchpad.net/bugs/475704 may have blocked ever noticing a short burst as above.

All SR1611NXs put the modem, radeon, and AC97 controller on IRQ17;
Forum folklore suggests pulling the modem could be the mindless fix but that would be annoying across multiple machines.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 Cannot stat file /proc/4366/fd/40: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2885 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17'
   Mixer name : 'Realtek ALC658D'
   Components : 'AC97a:414c4781'
   Controls : 38
   Simple ctrls : 24
Date: Sat Oct 2 01:46:01 2010
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
MachineType: Compaq Presario 061 ED866AA-ABA SR1611NX NA541
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 01/25/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.15
dmi.board.name: Amberine M
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.03
dmi.chassis.type: 3
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.15:bd01/25/2007:svnCompaqPresario061:pnED866AA-ABASR1611NXNA541:pvr0nx1411RE101AMBEM00:rvnASUSTekComputerINC.:rnAmberineM:rvr1.03:cvn:ct3:cvr1111:
dmi.product.name: ED866AA-ABA SR1611NX NA541
dmi.product.version: 0nx1411RE101AMBEM00
dmi.sys.vendor: Compaq Presario 061

Revision history for this message
floid (jkanowitz) wrote :
Revision history for this message
floid (jkanowitz) wrote :

Trouble with bug-reporting towards local midnight: "I lied" in a couple important ways:

1. I noticed this because it was *continually* flooding dmesg in my first boot into 10.10 RC; the halt of the messages at [ 335.695389] was seen on a later boot, and suggests this is an intermittent issue;

2. After announcing that it only occurs with 10.10 RC, I caught a flash of it while booting back into 9.10, so it may not be a regression and just have been drowned out by https://bugs.launchpad.net/bugs/475704 . However, I've never noticed it mixed in with that bug's noise before, so the *continuous* complaining first observed must be a rare or new case.

What I did *not* do was properly check the logs under 9.10 to confirm 'that really happened' and I was not just seeing something left in the framebuffer from the warm reboot. I'll have to take a look next time I'm near those machines.

description: updated
Revision history for this message
floid (jkanowitz) wrote :

Confirmed behavior:
On the machine that was warm-booted into i386 10.10 RC and back to 9.10, 9.10 with i386 2.6.31-22-generic #65-Ubuntu SMP does generate the noise from timestamps ~ 20 to 67 at boot. I haven't bothered checking to make sure it goes away from a cold boot - it's hardly a big deal - but does imply the 10.10 RC 'nudged' the hardware into a state to trigger it.

On an identical machine running 9.10 with the same i386 2.6.31-22-generic #65-Ubuntu SMP, I do have history back to boot-time and there's no such complaint.

Obviously warnings that *never stop* are annoying, but that was only observed the once.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

floid, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.