#74: module unstable on x86_64
------------------------------+---------------------------------------------
Reporter: kelmo | Owner:
Type: defect | Status: new
Priority: critical | Milestone: version 1.0.0 - first stable
release
Component: madwifi: driver | Version: trunk
Resolution: | Keywords:
------------------------------+---------------------------------------------
Comment (by [EMAIL PROTECTED]):
Just a general question here for people relying on logs to trace code
execution. How is this being done? I'm fairly sure that the logs (as
stored on disk) will not necessarily be 'complete', e.g. the latest logs
are stored in buffers in memory but not yet written to disk. A kernel
panic will (again, I believe) not write them out to disk, so the log (on
disk) doesn't really tell you the last thing that happened.
Are you using a serial console? Is that guaranteed to complete output
before moving on to the next line of code?
Again, I could be wrong in any of my assumptions. If so, I'm happy to be
corrected.
--
Ticket URL: <http://madwifi.org/ticket/74>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
