Skip to contentSkip to conversation

Kdump: Disabling PCI interrupts in capture kernel

RFC/PATCH Vivek Goyal 3 participants 3 messages Jun 4, 2005

lore
Share & tools
lore
#0 lore raw

Quoting Alan Stern <[email protected]>:

Quoted 13 lines · Vivek Goyal
Quoted 2 lines

In previous conversations, Alan Stern had raised the issue of console

also

Quoted 2 lines

not working if interrupts are disabled on all the devices. I am not sure but this should be working at least for serial consoles and vga text

consoles.

Quoted 1 line

May be sufficient to capture the dump.

This isn't an issue for x86. It affects other architectures, in which the system console is managed during the early stages of booting by the platform firmware. I suppose serial consoles would always work.

Hi Alan, I know very little about consoles and their working.
I had a question. Even if console is being managed by platform firmware, in initial states of booting, does it require interrupts to be enabled at VGA contorller (at least for the simple text mode). I was quickly browsing through drivers/video/console/vgacon.c and did not look like that this console driver needed interrupts to be enabled at the controller.

Anyway, looks like serial consoles will always work. So at least this can be done for kdump case (CONFIG_CRASH_DUMP) and not generic kernel. Or, as I mentioned in previous mail, while pre-loading capture kernel, pass a command line parameter containing pci dev id of console and capture kernel does not disable interrupts on this console.

Thanks
Vivek

#1 lore raw
Quoted 6 lines · Vivek Goyal

Hi Alan, I know very little about consoles and their working.
I had a question. Even if console is being managed by platform firmware, in initial states of booting, does it require interrupts to be enabled at VGA contorller (at least for the simple text mode). I was quickly browsing through drivers/video/console/vgacon.c and did not look like that this console driver needed interrupts to be enabled at the controller.

This isn't an issue for VGA, as far as I know. It applies to architectures like PPC-64 and perhaps Alpha or PA-Risc. And I don't know the details; ask Grant Grundler.

Quoted 5 lines

Anyway, looks like serial consoles will always work. So at least this can be done for kdump case (CONFIG_CRASH_DUMP) and not generic kernel. Or, as I mentioned in previous mail, while pre-loading capture kernel, pass a command line parameter containing pci dev id of console and capture kernel does not disable interrupts on this console.

I suspect you're right that implementing this only in kdump kernels will work okay.

For people interesting in reading some old threads on the subject, here are some pointers:

http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111055702309788&w=2

http://marc.theaimsgroup.com/?l=linux-kernel&m=98383052711171&w=2

Alan Stern

#2 lore raw
Quoted 9 lines · Alan Stern
Quoted 6 lines · Vivek Goyal

Hi Alan, I know very little about consoles and their working.
I had a question. Even if console is being managed by platform firmware, in initial states of booting, does it require interrupts to be enabled at VGA contorller (at least for the simple text mode). I was quickly browsing through drivers/video/console/vgacon.c and did not look like that this console driver needed interrupts to be enabled at the controller.

Quoted 3 lines

This isn't an issue for VGA, as far as I know. It applies to architectures like PPC-64 and perhaps Alpha or PA-Risc. And I don't know the details; ask Grant Grundler.

I'm more familiar with the serial consoles and how PDC interacts with them.

Quoted 1 line

From HP, both Alex Williamson and Bjorn Helgaas know more about

VGA support. I've cc'd both.

Quoted 5 lines
Quoted 5 lines

Anyway, looks like serial consoles will always work. So at least this can be done for kdump case (CONFIG_CRASH_DUMP) and not generic kernel. Or, as I mentioned in previous mail, while pre-loading capture kernel, pass a command line parameter containing pci dev id of console and capture kernel does not disable interrupts on this console.

parisc serial consoles don't need interrupts enabled. The serial device does need it's MMIO and/or IO Port range enabled (I forgot which). ISTR most serial consoles don't do DMA and thus don't need BusMaster enabled in the PCI command register either.

Quoted 9 lines

I suspect you're right that implementing this only in kdump kernels will work okay.

For people interesting in reading some old threads on the subject, here are some pointers:

http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111055702309788&w=2

http://marc.theaimsgroup.com/?l=linux-kernel&m=98383052711171&w=2

wow...from 2001.
That's when we first release a500 support with Debian 3.0.

thanks,
grant