From: Thomas Hood <jdthoodREMOVETHIS@yahoo.co.uk>
To: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: PATCH to fix bug: "serial" does not show up in /proc/interrupts
Date: Wed, 01 Aug 2001 23:20:31 -0400 [thread overview]
Message-ID: <3B68C6FF.31035354@yahoo.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2415 bytes --]
Here is a patch to fix the serial driver so that its name
appears in /proc/interrupts. The bug was caused by code
that was overwriting the string literal "serial" with "".
gcc merges all the "serial" strings together into one, so
the "serial" sent to irq_request() was being ""ed as a
side-effect.
Here is the patch to 2.4.7-ac3 both inline and attached.
// Thomas Hood <jdthood_AT_yahoo.co.uk>
--- serial.c_ORIG Wed Aug 1 23:02:09 2001
+++ serial.c Wed Aug 1 23:11:01 2001
@@ -4852,10 +4852,13 @@
MODULE_DEVICE_TABLE(pci, serial_pci_tbl);
+/* serial_pci_driver_name[] gets truncated to "" if the pci probe fails */
+static char serial_pci_driver_name[] = "serial";
+
static struct pci_driver serial_pci_driver = {
- name: "serial",
+ name: serial_pci_driver_name,
probe: serial_init_one,
- remove: serial_remove_one,
+ remove: serial_remove_one,
id_table: serial_pci_tbl,
};
I wrote:
> I noticed the following anomaly. I am using a modular serial
> driver for /dev/ttyS0 and /dev/ttyS1 (actually /dev/tts/0 and
> /dev/tts/1 under devfs). See the listing of my /proc/interrupts
> below. I have /dev/ttyS1 open; it uses IRQ3; but note that the
> name of the serial driver is not printed in the list.
>
> root@thanatos:~# cat /proc/interrupts
> CPU0
> 0: 65078 XT-PIC timer
> 1: 1546 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 3: 1979 XT-PIC
> 5: 3324 XT-PIC CS4231
> 8: 1 XT-PIC rtc
> 10: 27 XT-PIC mwave_3780i
> 11: 5021 XT-PIC usb-uhci, Texas Instruments PCI1250, Texas Instruments PCI1250 (#2)
> 12: 3268 XT-PIC PS/2 Mouse
> 14: 8807 XT-PIC ide0
> 15: 4 XT-PIC ide1
> NMI: 0
> ERR: 0
>
> Strange. But it gets stranger. I insert a combination modem/
> ethernet pcmcia card and I get:
>
> 7: 9 XT-PIC xirc2ps_cs,
>
> In the past, there was something printed after the comma,
> but now there's just a space. Bizarre.
>
> I was not able to find any silly bugs in the serial driver
> or irq routines that would account for this, so I am worried
> that something is very wrong somewhere.
>
> --
> Thomas Hood
> jdthood_AT_yahoo.co.uk
>
[-- Attachment #2: toms-serial-patch-20010801-1 --]
[-- Type: text/plain, Size: 583 bytes --]
--- serial.c_ORIG Wed Aug 1 23:02:09 2001
+++ serial.c Wed Aug 1 23:11:01 2001
@@ -4852,10 +4852,13 @@
MODULE_DEVICE_TABLE(pci, serial_pci_tbl);
+/* serial_pci_driver_name[] gets truncated to "" if the pci probe fails */
+static char serial_pci_driver_name[] = "serial";
+
static struct pci_driver serial_pci_driver = {
- name: "serial",
+ name: serial_pci_driver_name,
probe: serial_init_one,
- remove: serial_remove_one,
+ remove: serial_remove_one,
id_table: serial_pci_tbl,
};
next reply other threads:[~2001-08-02 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 3:20 Thomas Hood [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-02 3:46 PATCH to fix bug: "serial" does not show up in /proc/interrupts Thomas Hood
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=3B68C6FF.31035354@yahoo.co.uk \
--to=jdthoodremovethis@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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