devzero@web.de wrote:This message means something has invoked an interrupt in the range 0x20 to 0x3f, which it should never have done, since that's in the operating system range. Given the complaint about vesamenu further down the page, I'm assuming the VESA BIOS is invoking a DOS interrupt(!!!!)... although it's very hard to say for sure. It might be possible to track down by augmenting syslinux to print the CS:IP of the supposed DOS system call; if this is the VESA BIOS, it would be in the range C000:xxxx. This probably would be a useful hack anyway, so I'll just implement it. -hpa --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Eric Sandeen | Re: [RFC] Heads up on sys_fallocate() |
| YOSHIFUJI Hideaki / | request_module: runaway loop modprobe net-pf-1 (is Re: Linux 2.6.21-rc1) |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Ben Greear | Re: MACVLANs really best solution? How about a bridge with multiple bridge virtual... |
| Rafael J. Wysocki | 2.6.29-rc8: Reported regressions from 2.6.28 |
