From: Sean <knife@toaster.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-media@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Bugme-new] [Bug 14564] New: capture-example sleeping function called from invalid context at arch/x86/mm/fault.c
Date: Mon, 04 Jan 2010 19:32:22 -0800 [thread overview]
Message-ID: <4B42B2C6.8050702@toaster.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1001042129530.26506-100000@netrider.rowland.org>
Alan Stern wrote:
> Um, when you say it does the job, what do you mean?
It traps the error and prevents the kernel from crashing.
> The job it was _intended_ to do was to prove that your problems are
> caused by hardware errors rather than software bugs. If the patch
> causes the problems to stop, without printing any error messages in the
> log, then it does indeed prove this. After all, the only places the
> patch changes any persistent values are after it prints an error
> message.
>
It did print out error messages:
usb 4-2: new full speed USB device using ohci_hcd and address
2
usb 4-2: New USB device found, idVendor=093a,
idProduct=2460
usb 4-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
usb 4-2: Product: CIF Single
Chip
usb 4-2: Manufacturer: Pixart Imaging
Inc.
usb 4-2: configuration #1 chosen from 1
choice
[root@X-Linux]:~ # modprobe
gspca_pac207
Linux video capture interface:
v2.00
gspca: main v2.8.0
registered
gspca: probing
093a:2460
pac207: Pixart Sensor ID 0x27 Chips ID
0x09
pac207: Pixart PAC207BCA Image Processor and Control Chip detected
(vid/pid 0x093A:0x2460)
gspca: video0
created
usbcore: registered new interface driver
pac207
pac207:
registered
[root@X-Linux]:~ #
capture-example
......................................................................
capture-example used greatest stack depth: 5848 bytes
left
[root@X-Linux]:~ #
capture-example
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
...ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
.ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
....ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
.ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
...ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
.ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
.ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 32 c669f800 c677b800
c677b800
ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..ohci_hcd 0000:00:0b.0: Circular hash: 36 c669f900 c677b900
c677b900
..
[root@X-Linux]:~ #
> (Admittedly, I didn't expect the problem to stop; I expected to get a
> bunch of messages from the second ohci_err(). Just out of curiosity,
> does it make any difference if you remove all those "volatile"s in the
> declaration line for td1 and td2?)
>
It doesn't seem to make much difference.
> I noticed that your CPU is a Cyrix. Perhaps it is the culprit. Have
> you tried running the program on a different computer?
>
Yes, on other computers I don't get this error. Same os image. Though I
haven't found a computer with an ohci controller yet.
> Alan Stern
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2010-01-05 3:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14564-10286@http.bugzilla.kernel.org/>
2009-11-11 23:21 ` [Bugme-new] [Bug 14564] New: capture-example sleeping function called from invalid context at arch/x86/mm/fault.c Andrew Morton
2009-11-12 16:20 ` Alan Stern
2009-12-03 5:48 ` Sean
2009-12-03 21:03 ` Alan Stern
2009-12-16 23:30 ` Sean
2009-12-17 15:22 ` Alan Stern
2009-12-29 9:19 ` Sean
2009-12-29 19:48 ` Sean
2009-12-29 21:23 ` Alan Stern
2009-12-30 0:37 ` Sean
2009-12-30 3:22 ` Alan Stern
2010-01-02 9:00 ` Sean
2010-01-02 20:43 ` Alan Stern
2010-01-03 1:56 ` Sean
2010-01-03 17:35 ` Alan Stern
2010-01-03 23:47 ` Sean
2010-01-04 16:06 ` Alan Stern
2010-01-04 20:02 ` Sean
2010-01-04 20:48 ` Alan Stern
2010-01-04 22:24 ` Sean
2010-01-05 2:40 ` Alan Stern
2010-01-05 3:32 ` Sean [this message]
2010-01-05 15:11 ` Alan Stern
2010-01-05 20:05 ` Sean
2010-01-05 21:06 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B42B2C6.8050702@toaster.net \
--to=knife@toaster.net \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox