Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64

Andrew Morton <[email protected]> wrote:

> Possibly one could work out what's going on by reverse-engineering x86_64
> ioctl command 0x82187201, but unfortunately I don't have time to do that. 

strace can do that.

David
-
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/

---

• References:
  • Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
    • From: Andrew Morton <[email protected]>
  • BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
    • From: Kasper Sandberg <[email protected]>
  • Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
    • From: Andrew Morton <[email protected]>
  • Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
    • From: Kasper Sandberg <[email protected]>

• Prev by Date: Re: [PATCH] PCI: reenable Asus SMBus quirks on resume
• Next by Date: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
• Previous by thread: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
• Next by thread: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]