O_CLOFORK use case
I ran headlong into the use case for O_CLOFORK and got into a locking
debate over it.
The actual use case involves squashing a thread race between two
threads. If a file is opened for write in one thread with O_CLOEXEC
while another thread calls fork(), a race condition can happen where
the thread that closes the handle misses the out of disk error because
the child process closed the handle last inside execve().
The decades old idiom for replacing config files isn't safe in
multi-threaded code. Yipe.
int h = open(".configfile~", O_WRONY | O_EXCL | O_CLOEXEC, 0666);
if (h < 0) { perror(".configfile"); return 1; }
ssize_t delta = 0;
while ((delta = write(h, newconfigdata, newconfiglen)) > 0) {
newconfigdata += delta;
newconfiglen -= delta;
}
if (delta < 0) { perror(".configfile"); return 1; }
if (close(h)) { perror(".configfile"); return 1; }
rename(".configfile~", ".configfile");
To fix it, we have to put locks around close() and fork()/vfork(). Ugh.
USB Floppy Disk Driver
Has anybody tried the USB floppy disk driver in awhile? I just did to read an old disk, and I couldn't read a single byte. I started thinking maybe the hardware's bad, but dd didn't raise en error even after I pulled it out and got "USB Disconnect" on the screen from kernel log. I still don't know if the code is broken or if my hardware's bad. It worked 15 years ago with a 2.6 series kernel. Kernel version: joshua@nova:~ϟ uname -a Linux nova 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux joshua@nova:~ϟ
USB Floppy Disk Driver
Has anybody tried the USB floppy disk driver in awhile? I just did to read an old disk, and I couldn't read a single byte. I started thinking maybe the hardware's bad, but dd didn't raise en error even after I pulled it out and got "USB Disconnect" on the screen from kernel log. I still don't know if the code is broken or if my hardware's bad. It worked 15 years ago with a 2.6 series kernel. Kernel version: joshua@nova:~ϟ uname -a Linux nova 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux joshua@nova:~ϟ
Re: [PATCH] add support for larger files in minix filesystem
No response. I suppose I must be doing something wrong ... On 11/1/15, Joshua Hudson wrote: > From: Joshua Hudson > > The Minix v3 filesystem and kernel driver have no actual dependency on > files > being less than 2GB in size; however the kernel does not allow creating a > file of 2GB or larger on a Minix v3 filesystem. I was able to remove the > pseudo- > dependency easily by changing one line of code (filesystems need to tell > VFS > how big of files they allow). > > This code won't do anything useful unless the filesystem superblock is > patched at offset 1040 to a larger value. The largest safe value is > 0,252,255,255. > > Signed-off-by Joshua Hudson > --- > I'm not on the list anymore so if you don't CC me I won't see it. > > Background: I've been playing around with work on a new embedded device. > where the hardware simply isn't powerful enough to sustain ext2 filesystem. > This resulted in me choosing the Minix filesystem as the operational > filesystem > for reasons including find-next-free-block is sixteen times faster than > FAT. > I discovered the need to collect about 3gb of sensor data in one tape-like > run. > Naturally, this leads to creating a 3gb file; but Linux Kernel can't > handle that. > > Please note I'm pretty far down branches and I don't think a stock kernel > will run on my system (non-free hardware drivers). Thankfully the Minix fs > code changes so slowly this should apply all the same. I have tested that > the patch applies and builds a kernel that fixes the problem. > > The fact that the superblock has to be edited for the patch to do anything > interesting (else it replaces s_maxbytes with the same value) makes this > quite safe to apply even in the presence of a bug I don't know about. > > --- linux-4.2.3/fs/minix/inode.c.orig 2015-11-01 17:13:57.227148723 -0800 > +++ linux-4.2.3/fs/minix/inode.c2015-11-01 17:21:49.785390753 -0800 > @@ -232,6 +232,7 @@ > s->s_max_links = MINIX2_LINK_MAX; > } else > goto out_no_fs; > + s->s_maxbytes = (unsigned)sbi->s_max_size; /* s_max_size > cannot be >=4GB and MAX_LFS_SIZE must be >= 4GB */ > > /* > * Allocate the buffer map to keep the superblock small. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] add support for larger files in minix filesystem
No response. I suppose I must be doing something wrong ... On 11/1/15, Joshua Hudson <joshud...@gmail.com> wrote: > From: Joshua Hudson <joshud...@gmail.com> > > The Minix v3 filesystem and kernel driver have no actual dependency on > files > being less than 2GB in size; however the kernel does not allow creating a > file of 2GB or larger on a Minix v3 filesystem. I was able to remove the > pseudo- > dependency easily by changing one line of code (filesystems need to tell > VFS > how big of files they allow). > > This code won't do anything useful unless the filesystem superblock is > patched at offset 1040 to a larger value. The largest safe value is > 0,252,255,255. > > Signed-off-by Joshua Hudson <joshud...@gmail.com> > --- > I'm not on the list anymore so if you don't CC me I won't see it. > > Background: I've been playing around with work on a new embedded device. > where the hardware simply isn't powerful enough to sustain ext2 filesystem. > This resulted in me choosing the Minix filesystem as the operational > filesystem > for reasons including find-next-free-block is sixteen times faster than > FAT. > I discovered the need to collect about 3gb of sensor data in one tape-like > run. > Naturally, this leads to creating a 3gb file; but Linux Kernel can't > handle that. > > Please note I'm pretty far down branches and I don't think a stock kernel > will run on my system (non-free hardware drivers). Thankfully the Minix fs > code changes so slowly this should apply all the same. I have tested that > the patch applies and builds a kernel that fixes the problem. > > The fact that the superblock has to be edited for the patch to do anything > interesting (else it replaces s_maxbytes with the same value) makes this > quite safe to apply even in the presence of a bug I don't know about. > > --- linux-4.2.3/fs/minix/inode.c.orig 2015-11-01 17:13:57.227148723 -0800 > +++ linux-4.2.3/fs/minix/inode.c2015-11-01 17:21:49.785390753 -0800 > @@ -232,6 +232,7 @@ > s->s_max_links = MINIX2_LINK_MAX; > } else > goto out_no_fs; > + s->s_maxbytes = (unsigned)sbi->s_max_size; /* s_max_size > cannot be >=4GB and MAX_LFS_SIZE must be >= 4GB */ > > /* > * Allocate the buffer map to keep the superblock small. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] add support for larger files in minix filesystem
From: Joshua Hudson The Minix v3 filesystem and kernel driver have no actual dependency on files being less than 2GB in size; however the kernel does not allow creating a file of 2GB or larger on a Minix v3 filesystem. I was able to remove the pseudo- dependency easily by changing one line of code (filesystems need to tell VFS how big of files they allow). This code won't do anything useful unless the filesystem superblock is patched at offset 1040 to a larger value. The largest safe value is 0,252,255,255. Signed-off-by Joshua Hudson --- I'm not on the list anymore so if you don't CC me I won't see it. Background: I've been playing around with work on a new embedded device. where the hardware simply isn't powerful enough to sustain ext2 filesystem. This resulted in me choosing the Minix filesystem as the operational filesystem for reasons including find-next-free-block is sixteen times faster than FAT. I discovered the need to collect about 3gb of sensor data in one tape-like run. Naturally, this leads to creating a 3gb file; but Linux Kernel can't handle that. Please note I'm pretty far down branches and I don't think a stock kernel will run on my system (non-free hardware drivers). Thankfully the Minix fs code changes so slowly this should apply all the same. I have tested that the patch applies and builds a kernel that fixes the problem. The fact that the superblock has to be edited for the patch to do anything interesting (else it replaces s_maxbytes with the same value) makes this quite safe to apply even in the presence of a bug I don't know about. --- linux-4.2.3/fs/minix/inode.c.orig 2015-11-01 17:13:57.227148723 -0800 +++ linux-4.2.3/fs/minix/inode.c2015-11-01 17:21:49.785390753 -0800 @@ -232,6 +232,7 @@ s->s_max_links = MINIX2_LINK_MAX; } else goto out_no_fs; + s->s_maxbytes = (unsigned)sbi->s_max_size; /* s_max_size cannot be >=4GB and MAX_LFS_SIZE must be >= 4GB */ /* * Allocate the buffer map to keep the superblock small. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] add support for larger files in minix filesystem
From: Joshua Hudson <joshud...@gmail.com> The Minix v3 filesystem and kernel driver have no actual dependency on files being less than 2GB in size; however the kernel does not allow creating a file of 2GB or larger on a Minix v3 filesystem. I was able to remove the pseudo- dependency easily by changing one line of code (filesystems need to tell VFS how big of files they allow). This code won't do anything useful unless the filesystem superblock is patched at offset 1040 to a larger value. The largest safe value is 0,252,255,255. Signed-off-by Joshua Hudson <joshud...@gmail.com> --- I'm not on the list anymore so if you don't CC me I won't see it. Background: I've been playing around with work on a new embedded device. where the hardware simply isn't powerful enough to sustain ext2 filesystem. This resulted in me choosing the Minix filesystem as the operational filesystem for reasons including find-next-free-block is sixteen times faster than FAT. I discovered the need to collect about 3gb of sensor data in one tape-like run. Naturally, this leads to creating a 3gb file; but Linux Kernel can't handle that. Please note I'm pretty far down branches and I don't think a stock kernel will run on my system (non-free hardware drivers). Thankfully the Minix fs code changes so slowly this should apply all the same. I have tested that the patch applies and builds a kernel that fixes the problem. The fact that the superblock has to be edited for the patch to do anything interesting (else it replaces s_maxbytes with the same value) makes this quite safe to apply even in the presence of a bug I don't know about. --- linux-4.2.3/fs/minix/inode.c.orig 2015-11-01 17:13:57.227148723 -0800 +++ linux-4.2.3/fs/minix/inode.c2015-11-01 17:21:49.785390753 -0800 @@ -232,6 +232,7 @@ s->s_max_links = MINIX2_LINK_MAX; } else goto out_no_fs; + s->s_maxbytes = (unsigned)sbi->s_max_size; /* s_max_size cannot be >=4GB and MAX_LFS_SIZE must be >= 4GB */ /* * Allocate the buffer map to keep the superblock small. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Executable file format, locating stack?
Is there an executable file format that can specify things like where the stack ends up? Yes, I really do care. I want to put the stack at the top of virtual address space rather than randomized. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Executable file format, locating stack?
Is there an executable file format that can specify things like where the stack ends up? Yes, I really do care. I want to put the stack at the top of virtual address space rather than randomized. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
> > To build a virtual network device requires code for the device, code > for routing the device > in the kernel, some way to tell the router that this machine is hosted > through the host > machine's ethernet card, and control of which processes use which > network devices. > I've bombed out. I don't understand how the network devices work well enough to do any of this. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
To build a virtual network device requires code for the device, code for routing the device in the kernel, some way to tell the router that this machine is hosted through the host machine's ethernet card, and control of which processes use which network devices. I've bombed out. I don't understand how the network devices work well enough to do any of this. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
Quoting Serge E. Hallyn ([EMAIL PROTECTED]) >Quoting Joshua Hudson ([EMAIL PROTECTED]): > Why would you want a virtual network device implementation? The whole > >So that a jailed process can use the net but can't use your network >address (intercept ssh, imap/stunnel, etc). [snip] >But in the end vserver with read-only bind mounts seems a better way to >go imo. Latest version of linux vserver source: 100K bzipped Latest version of linux-jail: 34K uncompressed To build a virtual network device requires code for the device, code for routing the device in the kernel, some way to tell the router that this machine is hosted through the host machine's ethernet card, and control of which processes use which network devices. Way too much work for something intended to be simple and have essentially no overhead. All this work only gets jailed processes the ability to use 127.0.0.1. The rest I can already do with eth0:1 and the specs for jail(2) from BSD. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
All right, I'll see what I can come up with. This is quite a tall order. 1. A mechanism for creating virtual network interfaces 2. A mechanism for restricting binding to certain network interfaces 3. A mechanism for binding certain network interfaces. 4. The jail code itself Much of the work is already done in other projects, but it requires grafting. It seems much simpler to bind the jail's address to an network alias (such as eth0:1), and bind the jail to the address of the alias. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
All right, I'll see what I can come up with. This is quite a tall order. 1. A mechanism for creating virtual network interfaces 2. A mechanism for restricting binding to certain network interfaces 3. A mechanism for binding certain network interfaces. 4. The jail code itself Much of the work is already done in other projects, but it requires grafting. It seems much simpler to bind the jail's address to an network alias (such as eth0:1), and bind the jail to the address of the alias. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
Quoting Serge E. Hallyn ([EMAIL PROTECTED]) Quoting Joshua Hudson ([EMAIL PROTECTED]): Why would you want a virtual network device implementation? The whole So that a jailed process can use the net but can't use your network address (intercept ssh, imap/stunnel, etc). [snip] But in the end vserver with read-only bind mounts seems a better way to go imo. Latest version of linux vserver source: 100K bzipped Latest version of linux-jail: 34K uncompressed To build a virtual network device requires code for the device, code for routing the device in the kernel, some way to tell the router that this machine is hosted through the host machine's ethernet card, and control of which processes use which network devices. Way too much work for something intended to be simple and have essentially no overhead. All this work only gets jailed processes the ability to use 127.0.0.1. The rest I can already do with eth0:1 and the specs for jail(2) from BSD. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Fix mmap_kmem (was: [question] What's the difference between /dev/kmem and /dev/mem)
On 8/13/05, Arjan van de Ven <[EMAIL PROTECTED]> wrote: > On Fri, 2005-08-12 at 09:35 -0700, Linus Torvalds wrote: > > > > On Thu, 11 Aug 2005, Steven Rostedt wrote: > > > > > > Found the problem. It is a bug with mmap_kmem. The order of checks is > > > wrong, so here's the patch. Attached is a little program that reads the > > > System map looking for the variable modprobe_path. If it finds it, then > > > it opens /dev/kmem for read only and mmaping it to read the contents of > > > modprobe_path. > > > > I'm actually more inclined to try to deprecate /dev/kmem.. I don't think > > anybody has ever really used it except for some rootkits. It only exists > > in the first place because it's historical. > > > > We do need to support /dev/mem for X, but even that might go away some > > day. > > > > So I'd be perfectly happy to fix this, but I'd be even happier if we made > > the whole kmem thing a config variable (maybe even default it to "off"). > I believe rootkit detectors, as well as some versions of ps (wchan field) use kmem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
On 8/13/05, Serge E. Hallyn <[EMAIL PROTECTED]> wrote: > The latest version (which is still quite old) is at > http://www.sf.net/projects/linuxjail and does have ipv6 support. The last > time I submitted it, Christoph had objected to the way the networking was > done in general. I've tried twice to float a generalized "per-process > network namespaces" patch, but haven't really found a good approach. > > I suspect that the best approach would be to take the linux-vserver > ngnet implementation and convert it to a standalone network namespace > plus virtual network device implementation. Do you care to give this > a try? > > thanks, > -serge Why would you want a virtual network device implementation? The whole point of jail() is a replacement for chroot() for housing untrusted root processes in a lightweight manner as reasonable. I think in one way at least, I have restricted the manner of jail behavior better than the current linuxjail, by turning off capabilities rather than blocking mknod(), mount(), etc. I do like the idea of patching in through LSM, however not everything can be done there. In particular, I could escape from the jail as implemented there by a classic chroot() trick. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BSD jail
On 8/13/05, Serge E. Hallyn [EMAIL PROTECTED] wrote: The latest version (which is still quite old) is at http://www.sf.net/projects/linuxjail and does have ipv6 support. The last time I submitted it, Christoph had objected to the way the networking was done in general. I've tried twice to float a generalized per-process network namespaces patch, but haven't really found a good approach. I suspect that the best approach would be to take the linux-vserver ngnet implementation and convert it to a standalone network namespace plus virtual network device implementation. Do you care to give this a try? thanks, -serge Why would you want a virtual network device implementation? The whole point of jail() is a replacement for chroot() for housing untrusted root processes in a lightweight manner as reasonable. I think in one way at least, I have restricted the manner of jail behavior better than the current linuxjail, by turning off capabilities rather than blocking mknod(), mount(), etc. I do like the idea of patching in through LSM, however not everything can be done there. In particular, I could escape from the jail as implemented there by a classic chroot() trick. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Fix mmap_kmem (was: [question] What's the difference between /dev/kmem and /dev/mem)
On 8/13/05, Arjan van de Ven [EMAIL PROTECTED] wrote: On Fri, 2005-08-12 at 09:35 -0700, Linus Torvalds wrote: On Thu, 11 Aug 2005, Steven Rostedt wrote: Found the problem. It is a bug with mmap_kmem. The order of checks is wrong, so here's the patch. Attached is a little program that reads the System map looking for the variable modprobe_path. If it finds it, then it opens /dev/kmem for read only and mmaping it to read the contents of modprobe_path. I'm actually more inclined to try to deprecate /dev/kmem.. I don't think anybody has ever really used it except for some rootkits. It only exists in the first place because it's historical. We do need to support /dev/mem for X, but even that might go away some day. So I'd be perfectly happy to fix this, but I'd be even happier if we made the whole kmem thing a config variable (maybe even default it to off). I believe rootkit detectors, as well as some versions of ps (wchan field) use kmem. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BSD jail
I had been wanting this functionality myself, but for some reason it never found its way into the stock kernel. I looked around, started coding, looked some more, coded some more, looked some more until I found this: http://kerneltrap.org/node/3823 I suppose the reason it wasn't applied is lack of good IPv6 support. It is perhaps about what I was looking for, but a slightly different method. My idea was to cause no disturbance to the normal security chain, and so maintain jails in the following manner (remember, the sys_jail call is trusted) 1. Add an additional check to path_lookup (actually, a functioned called by path_lookup) to check for jail roots in addition to normal chroots. 2. Lockdown process visibility to only processes in the same jail. 3. Lockdown kill/ptrace/setpriority to processes in the same jail. 4. Lockdown capabilities to a restricted set that prevents novel means of breaking the jail. 5. Restrict binding to one IPv4 and one IPv6 address (squash bind to all to bind to that). All of this is done in front of the normal security mechansim, so that some non-default security module will not accidentally break this. I provided compatability for exactly the BSD jail(2) call, but did it without breaking programs that depend on chroot escapes working (there are a few). I am currently about a third of the way to completion. This means that I will finish unless some other mechanism is provided before I do. I personally don't care if my patch is used (if released), but I want this functionality. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BSD jail
I had been wanting this functionality myself, but for some reason it never found its way into the stock kernel. I looked around, started coding, looked some more, coded some more, looked some more until I found this: http://kerneltrap.org/node/3823 I suppose the reason it wasn't applied is lack of good IPv6 support. It is perhaps about what I was looking for, but a slightly different method. My idea was to cause no disturbance to the normal security chain, and so maintain jails in the following manner (remember, the sys_jail call is trusted) 1. Add an additional check to path_lookup (actually, a functioned called by path_lookup) to check for jail roots in addition to normal chroots. 2. Lockdown process visibility to only processes in the same jail. 3. Lockdown kill/ptrace/setpriority to processes in the same jail. 4. Lockdown capabilities to a restricted set that prevents novel means of breaking the jail. 5. Restrict binding to one IPv4 and one IPv6 address (squash bind to all to bind to that). All of this is done in front of the normal security mechansim, so that some non-default security module will not accidentally break this. I provided compatability for exactly the BSD jail(2) call, but did it without breaking programs that depend on chroot escapes working (there are a few). I am currently about a third of the way to completion. This means that I will finish unless some other mechanism is provided before I do. I personally don't care if my patch is used (if released), but I want this functionality. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
PCI: Using ACPI for IRQ routing ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: Sleep Button (CM) [SBTN] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (59 C) ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI interrupt :00:02.0[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PS/2 Keyboard Controller [KBC] at I/O 0x60, 0x66, irq 1 ACPI: PS/2 Mouse Controller [PS2M] at irq 12 i8042.c: Can't read CTR while initializing i8042. ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7 ACPI: PCI interrupt :00:1f.6[B] -> GSI 7 (level, low) -> IRQ 7 ACPI: PCI interrupt :02:01.0[A] -> GSI 7 (level, low) -> IRQ 7 ACPI: PCI interrupt :00:1f.1[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt :02:04.0[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.7[D] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt :00:1d.0[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.1[B] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.2[C] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt :00:1f.5[B] -> GSI 7 (level, low) -> IRQ 7 ACPI wakeup devices: ACPI: (supports S0 S1 S3 S4 S4bios S5) More like it, hmmm? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
On Wed, 2 Mar 2005, Dmitry Torokhov wrote: > On Wed, 2 Mar 2005 13:26:18 -0800 (PST), Joshua Hudson > <[EMAIL PROTECTED]> wrote: > > No obvous reason. Works fine with kernel 2.6.10 > > Does it work with i8042.noacpi kernel boot parameter? > Yes, it does. I never heard of that option before, or any one like it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
Relevent messages (erring on the heavy side) ACPI: RSDP (v000 DELL ) @ 0x000fdf00 ACPI: RSDT (v001 DELLCPi R 0x27d4061d ASL 0x0061) @ 0x1fef ACPI: FADT (v001 DELLCPi R 0x27d4061d ASL 0x0061) @ 0x1fef0400 ACPI: DSDT (v001 INT430 SYSFexxx 0x1001 MSFT 0x010e) @ 0x ACPI: PM-Timer IO Port: 0x808 ... ACPI: Subsystem revision 20050211 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11 ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT] ... i8k: unable to get SMM Dell signature i8k: unable to get SMM BIOS version ... PCI: Using ACPI for IRQ routing ** PCI interrupts are no longer routed automatically. If this ** causes a device to stop working, it is probably because the ** driver failed to call pci_enable_device(). As a temporary ** workaround, the "pci=routeirq" argument restores the old ** behavior. If this argument makes the device work again, ** please email the output of "lspci" to [EMAIL PROTECTED] ** so I can fix the driver. ... apm: BIOS not found. NTFS driver 2.1.22 [Flags: R/W]. ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: Sleep Button (CM) [SBTN] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (56 C) ... ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI interrupt :00:02.0[A] -> GSI 11 (level, low) -> IRQ 11 ... i8042: ACPI detection disabled i8042.c: Warning: Keylock active. ... i8042: ACPI detection disabled i8042.c: Warning: Keylock active. ... ACPI: PCI interrupt :02:01.0[A] -> GSI 7 (level, low) -> IRQ 7 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
> > > Does it work with i8042.noacpi kernel boot parameter? > > > > > Yes, it does. > Btw, when it boots _without_ this option is there any messages from > i8042 or ACPI? > A few. I'll go back and catch them for you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
No obvous reason. Works fine with kernel 2.6.10 Result of lspci: 00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) 00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) 00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 01) 00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 01) 00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 01) 00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 01) 00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corp. 82801DB (ICH4) AC'97 Modem Controller (rev 01) 02:01.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 02:02.0 Network controller: Broadcom Corporation: Unknown device 4324 (rev 03) 02:04.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller Diff of .config between 2.6.10 & 2.6.11 --- linux-2.6.10/.config2005-02-19 18:33:49.0 -0800 +++ linux-2.6.11/.config2005-03-02 12:11:54.0 -0800 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit -# Linux kernel version: 2.6.10 -# Sat Feb 19 17:34:02 2005 +# Linux kernel version: 2.6.11 +# Wed Mar 2 12:11:54 2005 # CONFIG_X86=y CONFIG_MMU=y @@ -92,6 +92,7 @@ CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y @@ -102,6 +103,7 @@ # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y +CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y @@ -158,6 +160,7 @@ CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y +# CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support @@ -176,7 +179,8 @@ # CONFIG_CPU_FREQ=y # CONFIG_CPU_FREQ_DEBUG is not set -# CONFIG_CPU_FREQ_PROC_INTF is not set +CONFIG_CPU_FREQ_STAT=y +# CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y @@ -216,6 +220,7 @@ CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y +# CONFIG_PCIEPORTBUS is not set CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # CONFIG_ISA is not set @@ -227,7 +232,6 @@ # CONFIG_PCCARD=y CONFIG_PCMCIA_DEBUG=y -CONFIG_PCMCIA_OBSOLETE=y CONFIG_PCMCIA=y CONFIG_CARDBUS=y @@ -238,6 +242,7 @@ CONFIG_PD6729=y CONFIG_I82092=y CONFIG_TCIC=y +CONFIG_PCCARD_NONSTATIC=y # # PCI Hotplug Support @@ -291,6 +296,7 @@ # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set +# CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set @@ -313,6 +319,7 @@ CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y +# CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support @@ -406,6 +413,7 @@ # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set +# CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers @@ -426,6 +434,7 @@ CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set +# CONFIG_SCSI_SATA_QSTOR is not set CONFIG_SCSI_SATA_SX4=m # CONFIG_SCSI_SATA_SIL is not set CONFIG_SCSI_SATA_SIS=m @@ -454,7 +463,6 @@ # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set -# CONFIG_SCSI_QLA6322 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_NSP32 is not set @@ -579,7 +587,6 @@ CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_TARGET_NETMAP=y CONFIG_IP_NF_TARGET_SAME=y -# CONFIG_IP_NF_NAT_LOCAL is not set # CONFIG_IP_NF_NAT_SNMP_BASIC is not set CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y @@ -798,6 +805,7 @@ # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set CONFIG_SERIO_PCIPS2=y +CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # @@ -968,6 +976,7 @@ CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y +# CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound @@ -986,7 +995,7 @@ CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_SEQUENCER_OSS=y -# CONFIG_SND_RTCTIMER is not set +CONFIG_SND_RTCTIMER=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is
Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
No obvous reason. Works fine with kernel 2.6.10 Result of lspci: 00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) 00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) 00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 01) 00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 01) 00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 01) 00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 01) 00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corp. 82801DB (ICH4) AC'97 Modem Controller (rev 01) 02:01.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 02:02.0 Network controller: Broadcom Corporation: Unknown device 4324 (rev 03) 02:04.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller Diff of .config between 2.6.10 2.6.11 --- linux-2.6.10/.config2005-02-19 18:33:49.0 -0800 +++ linux-2.6.11/.config2005-03-02 12:11:54.0 -0800 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit -# Linux kernel version: 2.6.10 -# Sat Feb 19 17:34:02 2005 +# Linux kernel version: 2.6.11 +# Wed Mar 2 12:11:54 2005 # CONFIG_X86=y CONFIG_MMU=y @@ -92,6 +92,7 @@ CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y @@ -102,6 +103,7 @@ # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y +CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y @@ -158,6 +160,7 @@ CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y +# CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support @@ -176,7 +179,8 @@ # CONFIG_CPU_FREQ=y # CONFIG_CPU_FREQ_DEBUG is not set -# CONFIG_CPU_FREQ_PROC_INTF is not set +CONFIG_CPU_FREQ_STAT=y +# CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y @@ -216,6 +220,7 @@ CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y +# CONFIG_PCIEPORTBUS is not set CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # CONFIG_ISA is not set @@ -227,7 +232,6 @@ # CONFIG_PCCARD=y CONFIG_PCMCIA_DEBUG=y -CONFIG_PCMCIA_OBSOLETE=y CONFIG_PCMCIA=y CONFIG_CARDBUS=y @@ -238,6 +242,7 @@ CONFIG_PD6729=y CONFIG_I82092=y CONFIG_TCIC=y +CONFIG_PCCARD_NONSTATIC=y # # PCI Hotplug Support @@ -291,6 +296,7 @@ # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set +# CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set @@ -313,6 +319,7 @@ CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y +# CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support @@ -406,6 +413,7 @@ # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set +# CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers @@ -426,6 +434,7 @@ CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set +# CONFIG_SCSI_SATA_QSTOR is not set CONFIG_SCSI_SATA_SX4=m # CONFIG_SCSI_SATA_SIL is not set CONFIG_SCSI_SATA_SIS=m @@ -454,7 +463,6 @@ # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set -# CONFIG_SCSI_QLA6322 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_NSP32 is not set @@ -579,7 +587,6 @@ CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_TARGET_NETMAP=y CONFIG_IP_NF_TARGET_SAME=y -# CONFIG_IP_NF_NAT_LOCAL is not set # CONFIG_IP_NF_NAT_SNMP_BASIC is not set CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y @@ -798,6 +805,7 @@ # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set CONFIG_SERIO_PCIPS2=y +CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # @@ -968,6 +976,7 @@ CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y +# CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound @@ -986,7 +995,7 @@ CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_SEQUENCER_OSS=y -# CONFIG_SND_RTCTIMER is not set +CONFIG_SND_RTCTIMER=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
Does it work with i8042.noacpi kernel boot parameter? Yes, it does. Btw, when it boots _without_ this option is there any messages from i8042 or ACPI? A few. I'll go back and catch them for you. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
Relevent messages (erring on the heavy side) ACPI: RSDP (v000 DELL ) @ 0x000fdf00 ACPI: RSDT (v001 DELLCPi R 0x27d4061d ASL 0x0061) @ 0x1fef ACPI: FADT (v001 DELLCPi R 0x27d4061d ASL 0x0061) @ 0x1fef0400 ACPI: DSDT (v001 INT430 SYSFexxx 0x1001 MSFT 0x010e) @ 0x ACPI: PM-Timer IO Port: 0x808 ... ACPI: Subsystem revision 20050211 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11 ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT] ... i8k: unable to get SMM Dell signature i8k: unable to get SMM BIOS version ... PCI: Using ACPI for IRQ routing ** PCI interrupts are no longer routed automatically. If this ** causes a device to stop working, it is probably because the ** driver failed to call pci_enable_device(). As a temporary ** workaround, the pci=routeirq argument restores the old ** behavior. If this argument makes the device work again, ** please email the output of lspci to [EMAIL PROTECTED] ** so I can fix the driver. ... apm: BIOS not found. NTFS driver 2.1.22 [Flags: R/W]. ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: Sleep Button (CM) [SBTN] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (56 C) ... ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI interrupt :00:02.0[A] - GSI 11 (level, low) - IRQ 11 ... i8042: ACPI detection disabled i8042.c: Warning: Keylock active. ... i8042: ACPI detection disabled i8042.c: Warning: Keylock active. ... ACPI: PCI interrupt :02:01.0[A] - GSI 7 (level, low) - IRQ 7 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
On Wed, 2 Mar 2005, Dmitry Torokhov wrote: On Wed, 2 Mar 2005 13:26:18 -0800 (PST), Joshua Hudson [EMAIL PROTECTED] wrote: No obvous reason. Works fine with kernel 2.6.10 Does it work with i8042.noacpi kernel boot parameter? Yes, it does. I never heard of that option before, or any one like it. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Bug report -- keyboard not working Linux 2.6.11 on Inspiron 1150
PCI: Using ACPI for IRQ routing ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: Sleep Button (CM) [SBTN] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (59 C) ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI interrupt :00:02.0[A] - GSI 11 (level, low) - IRQ 11 ACPI: PS/2 Keyboard Controller [KBC] at I/O 0x60, 0x66, irq 1 ACPI: PS/2 Mouse Controller [PS2M] at irq 12 i8042.c: Can't read CTR while initializing i8042. ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7 ACPI: PCI interrupt :00:1f.6[B] - GSI 7 (level, low) - IRQ 7 ACPI: PCI interrupt :02:01.0[A] - GSI 7 (level, low) - IRQ 7 ACPI: PCI interrupt :00:1f.1[A] - GSI 11 (level, low) - IRQ 11 ACPI: PCI interrupt :02:04.0[A] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.7[D] - GSI 11 (level, low) - IRQ 11 ACPI: PCI interrupt :00:1d.0[A] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.1[B] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI interrupt :00:1d.2[C] - GSI 11 (level, low) - IRQ 11 ACPI: PCI interrupt :00:1f.5[B] - GSI 7 (level, low) - IRQ 7 ACPI wakeup devices: ACPI: (supports S0 S1 S3 S4 S4bios S5) More like it, hmmm? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help - really messed up kernel
Thinks for trying. I finally found the problem myself. There is some incompatability between syslinux 2.10 and kernel 2.6.10 Using lilo on the first floppy fixed the problem Oh, and no I am *not* using an initrd. I am using the old paramiters that cause the kernel to load the ramdisk after it boots. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help - really messed up kernel
On Sun, 20 Feb 2005, Brian Beattie wrote: > On Sun, 2005-02-20 at 15:22 -0800, Joshua Hudson wrote: > > I am trying to install linux on a laptop that cannot boot from cdrom. > I handled this by putting smart-boot http://btmgr.webframe.org/ in the > hard drive MBR from a dos floppy, smart-boot can boot from a cdrom. > Then as long as you don't wipe out your MBR you can still boot from a > cdrom. > Ah yes, that crashes. Spotted it in Slackware 10 install CD, but it doesn't work on this system. Too bad. > -- > Brian Beattie LFS12947 | "Honor isn't about making the right choices. > [EMAIL PROTECTED] | It's about dealing with the consequences." > www.beattie-home.net | -- Midori Koto > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Help - really messed up kernel
I am trying to install linux on a laptop that cannot boot from cdrom. I got a stripped-down kernel to boot from floppy, ran lspci to get the hardware information. I then reconfigured and rebuilt the kernel for the image. I built this kernel from stock 2.6.10 from www.kernel.org. This is the configuration file. I then installed it on a floppy disk with syslinux, then tried to boot it. boot: vmlinuz root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1 (my ramdisk is the next flooppy, this kernel is 1.3mb) Did not load the ramdisk. I got an error about unable to open root on "" or device 22,6. Hmm. So, I ran rdev to set the kernel default root to /dev/fd0 and booted. Result: loaded the ramdisk, then complained about lack of a valid filesystem on /dev/fd0 Hmm. I've never seen anything like this before. # # Automatically generated make config: don't edit # Linux kernel version: 2.6.10 # Sun Feb 20 14:07:04 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION="/dev/hda2" # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y
Help - really messed up kernel
I am trying to install linux on a laptop that cannot boot from cdrom. I got a stripped-down kernel to boot from floppy, ran lspci to get the hardware information. I then reconfigured and rebuilt the kernel for the image. I built this kernel from stock 2.6.10 from www.kernel.org. This is the configuration file. I then installed it on a floppy disk with syslinux, then tried to boot it. boot: vmlinuz root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1 (my ramdisk is the next flooppy, this kernel is 1.3mb) Did not load the ramdisk. I got an error about unable to open root on NULL or device 22,6. Hmm. So, I ran rdev to set the kernel default root to /dev/fd0 and booted. Result: loaded the ramdisk, then complained about lack of a valid filesystem on /dev/fd0 Hmm. I've never seen anything like this before. # # Automatically generated make config: don't edit # Linux kernel version: 2.6.10 # Sun Feb 20 14:07:04 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION=/dev/hda2 # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y
Re: Help - really messed up kernel
On Sun, 20 Feb 2005, Brian Beattie wrote: On Sun, 2005-02-20 at 15:22 -0800, Joshua Hudson wrote: I am trying to install linux on a laptop that cannot boot from cdrom. I handled this by putting smart-boot http://btmgr.webframe.org/ in the hard drive MBR from a dos floppy, smart-boot can boot from a cdrom. Then as long as you don't wipe out your MBR you can still boot from a cdrom. Ah yes, that crashes. Spotted it in Slackware 10 install CD, but it doesn't work on this system. Too bad. -- Brian Beattie LFS12947 | Honor isn't about making the right choices. [EMAIL PROTECTED] | It's about dealing with the consequences. www.beattie-home.net | -- Midori Koto - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help - really messed up kernel
Thinks for trying. I finally found the problem myself. There is some incompatability between syslinux 2.10 and kernel 2.6.10 Using lilo on the first floppy fixed the problem Oh, and no I am *not* using an initrd. I am using the old paramiters that cause the kernel to load the ramdisk after it boots. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
