From: Carsten Rietzschel <cr7@os.inf.tu-dresden.de>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Lee Revell" <rlrevell@joe-job.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"William Lee Irwin III" <wli@holomorphy.com>,
"Lenar L?hmus" <lenar@vision.ee>, "Andrew Morton" <akpm@osdl.org>,
"Arjan van de Ven" <arjanv@redhat.com>,
"Wood, Scott" <Scott.Wood@timesys.com>,
"Saksena, Manas" <Manas.Saksena@timesys.com>
Subject: Re: [patch] voluntary-preempt-2.6.8-rc2-L2 - modem dialup broken
Date: Thu, 29 Jul 2004 14:26:38 +0200 [thread overview]
Message-ID: <200407291426.38785.cr7@os.inf.tu-dresden.de> (raw)
In-Reply-To: <3D848382FB72E249812901444C6BDB1D036EDFD3@exchange.timesys.com>
Hello,
I've found another problem w/ voluntary-preempt-2.6.8-rc2-L2:
my dialup connection with a modem is broken with voluntary-preempt=3.
With
"echo 2 > /proc/sys/kernel/voluntary_preemption"
it works. All modem LEDs are blinking :)
Then
"echo 3 > /proc/sys/kernel/voluntary_preemption"
-> the LEDs stop blinking after a few seconds. The connection times out.
The only log message I see when booting with voluntary-preempt on is this one:
Jul 29 10:57:51 linux irq event 4: bogus return value ffffffff
Jul 29 10:57:51 linux [<c01076ae>] dump_stack+0x1e/0x20
Jul 29 10:57:51 linux [<c0108b4b>] __report_bad_irq+0x2b/0x90
Jul 29 10:57:51 linux [<c0108be0>] report_bad_irq+0x30/0x40
Jul 29 10:57:51 linux [<c0108c82>] note_interrupt+0x92/0xa0
Jul 29 10:57:51 linux [<c0108ecb>] do_hardirq+0x11b/0x180
Jul 29 10:57:51 linux [<c012025c>] irqd+0x9c/0xc0
Jul 29 10:57:51 linux [<c012e25d>] kthread+0xad/0xc0
Jul 29 10:57:51 linux [<c01052b1>] kernel_thread_helper+0x5/0x14
Jul 29 10:57:51 linux handlers:
Jul 29 10:57:51 linux irq event 3: bogus return value ffffffff
Jul 29 10:57:51 linux [<c01076ae>] dump_stack+0x1e/0x20
Jul 29 10:57:51 linux [<c0108b4b>] __report_bad_irq+0x2b/0x90
Jul 29 10:57:51 linux [<c0108be0>] report_bad_irq+0x30/0x40
Jul 29 10:57:51 linux [<c0108c82>] note_interrupt+0x92/0xa0
Jul 29 10:57:51 linux [<c0108ecb>] do_hardirq+0x11b/0x180
Jul 29 10:57:51 linux [<c012025c>] irqd+0x9c/0xc0
Jul 29 10:57:51 linux [<c012e25d>] kthread+0xad/0xc0
Jul 29 10:57:51 linux [<c01052b1>] kernel_thread_helper+0x5/0x14
May be this related to the above problem.
Sorry for this inprecise description. Just ask me for more informations.
Regards,
Carsten
cat /proc/interrupts (without beeing online):
CPU0
0: 5159722 XT-PIC timer
1: 14081 XT-PIC i8042
2: 0 XT-PIC cascade
7: 2855 XT-PIC VIA8233, uhci_hcd
8: 4 XT-PIC rtc
9: 0 XT-PIC acpi
10: 501556 XT-PIC ohci1394, uhci_hcd
11: 40604 XT-PIC eth0, uhci_hcd, ehci_hcd
14: 57086 XT-PIC ide0
15: 38 XT-PIC ide1
NMI: 0
LOC: 5159632
cat /proc/interrupts (beeing online):
CPU0
0: 5248767 XT-PIC timer
1: 14803 XT-PIC i8042
2: 0 XT-PIC cascade
3: 1945822 XT-PIC serial
7: 2893 XT-PIC VIA8233, uhci_hcd
8: 4 XT-PIC rtc
9: 0 XT-PIC acpi
10: 512803 XT-PIC ohci1394, uhci_hcd
11: 40693 XT-PIC eth0, uhci_hcd, ehci_hcd
14: 57251 XT-PIC ide0
15: 38 XT-PIC ide1
NMI: 0
LOC: 5248676
ERR: 21
prev parent reply other threads:[~2004-07-29 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 3:26 [patch] voluntary-preempt-2.6.8-rc2-L2, preemptable hardirqs Saksena, Manas
2004-07-28 20:59 ` Carsten Rietzschel
2004-07-28 22:55 ` Felipe Alfaro Solana
2004-07-29 12:26 ` Carsten Rietzschel [this message]
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=200407291426.38785.cr7@os.inf.tu-dresden.de \
--to=cr7@os.inf.tu-dresden.de \
--cc=Manas.Saksena@timesys.com \
--cc=Scott.Wood@timesys.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=lenar@vision.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®